Web Lifecycle
Lock and reset behaviour, network and server-error recovery, refresh on screen wake
1. Lock on Launch
When enabled, the app will immediately enter locked/pinned mode on startup, preventing exit until unpinned.
On some devices, you may still be prompted with a confirmation screen.
Default: false
2. Reset on Launch
When enabled, the app will always start fresh at the Home URL when closed and re-opened, as opposed to the last visited URL.
The navigation history will also be cleared.
Default: false
3. Reset On Inactivity (seconds)
Number of seconds of inactivity before the app resets to the home URL.
When there is 5 seconds left, a warning countdown will be shown on the screen. User interactions with the screen reset the timer.
The navigation history is cleared when History is selected under
Reset Actions (enabled by default).
To disable, use the value 0.
Minimum: 10
Default: 0
4. Reset Actions
Choose which browsing data to clear when the inactivity timer resets the app
to the Home URL. Use Add to select more actions, remove any unwanted actions,
or drag the handle at the end of a row to rearrange them.
The app returns to the Home URL even if no actions are selected.
| Action | Description |
|---|---|
| History | Clears the browsing history and back/forward navigation history. |
| Cookies | Removes all WebView cookies, including login sessions. |
| Web Storage | Deletes HTML5 website storage, including localStorage and IndexedDB. |
| Cache | Clears cached website resources from disk. |
| Form Data | Clears saved WebView form entries on older Android versions. |
| SSL Preferences | Clears remembered SSL certificate decisions. |
| Recreate WebView | Replaces the current WebView to end the in-memory page session. |
Form Data
This action does not remove saved entries from Android's autofill service.
Selected cleanup actions run in the configured order. Recreate WebView
always runs after the other actions, before loading the Home URL.
Cookies and Web Storage are shared across websites in the app. Clearing them may sign you out of multiple websites. App settings, bookmarks, and local files are not removed.
Default:
["HISTORY"]5. Dim Screen On Inactivity (seconds)
Number of seconds of inactivity before the screen is dimmed (brightness = 0).
This will set the app brightness to 0, and will restore the brightness to
your device -> brightness setting upon new user interactions.
Minimum: 10
Default: 0
6. Refresh on Network Available
Select when the page should automatically refresh when network connectivity is restored.
- Always: refresh whenever a network connection is available
- On Page Error: only refresh if the previous page load failed
- Never: do not refresh automatically
Default: On Page Error
7. Refresh on Loading Error Interval (seconds)
Interval in seconds between automatic refresh attempts when a page fails to load. This usually indicates a connection failure, such as when the device is offline or the server is unavailable. On Android 6 and newer, main-page HTTP 5xx responses (such as 500, 502 and 503) also trigger retries. HTTP 4xx responses, including 401, 403 and 404, do not trigger retries. Failed images, scripts and iframes do not trigger a page refresh.
This is detected using the Android API:
WebViewClient#onReceivedError
in conjunction with
WebResourceRequest#isForMainFrame.
HTTP server errors are detected using
WebViewClient#onReceivedHttpError.
These errors also count as page errors for Refresh on Network Available.
Retries honour URL restrictions. The server's response remains visible until the next attempt; a successful new load or navigation to another page clears the error. On Android 5, connection-error recovery continues to work, but HTTP status recovery is unavailable.
To disable, use the value 0.
Minimum: 5
Default: 0
8. Refresh on Screen Wake
Refresh the current page once when the device wakes from sleep. The kiosk page must be in the foreground before and after sleep.
Default: false
Last updated on