feat: add Expo Config Plugins to support Continuous Native Generation#577
Open
kota113 wants to merge 1 commit intogooglemaps:mainfrom
Open
feat: add Expo Config Plugins to support Continuous Native Generation#577kota113 wants to merge 1 commit intogooglemaps:mainfrom
kota113 wants to merge 1 commit intogooglemaps:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This PR adds several Expo config plugins that automate the native code changes required by the app.
Also, updated the document from Objective-C to Swift, since React Native has already migrated to Swift.
Motivation
These plugins support Expo’s Continuous Native Generation workflow by moving native customizations into versioned, repeatable configuration instead of requiring manual edits to the generated
iosandandroidprojects.This makes the native setup easier to maintain because the project can be regenerated with
npx expo prebuild, reducing native project drift, simplifying upgrades, and lowering the risk of orphaned native code when dependencies or features change.Issues
Pre-launch Checklist