fix(bridge): Catch ObjC Exceptions and throw them to JS #1043
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.
ffi_call
s with @try-block(attaching the original native one as
nativeException
property)fix from Feature Request: support unwinding on iOS and OSX libffi/libffi#418
refs #1029
PR Checklist
What is the current behavior?
Objective-C exceptions in calls made from JS crash the application.
What is the new behavior?
Objective-C exceptions are intercepted by iOS Runtime and are thrown to JS, where they can be caught. If no catch handler is found they will be treated as unhandled JavaScript exceptions.