The Fully Kiosk Browser is crashing. Why?
If the Fully Kiosk app disappears randomly, it may be crashing or being killed by the Android OS. 99% of such issues originate from Android Webview, which still has tons of known bugs (e.g., known memory leaks when using CSS animations). ANR (application not responding) issues are also possible. These issues are usually related to a specific website and Android hardware combination.
The Android Webview can crash after some time or cause ANRs because of website complexity and resource usage, which we unfortunately can’t catch. You can try running a simple page like www.google.com. If the Fully Kiosk Browser doesn’t crash anymore, then that’s 100% a Webview issue. Crashes like this can start and stop because of updates on the particular website or Android Webview updates. You can only prevent these crashes by upgrading/downgrading the Webview or simplifying your website. In many cases, the issue is also related to the device hardware; changing the device type can help.
If Fully Kiosk suddenly started crashing on each app start it could be introduced by a buggy Webview update like that in March 2021. We recommend disabling Webview/Chrome auto-updates once tested to avoid such risks. Please use device provisioning to be able to remote update the Webview manually when needed.
Make sure these options in Other Settings are enabled to try automatic app restart after it stops: Restart Fully After Crash, Restart Fully After Update, Run as Priority App. The Fully Kiosk restart mechanisms work best if Keep Screen On and Kiosk Mode are enabled. Note that we can’t guarantee a restart in some cases because our app is a non-system app and can’t override the power of the Android OS.
When Fully Kiosk automatically restarts after a crash, there is a log entry. Check the Fully Log in Remote Admin. If you want to know exactly what is causing the crash, you can get and analyze a bug report just after the crash on your device. If you can’t make a bug report immediately after the crash, you can connect your device to the PC and continuously record Logcat using ADB tools and a command like /path/to/adb logcat >logcat.txt, then analyze the resulting file.