asterics
Android chrome app, pinned back button show Splash logo, can't move anywhere
Hello,
there is a "bug" when you use Grid as installed Chrome app and pin app to keep all the time on screen.
- open grid.asterics. in Chrome on android tablet
- Install Grid as chrome app
- pin the app to persist on screen
- open app, logo is shown, loading is shown, app is shown
- ~~switch app to Full screen mode~~ not needed
- swipe from bottom to show android navigation buttons
- use ◀️ android Back button fast many times (like my kid will try to go out of app)
- app stuck on Grid logo and nothing more happen. You are stucked on Splash screen of app and can't navigate anywhere.
This happen only when app is in Pinned mode. In standard usege (non-pinned) pressing ◀️ back button many times show Home screen.
I've tried it on Android 11, where I cannot reproduce it. I can use the back button as often as I want, but nothing happens in pinned mode. However after leaving pinned mode (long press of back button and entering the phone pin), the App is just a white screen and not usable anymore, I then have to close and re-open the app. But I think that's maybe another issue.
If you do it with another installed PWA (e.g. this one: https://whatpwacando.today/ ) - is it the same issue or not? For me with this PWA I have the same issue with the empty screen after coming back from pinned mode - so at least this issue seems to be an Android bug.
hmm, I can stuck on logo in PWA as well, so it's more related to PWA?
Android 13, Umidigi G1 Kids
Chrome: stuck on splashscreen / logo - but hard to get there (happen 2 or 3 times on beginnig and now can't reproduce anymore - so happen only sometimes, don't know steps which I do different to get to logo) Firefox: stuck on white screen - much easier to get there (all the time).
In Chrome it happen only sometime and you must click fast on back manytimes. In firefox it happen in 100% just by slow clicking back 2 or 3 times in PWA app.
When turn of screen and turn on again PWA app pinned: Chrome: PWA is in crash, only chrome toolbar visible and white screen, nothing work Firefox: recover and work
When turn of screen and turn on again PWA app NOT pinned: Chrome and FF recover without any issue and continue in work.
Grid app: When turn of screen and turn on again PWA app pinned is returned to expected screen (works better than PWA demo).
NOTE: I don't use lock screen on that tablet, no swipe needed after turn screen off/on, it start immediatelly again PWA app.
Main goal was create tablet as communicator only (all the time available), because in case, that kids can go to Homescreen it will start another apps and I want have one tablet dedicated only for communicator and nothing else. But it's required to stay on Grid (it will be provided to kindergarder, grandparents, etc). I'll try to find more precise info that/how to reproduce and try to report to ... have no idea yet :D (chrome / FF / android)...
I'm not able to use Firefox, because it has only online voice in Czech and it's super slow to say anything and require internet. So I'm stuck to use Chrome (Edge tested as well, but have online voice too). Chrome has offline voice which is much faster than online voices. I'll try some other browsers.
OK, so if you're experiencing similar problems with the PWA demo app and the behaviour is different between Firefox and Chrome, I assume that the bugs are browser-based. You could add a bug report to the Chromium bug tracker. I assume that using other browsers won't help, since all (except Firefox) are Chromium-based.
When turn of screen and turn on again PWA app NOT pinned: Chrome and FF recover without any issue and continue in work.
Maybe a temporary workaround is to use a browser or app, where it's possible to restrict it to a single page, namely grid.asterics.eu and then to pin this browser app. So not using the "installed" PWA version, but using AsTeRICS Grid in the normal browser, while restricting access to other pages and then pinning the browser app.
This seems to describe some possibilities how to restrict pages, but I don't have experience with it.
Someone already opened the issue for that on chromium: https://issues.chromium.org/issues/40746880
... 3 years ago 🙈🤷♂️🤦♂️
I've tested it on different devices as well, same on all devices. PWA stuck on splash screen.
Ok 🤦♂️
That's the bad thing of the PWA, that we're depending on the browser. However, it also has many advantages.
I'm closing the issue, because nothing we can do currently. Feel free to add new comments or issues if there is something new to discuss.