I have an app that pulls sensor data from an external API. It pulls all the data in one call and stores the data in custom states. On the web everything works fine, but on mobile, if I have more than 7 or 8 sensors, several seconds after the API call has completed and all data has been pulled down, the page will refresh. On Safari it will do this twice and then “A problem repeatedly occurred on…”. On Chrome it refreshes once and then works.
Any thoughts on how I can debug this?
Hey!
I’m having a similar issue. Only on mobile; some pages on my site will refresh once or twice, then crash. It happens on Safari as well as Chrome. Did you find a solution or anything helpful? Anything would be greatly appreciated.
Edit: It also happens on desktop when I make the screen size mobile. It doesn’t happen in Version Test on either devices
I just found this thread:
He seemed to have been in the same situation and said it was because of a Plugin called “tagger” which I also had installed. Do you also have Tagger?
I’m experiencing something similar on my app currently, but it’s tied to the table element. If there are too many rows loaded it crashes iOS Safari and forces a page refresh. In my PWA, after the second refresh it will crash with the problem occurred repeatedly message which is a larger problem. I am adding pagination to my table now to help alleviate, which is probably a good idea either way.
Glad to see some other people chiming in here! I still haven’t fixed this. Unfortunately I don’t have Tagger installed, so that’s not it for me. The items are in a repeating group, but I’m not using the Table element.
GOT IT!!! Microsoft Clarity plugin. Once I removed that, no more crashes. Phew!
Hi everyone,
It seems plugins can cause these refresh problems. If you’re still facing this, try checking your plugins like Microsoft Clarity or Tagger. Turning them off for a while might help figure out the issue.
Omg, you’re right bc we also use Clarity. I’ll remove it and lyk if it works. Both Tagger and Clarity will be removed this publish, so I won’t really be able to tell which worked for me. I’m glad you figured this out; I’ve been stressing about this a lot lately hahaha
I can confirm removing Microsoft Clarity fixed this issue for us too!
Thanks everyone for the updates. I am using Clarity so I’m sure that was the issue for me as well, but it forced me to add pagination to all my large tables and that was worthwhile!
Is anyone still experiencing this issue, even if you are not using Clarity or Tagger plugins?
