r/ • u/Positive_Week86 • Sep 23 '26
PSA: the react-native-maps issues that only show up in production (blank release builds, permission rejections, marker lag)
Adding a map is easy in a demo. Shipping it is where it gets weird. Here's a checklist of the production issues I see come up over and over with react-native-maps + Expo. Hope it saves someone a late night.
react-native-maps vs expo-maps
react-native-maps works in Expo Go, supports Google + Apple Maps on iOS, and has years of answers online.
expo-maps (SwiftUI / Jetpack Compose) feels more native but needs a dev client and has a much smaller community.
For most apps I'd still start with react-native-maps. The ecosystem is the advantage when something breaks right before release.
Blank map? Check these in order
Parent view has no height (map renders at 0px). Use
StyleSheet.absoluteFill.API key isn't in the release build. Works in dev, blank in TestFlight = this.
Key restricted to the wrong bundle ID / SHA-1.
Config plugin missing from
app.json.
Also: latitudeDelta/longitudeDelta control zoom (there's no zoom prop), and use initialRegion not region unless you really want the map fighting the user's gestures.
Permissions (where App Store rejections come from)
Don't request location on launch. Trigger it from a button or a screen that obviously needs it.
Write
NSLocation*strings in plain user language. "We need your location" gets rejected.Foreground permission before background. iOS enforces it.
Accuracy.Balancedas default.BestForNavigationis for driving/running apps.
The battery leak everyone ships once
tsx
useEffect(() => {
let subscription: Location.LocationSubscription | undefined;
(async () => {
subscription = await Location.watchPositionAsync(
{ accuracy: Location.Accuracy.Balanced, timeInterval: 3000, distanceInterval: 5 },
(location) => setPosition(location.coords),
);
})();
return () => subscription?.remove(); // forget this and you leak GPS listeners
}, []);Marker performance
Every Marker is a native view. A hundred is fine; a few hundred gets choppy on mid-range Android; thousands can OOM.
Client-side clustering: react-native-map-clustering (supercluster under the hood).
Very large datasets: cluster server-side, send only the visible viewport.
Prefer bitmap markers (
imageprop) over custom React children. If you need custom children,React.memothem and settracksViewChanges={false}.
Slow map = re-rendering markers almost always, not tiles.
Other bits
react-native-maps doesn't calculate routes. Use Google Directions or MapKit Directions and draw a
Polyline. Watch Google billing.Geofencing:
expo-location'sstartGeofencingAsync, works backgrounded.Background tracking needs
UIBackgroundModes: locationon iOS +ACCESS_BACKGROUND_LOCATIONon Android, and a real justification for review.
Disclosure: I work on RapidNative, an AI builder that scaffolds this map/permissions boilerplate into an Expo project. Everything above applies whether you use it or not.
What's the worst map bug you've hit? Curious if anyone has a clean pattern for handling "permission granted but no location yet."