Add new architecture support #2033
Open
+16,588
−110
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
|
looking forward to this landing and getting us one step closer to new arch support in the ecosystem! @ivpusic any chance you could merge this and get it into a new release, so that we can include it in a list of libraries supported in the new arch for react-native 74? |
|
@ivpusic - any chance you can land this? |
|
Is this PR still mergable or is it stale? |
|
Can this please get merged? Preventing us from updating to RN 76 |
|
@ivpusic Any ETA on getting this merged? |
|
Would love this! |
|
Please merge this one.. Needed |
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.
Adds support for the new architecture with bridgeless enabled which will be the default in 0.74
Tested on
Note: On Android,onActivityResultwas not implemented in RN 0.74 RC2 on bridgeless. It will be added in RC3. I have already tested against this change and it works as expectedIssues have been resolved in RC3 and now everything works correctly