We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Mapbox
deafult
0.76.7
Android
@rnmapbox/maps
10.1.37
// App.tsx import React from "react"; import { View } from "react-native"; import { MapView } from "@rnmapbox/maps"; export default function App() { return ( <View style={{ flex: 1 }}> <MapView style={{ flex: 1 }} /> </View> ); }
When using @rnmapbox/maps together with React Navigation in an Expo app, the application fails to load with native module resolution errors.
This basic implementation works correctly:
{ "dependencies": { "@rnmapbox/maps": "^10.1.37", "expo": "~52.0.37", "react": "18.3.1", "react-native": "0.76.7" } }
Adding React Navigation causes the app to fail:
// App.tsx import React from "react"; import { NavigationContainer } from "@react-navigation/native"; import { createNativeStackNavigator } from "@react-navigation/native-stack"; import { View } from "react-native"; import { MapView } from "@rnmapbox/maps"; const Stack = createNativeStackNavigator(); function MapScreen() { return ( <View style={{ flex: 1 }}> <MapView style={{ flex: 1 }} /> </View> ); } export default function App() { return ( <NavigationContainer> <Stack.Navigator> <Stack.Screen name="Map" component={MapScreen} /> </Stack.Navigator> </NavigationContainer> ); }
{ "dependencies": { "@react-navigation/native": "^7.0.15", "@react-navigation/native-stack": "^7.2.1", "@rnmapbox/maps": "^10.1.37", "expo": "~52.0.37", "react": "18.3.1", "react-native": "0.76.7" } }
There was a problem loading the project. This development build encountered the following error: ViewManagerResolver returned null for either RNSScreenStackHeaderConfig or RCTRNSScreenStackHeaderConfig, missing names are: RCTSafeAreaView, RNMBXVectorSource, AndroidProgressBar, RNMBXAtmosphere, RNMBXStyleImport, RNMBXRasterDemSource, RNCSafeAreaView, AutoLayoutView, RNMBXTerrain, AndroidSwitch, RNMBXPointAnnotation, RNMBXRasterLayer, RNMBXSkyLayer, RNCSafeAreaProvider, RNMBXSymbolLayer, RNMBXMapView, RNMBXShapeSource, RNMBXImage, RNMBXCallout, RNMBXLocationProvider, UnimplementedNativeView, RNMBXLight, AndroidDrawerLayout, RNCAndroidDialogPicker, RNMBXCircleLayer, AndroidTextInput, RNMBXLineLayer, RNMBXHeatmapLayer, RNMBXImageSource, DebuggingOverlay, RNMBXMarkerViewContent, RNMBXBackgroundLayer, AndroidHorizontalScrollView, RNMBXNativeUserLocation, RCTText, RNMBXModelLayer, AndroidHorizontalScrollContentView, RNMBXRasterSource, RNMBXFillLayer, RNMBXFillExtrusionLayer, RCTView, CellContainer, RNMBXImages.
When setting "newArchEnabled": false in app.json, the error changes to:
"newArchEnabled": false
No ViewManager found for class RNSScreeContentWrapper
npm install @rnmapbox/maps @react-navigation/native @react-navigation/native-stack
npx expo prebuild --clean npx expo run:android
The map should render within the React Navigation stack screen.
The app fails to load with native module resolution errors.
Similar problems have been reported recently in this others issues: #3666 #3681 #3756
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Mapbox Implementation
Mapbox
Mapbox Version
deafult
React Native Version
0.76.7
Platform
Android
@rnmapbox/maps
version10.1.37
Standalone component to reproduce
Observed behavior and steps to reproduce
Description
When using @rnmapbox/maps together with React Navigation in an Expo app, the application fails to load with native module resolution errors.
Working Example (Vanilla Mapbox)
This basic implementation works correctly:
package.json - working
Non-working Example (With React Navigation)
Adding React Navigation causes the app to fail:
package.json - non-working
Error Message
When setting
"newArchEnabled": false
in app.json, the error changes to:Steps to Reproduce
Expected behavior
Expected Behavior
The map should render within the React Navigation stack screen.
Actual Behavior
The app fails to load with native module resolution errors.
Notes / preliminary analysis
Environment
Additional links and references
Similar problems have been reported recently in this others issues:
#3666 #3681 #3756
The text was updated successfully, but these errors were encountered: