pulsejet
IOS Progressive Web App: Image Download breaks app
Describe the bug Using the newest IOS, when using Memories as a Progressive Web App, downloading an image opens a "Share" Dialogue from which I cannot go back to the timeline view. See the second pic: there are no navigation bars to go back. I need to completely close the task and restart the app to get back to the timeline view.
Steps to reproduce the behavior:
- Using Safari on IOS, add Memories to Homescreen as a Progressive Web App.
- Click on any image and using the context menu, click on download.
- IOS opens sharing screen with no possibility to return to previous page.
Screenshots If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
- OS: iOS
- Browser Safari as Web App
I am seeing this too on iPhone 13 Pro. I am not really sure how to debug this so I went to my nginx logs and there is one 404 every time this download screen shows up. The rest looks fine - all 200s.
MyIP - - [20/Apr/2023:20:49:24 +0200] "GET /apps/memories/js/memories-node_modules_nextcloud_vue_dist_Components_NcNoteCard_js.js.map?v=fce34ecd7bfa96bc891c HTTP/2.0" 404 4093 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 16_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Mobile/15E148 Safari/604.1"
MyIP - - [20/Apr/2023:20:50:20 +0200] "GET /apps/memories/js/memories-node_modules_nextcloud_vue_dist_Components_NcNoteCard_js.js.map?v=fce34ecd7bfa96bc891c HTTP/2.0" 404 4091 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 16_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Mobile/15E148 Safari/604.1"
I am also not that much familiar with iOS so I am not entirely sure that it is not a "feature" of iOS.
Progressive Web App in iOS is the ultimate way to access memories on an iPhone. User experience wise, makes the webpage feel like an actual app.
Apparently PhotoPrism had the problem and was able to fix it. https://github.com/photoprism/photoprism/issues/895
It looks like they enabled browser controls when the download button was hit, so the user could then access the back button.
It doesn't necessarily solve how to implement the solution, merely what the solution should/could look like inside the constraints of Apple's Progressive Web App. Hope this helps!
