|
olemak
|
August 13, 2015 at 7:25 am
We’re getting almost the exact same error too (except it is “607” at the end, not “598”). Would that be a completely different issue?
We have not enabled any caching but will check with the host. However, we were able to replicate the exact same error on another site we found that also uses Event Espresso.
For us, the error only occurs on iPhone 4 running Chrome. Safari on the same phone works fine, and Chrome everywhere else also seems to run fine.
So I am thinking maybe it’s related to the javascript engine Chrome uses on pre-ios 8. From iOS8 and up, everything uses Apples native. On sub-iOS8, however, there’s a “bring your own” javascript engine for all third parties. I suspect that would perhaps be the pulprit, what do you think?
|
|
Josh
|
August 17, 2015 at 3:42 pm
Hi there,
I split this reply into its own topic so we can follow up here. I don’t think it’s an issue specifically to Chrome for iOS’s JS engine. Along with that, I tried a registration on your site with Chrome for iOS and it appears to work as expected.
Some potential causes may be cookies being blocked or network settings. When you see the error, is the iOS device connected to wifi or is it using the cellular network?
|
