Closed ubipo closed 2 years ago
We moved from using Activity
to using Application
as the context for stuff that doesn't need a UI context (see AppContextSingletonDelegate.getValue()
).
As a result we're no longer using Activity.startActivity
in the thread default exception handler. The Application
context implementation (android.app.Instrumentation.execStartActivity()
) doesn't ever call cancelInputsAndStartExitTransition
so this bug can't occur anymore. Hooray.
Not immediately sure what went wrong here. Combination of the exception reporter activity and the element details taglist is pretty odd.
Stacktrace: