Questions

Hi everyone,

We run an enterprise operations app built on Median for iOS, used by field supervisors running shifts between 8 and 12 hours with background geolocation tracking active.

Recently, a field worker experienced a completely blank white screen on their iPhone towards the end of their shift. The native iOS status bar remained visible, but the entire web container went blank with no error screen and no automatic recovery. The user had to force-quit the app from the iOS app switcher and reopen it.

Because our web app's React Error Boundaries and window.onerror listeners did not catch anything, this appears to be an iOS WebKit process termination (webViewWebContentProcessDidTerminate:) caused by memory pressure after extended use.

I have a few questions for the community and Median team:

1. Does the Median iOS wrapper automatically handle webViewWebContentProcessDidTerminate:(WKWebView *)webView by reloading the page, or is there a setting we need to configure?
2. What are the best practices or recommended settings in the Median app builder for long-running apps with continuous GPS tracking to prevent WebProcess crashes?
3. Is enabling native Pull-to-Refresh the recommended fallback so users can recover the screen without having to kill the app?
4. Are there any native memory management flags or configurations available in Median for enterprise iOS builds?

Any guidance or shared experience would be greatly appreciated!