Yes, as Sam mentioned, I am still working on this. A beta version of the app is up but it hasn’t yet passed Apple’s beta review, will post the link here when it does.
My current understanding is that this happens when iOS terminates the webview (to reclaim memory, for example) but doesn’t terminate the rest of the app. In that scenario, the app is left in an odd state where its internal navigation is still in the webview route but the webview itself is terminated.
In the upcoming beta, I have added a way to dismiss the route when the webViewWebContentProcessDidTerminate hook is invoked. There are reports that this hook isn’t reliably hit when the app is in the background, and the original issue is very hard to reproduce at will, so, let’s hope and see.