Repository navigation
fix: build under React Native 0.89's RN_STRICT_API - #2025
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This branch was previously deployed
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
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.
React Native 0.89 lets apps turn on its C++ stable API guards with
RN_STRICT_API=1 pod installor GradlestrictCxxApiEnabled=true, which defineRN_STRICT_APIfor every pod and Android library.Under it, a direct include of a private header or of a header that has a
<React/...>umbrella is a hard#error, and Nitro hits both, so no app using Nitro can opt in today. This branch includes those headers through the umbrellas when they exist and keeps the current includes on older React Native.I tested following scenarios: