Issues with iOS

Hi Janto,

Thanks for reaching out. I’m not aware of any issues on iOS, please could you provide a link to your site so I can take a look? Also, are you experiencing this issue when you view the demo?

Thanks,

Joe

Hi Joe,

thanks for your fast reply. So far I have triggered that problem also on different (iOS) devices. Using Android everything works fine.
You can find my tryouts here.
In the demo all maps are illustrated appropriately.

Best
Janto

Hi Janto,

Thanks for the link. I have viewed your site on my physical iOS device and on various devices using the iOS simulator and everything seems to be working correctly. Please could you detail the exact issue you are having? Perhaps I am missing something.

Thanks,

Joe

Hi Joe,

that is certainly interesting. This is basically what the map looks like on my phone. Since nobody else has ever experienced this issue, it is probably attributed to the individual setting of my devices?

Best
Janto

Hi Janto,

Yes this is very weird. All of a sudden I started seeing the same thing on my physical device (but not on the simulators), so I was able to view the following JavaScript error message triggered by jQuery:

RangeError: Maximum call stack size exceeded.

It would appear that this error is stopping Waymark from loading. My guess is that this error is being caused by either your theme, or a plugin you have installed. So you might want to try switching themes and systematically disabling other plugins to see if you can locate the source of the error.

Unfortunately viewing the iOS Safari errors is quite cumbersome.

My apologies, but at this time I can not think of anything else to suggest. Please do feel free to come back if you make any discovers or if there is anything else I can do to help.

All the best,

Joe

I am marking this topic as resolved, as I do not believe it to be an issue with Waymark. However please do let me know if I can be of further assistance.

Thanks,

Joe

Hi Joe,

I seem to be having this issue also, I dont suppose you have any further update on this or if you found out anything else about the issue.

Thanks
Alex

Hi Alex,

Thanks for reaching out. No, I don’t have any other details on this issue other than outlined above.

Could you provide a link to where I can see this behavior so I could take a look?

Thanks,

Joe

Hi Alex and Joe,

In my case I only remade the map which did not show up properly.
Afterwards I have been using the plugin without encountering this problem ever since. I however know that does not help much to fix the issue.

Best
Janto

Hi Joe,

of course, the map is on the page – https://emmasadventures.co.uk/millington-walk/
it works via the desktop browsers but I have tried it via 2 different browsers on ios but the map doesnt seem to show. You can see the outline where the map would be but not the map itself.

Regards,
Alex

Hi Janto,

Thanks for the update, I did try that earlier but It for me didnt seem to make any difference unfortunately.

Regards,
Alex

Hi Alex,

Thanks for the link. Unfortunately I am having issues viewing your site, the page is either taking minutes to load, or not at all. This is happening for me on multiple browsers and devices, so I’m not sure what is going on there.

The times I did get the page to load I am seeing lots of console errors. Errors appearing here can prevent Waymark from functioning. The errors I am seeing include multiple jQuery is not defined errors, which Waymark requires and so could be the reason for the issue.

It is puzzling that things are working for you on desktop but not on mobile. As this is as far as I could get, I can’t see anything Waymark specific at this time. Perhaps try clearing all of your browser caches and then reloading the page with the error console open to see if there are any clues there.

I hope this helps.

Cheers,

Joe

Hi Joe,

All sorted, it was a pesky plugin that was causing the issue, Thanks for having a look and pointing me in the right direction :).

Cheers
Alex

Hi Alex,

Glad to hear you got it working ??

Joe

Also, thanks for your input @chilledkroete, happy to hear you got your issue sorted also.

Joe