[PLAT-11900] Move BugsnagReactNative from objective-c to objective c++ #2113
Conversation
This file contains 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
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
Fixes an iOS build error in React Native when New Architecture is enabled (reported in #2101).
A fix introduced in React Native 0.73.5 (and backported to 0.72.12) ensures that the
RCT_NEW_ARCH_ENABLEDflag is now passed down to libraries where it was not previously (facebook/react-native#43088). This means that anything imports the generated spec header must be Objective-C++.Design
Moved
BugsnagReactNativefrom Objective-C to Objective-C++.Testing
Upgraded the React Native 0.72 test fixture to 0.72.12 which contains the aforementioned fix.