Add reference to react-native-maps upgrade#10
Open
eduardinni wants to merge 2 commits intoexpo:mainfrom
Open
Conversation
EvanBacon
reviewed
Jan 23, 2026
| - ./references/new-architecture.md -- SDK +53: New Architecture migration guide | ||
| - ./references/react-19.md -- SDK +54: React 19 changes (useContext → use, Context.Provider → Context, forwardRef removal) | ||
| - ./references/react-compiler.md -- SDK +54: React Compiler setup and migration guide | ||
| - ./references/react-native-maps.md -- SDK +54: react-native-maps Expo plug-in configuration |
Contributor
There was a problem hiding this comment.
Suggested change
| - ./references/react-native-maps.md -- SDK +54: react-native-maps Expo plug-in configuration | |
| - ./references/react-native-maps.md -- SDK +54: react-native-maps Config Plugin setup |
EvanBacon
reviewed
Jan 23, 2026
| - Remove implicit packages from `package.json`: `@babel/core`, `babel-preset-expo`, `expo-constants`. | ||
| - If the babel.config.js only contains 'babel-preset-expo', delete the file | ||
| - If the metro.config.js only contains expo defaults, delete the file | ||
| - Configure Expo plug-in for `react-native-maps` if the package is used by the app |
Contributor
There was a problem hiding this comment.
Suggested change
| - Configure Expo plug-in for `react-native-maps` if the package is used by the app |
Doesn't apply to every app
EvanBacon
reviewed
Jan 23, 2026
|
|
||
| Expo SDK 55 uses `react-native-maps` version 1.26.20+ | ||
|
|
||
| An Expo plug-in for `react-native-maps` was introduced in version 1.22 and it requires Expo SDK 53+ |
Contributor
There was a problem hiding this comment.
Suggested change
| An Expo plug-in for `react-native-maps` was introduced in version 1.22 and it requires Expo SDK 53+ | |
| `react-native-maps@1.22.0` now has an Expo Config Plugin (SDK 53+) |
EvanBacon
reviewed
Jan 23, 2026
Comment on lines
66
to
76
| ### Migration Steps | ||
|
|
||
| 1. Remove legacy configuration | ||
| 2. Add `react-native-maps` Expo plug-in configuration | ||
|
|
||
| ## Cleanup Checklist | ||
|
|
||
| When upgrading to SDK 55: | ||
|
|
||
| - [ ] Use `rect-native-maps` Expo plug-in | ||
| - [ ] Add Google Maps API keys for each platform in use |
Contributor
There was a problem hiding this comment.
Suggested change
| ### Migration Steps | |
| 1. Remove legacy configuration | |
| 2. Add `react-native-maps` Expo plug-in configuration | |
| ## Cleanup Checklist | |
| When upgrading to SDK 55: | |
| - [ ] Use `rect-native-maps` Expo plug-in | |
| - [ ] Add Google Maps API keys for each platform in use |
redundant
Author
There was a problem hiding this comment.
thanks for the review - pushed a commit that includes your suggestions and other minor changes
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.
Context
react-native-mapsuses Google Maps on iOS.react-native-mapsbuilt-in Expo plug-in.This housekeeping reference will take care of it, once
react-native-mapsExpo plug-in is fixed.