pwa-police / pwa-bugs Goto Github PK

On iOS 12 when PWA is in "standalone" mode (installed) there is no way to correctly handle the "mailto:" link

<a href="mailto:[email protected]">test[dot]com</a>
<a href="mailto:[email protected]" target="_blank">test[dot]com</a<

The only workaround found is to add a click event handler similar to:

()=>{
    window.location.href = "mailto:[email protected]?subject=" + emailSubject + "&body=" + emailBody
    return
}

On iOS 13 the standard usage works correctly.

Is there still no workaround for this issue in iOS 12.1?

"Problem: in iOS 12 cache in Cache Storage magically disappears"

or

“Safari and the home screen shortcut share the same Service Worker registration (but not the instance) and the cached files. Safari View Controller (such as the In-App Browser within Twitter) supports Service Workers and the cache but it seems it’s deleting all the data after the session is closed.”

:_(

Bluetooth and Wifi is off but it still doesn't appear. If I switch to light mode it works.

Hi, I found an error with input type file with caputre="camera"
Steps to reprodue:
open app,
click input,
do not create photo and close app.
Open app again
You cannot use input again
It started with ios 12.2 update (saving state of app), didn't notice it on android.

iOS PWA does't support icons from manifest.json. The solution is to add link apple-touch-icon with different sizes.

Example:
<link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon.png">

The solution in the doc doesn't seem complete. This article with examples shows how to do it properly.

Sorry, right now don't have time to PR. Maybe someone do it faster than me

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

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

The problem is decribed in the article
After iOs 12.2:

PWAs have a new lifecycle and on most normal situations, the state of your app will be saved and restored between sessions, but there is no way to kill the PWA and restart it from scratch.

That is actually quite a nasty problem when you need to unload the app and to launch fresh one again. You just can't -)

There is not very consistent workaround: exit the app, and try to load some other "PWA" or even just some site in Safari. Often it leads to unloading target "PWA" from memory. Though I believe it depends on available resources.