React Native test scenarios for synchronous native exceptions #2530
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
gingerbenw
approved these changes
Aug 21, 2025
yousif-bugsnag
deleted the
PLAT-14049/synchronous-native-exception-tests
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Goal
Previously all of the React Native scenarios that trigger native exceptions did so via an async turbo module method. This PR updates the test runner to support running native scenarios synchronously, and adds a new separate scenario to test native errors in synchronous turbo module methods.
Design
Native scenarios can implement a
runSyncmethod to allow them to be executed synchronously - the new scenario just callsrunSyncon the same native scenario (UnhandledNativeErrorScenario)Testing
Covered by CI