Closed ndegwamartin closed 2 months ago
Any thoughts on how to reproduce this?
We experienced something similar when working on WDF with @Rkareko. In our case, this line seemed to have been the culprit
Anytime an error occurred it didn't throw but killed the process
oh nice catch! that seems very suspicious can remove that init block? that looks like the only place we call setDefaultUncaughtExceptionHandler
Describe the Issue It has been observed that sometimes the app crashes or silently fails without any Logs displayed in std out during development or Sentry for releases. Some investigations pointed to the exceptions thrown within Coroutine scopes somehow 'disappearing' .
We want to troubleshoot further and come up with a better error handling solution in this context.