Thanks, I believe it's fixed now. (Chrome on iOS is essentially Safari so I guess the similarity of errors was expected)