Post

Replies

Boosts

Views

Activity

Reply to PWA in Safari A2HS iPad breaks if opening a link and return to the PWA app
New information: My PWA runs fine a day later after a fresh reboot..no issue after opening a link from within my PWA then returning to the PWA. But then "later in the day" it seems to get corrupted again if opening a link then returning to the PWA. Its almost as though indexedDB storage memory gets corrupted by the opened link? Is indexedDB memory not isolated from the rest of Safari browser memory..or is it all shared? This did not seem to be a problem in earlier versions prior to iOS14.6? I am currently running iOS14.7.1 on an iPad Pro 9.7". My PWA also runs with no issues in the Edge browser…except Edge for iOS does not have a A2HS option! So might this be a bug in the latest Safari or I am afraid more likely a bug in my code but I am at a loss as to how to fix it. I suspect a javascript Alert function might play a part? My code also uses an indexedDB function to fetch the current database files in Safari indexedDB storage. But why does my code work most of the time and why does it work everytime in Edge? Any one experienced similar problems. How well does Safari iOS support PWAs? Any suggestion or work around would be much appreciated! Thank you for reading this!
Aug ’21
Reply to Safari iOS PWA breaks if opening an external link and then returning to my PWA
New information: My PWA runs fine a day later after a fresh reboot..no issue after opening a link from within my PWA then returning to the PWA. But then "later in the day" it seems to get corrupted again if opening a link then returning to the PWA. Its almost as though indexedDB storage memory gets corrupted by the opened link? Is indexedDB memory not isolated from the rest of Safari browser memory..or is it all shared? This did not seem to be a problem in earlier versions prior to iOS14.6? I am currently running iOS14.7.1 on an iPad Pro 9.7". My PWA also runs with no issues in the Edge browser…except Edge for iOS does not have a A2HS option! So might this be a bug in the latest Safari or I am afraid more likely a bug in my code but I am at a loss as to how to fix it. I suspect a javascript Alert function might play a part? My code also uses an indexedDB function to fetch the current database files in Safari indexedDB storage. But why does my code work most of the time and why does it work everytime in Edge? Any one experienced similar problems. How well does Safari iOS support PWAs? Any suggestion or work around would be much appreciated! Thank you for reading this!— DougieBase 23 hours ago
Aug ’21