bugfix: deliver unhandled java exception reports before process death - #393
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
In the default configuration an unhandled Java exception report never left the device: the handler killed the process right after handing the exception to JS.
Changes
BacktraceAndroidBackgroundUnhandledExceptionHandler.java: blocks the crashing thread on aCountDownLatchuntil JS calls the newreportProcessedmethod, 5s cap, invokes the JS callback once, synchronizesuncaughtException.AndroidUnhandledExceptionHandler.ts: awaitsclient.send, callsreportProcessedfrom a finally, swallows a failed send.androidUnhandledExceptionHandlerTests.spec.ts: new, covers signalling native after a successful and a failed send, the error type, no start without the bridge, stop on dispose.ref: BT-7513