You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like service workers are cloned when installing a PWA with Safari, thus it would be possible to store authentication info in the Cache and make use of it on the first start of the PWA. However, there is no documentation on Safari PWAs and how the isolation is supposed to work, so I am rather hesitant to go down this road.
As a side note, in addition to the problems above, some apps open URLs in a SFSafariViewController, which is also isolated. For example see Telegram iOS.
After opening a link to a shared list, it is not available on the start page of the Safari PWA.
How to reproduce:
Share > Add to Home Screen...
Create new list > Simple list
Share...
for example via MessengerA (poor) workaround for now would be to bookmark Listling (
Share > Bookmark...
) instead of installing the PWA (Share > Add to Home Screen...
).The text was updated successfully, but these errors were encountered: