Unhandled runtime error when leaving an app open overnight

[mark.breuss]

Hi All,

I often see that a browser window that is left open over night raises an uhandled runtime error after some time. Since our users do that a lot we received quite some bug reports because of that.

To me it seems to be an issue of anvils websocket connections:

We have “solved” it, by overriding the errorhandling for production and catching those errors and handle unhandled runtime errors differntly. However this doesn’t feel clean as we could potentially be overlooking important unhandled rt errors.

Mark

[mark.breuss]

Any update from Anvil central on this?
We are seeing this specific error on several places, especially in offline cases.

This is very annoying for us and any update would be greatly appreciated.

[mark.breuss]

Update: We are still seeing those errors pop up in the applogs.

It is a combination of offline/online and session expired which causes this error.

[Aaron]

Hi,
we experience this ‘Unhandled runtime error’ as well.
Strangley only with mobile phones, not from desktop.
How can we handle the Unhandled?
Cheers Aaron

[eli-anvil]

Hi all,

@meredydd has some advice here on catching these kinds of errors for more detailed logs:

"Unknown error" likely related to ByteDance WebView (TikTok)

The first question, of course, is whether this is an error you can reproduce for yourselves (with your own TikTok app). If so, the rest of this gets much easier; if not, you’re going to have to rely more on logging and writing custom error handlers to collect this information in the wild. (If you do this, I would advise testing your error handling code carefully - including with artificial JS errors, eg raised from native libraries or from the browser console.) So, here are some strategies for …

It sounds like @mark.breuss has already got custom error handlers in place, which should hopefully make this process easier - if you’ve already got this kind of debug info, please let us know so we can help track the problem down!

[mark.breuss]

Hi @eli-anvil,

thanks for the follow up!
Just added the original error stack trace to the next release.

Interested to see what it uncovers.
will report back.

-Mark