Hello,
My app is running in production with a few liveview pages. Customers in regions known to have poor connection have reported that the liveview pages constantly refresh on a 10 second or so interval. I was not able to reproduce the issue myself, but I was able to force the app into the refresh cycle by including :timer.sleep(10000) in the mount/3 callback. My thinking was this would simulate a shaky connection, and indeed it forced me into the same sort of refresh loop.
I have a few questions
- Is there anything I can do about this? I am going to have users in regions of poor connection. Is there a way to gracefully degrade the liveview page for users who are not able to get a strong connection? If not, I may have to completely sunset use of liveview in my application, which is not something I want to do.
- What is liveview’s failsafe mode? After 10 refreshes the debugger mentioned that it was putting itself in failsafe mode, which didn’t actually seem to change the behavior. I was still getting put into a refresh loop.
Any help would be appreciated! After exploring liveview for 6 months or so in a production environment, the biggest barrier to full adoption is the fact that it does not seem to gracefully degrade. Putting a page into a refresh loop every 10 seconds is not a useable experience.
