Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS Infinite Loading #10

Open
KingRial opened this issue Mar 21, 2019 · 7 comments
Open

iOS Infinite Loading #10

KingRial opened this issue Mar 21, 2019 · 7 comments

Comments

@KingRial
Copy link

Is there any working example to handle the Infinite Loading on iOS ?

I am trying to follow the proposed solution but without success.

@NekR
Copy link
Member

NekR commented May 3, 2019

Hi. I may publish one soon. I'll let you know

@danielbayerlein
Copy link

@KingRial Have you found a solution?

@KingRial
Copy link
Author

KingRial commented Aug 2, 2019

@danielbayerlein Unluckily, up to now on iOS 12+ I just admitted defeat when using PWA technology.
Too many problems with the caches and the lifecycle; no way to debug the PWA when it's used as standalone; odd behaviours; and so on...

I hope iOS 13 will change the situation.

@lastmjs
Copy link

lastmjs commented Aug 2, 2019

@KingRial I'm sorry for our loss, this is kind of tragic

@danielbayerlein
Copy link

@KingRial Looks like the problem has been fixed with iOS 13.

@danburzo
Copy link

I still have issues with SW-powered websites not loading on iOS 13. I experience it daily on mobile.twitter.com and dev.to, for example. So, while it feels like iOS 13 brought some improvements, it has not fixed the infinite loading problem.

@KingRial
Copy link
Author

@danburzo I can confirm that iOS 13 has improved the situation but hasn't solved the main problem.
From the little I understood, I get the "inifinite loading" whenever I update my PWA and it exceeds the cache limit on iOS (which is 50Mb).

Usually it happens because each "service worker" has it's own life and it's own size.

For example, if you have a PWA of around 22Mb, and you install it and then update it for the first time, the problem doesn't occur (44Mb are lesser that the 50Mb limit)

But if you update the PWA a second time it seems you exceeds the cache limit because the first unused service worker wasn't cleaned by the OS (66Mb are bigger than 50Mb); in this case the OS kills the service worker's caches in a odd way and 90% of times nothing works until you clean the temporary files in the safari browser...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants