[Bug]: Black map / zero native initialisation on Android 15 (Pixel 9) with Expo SDK 54 + React Native 0.81 Environment:
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 2.9k
- Forks
- 947
- Avg merge
- 6d 37m
- Merged PRs (30d)
- 1
Description
Title:
@rnmapbox/maps versions tried: 10.2.10, 10.3.0, 10.3.1 (with RNMapboxMapsVersion 11.21.5)
React Native version: 0.81
Expo version: 54.0.35
Android device: Google Pixel 9
Android version: Android 15
New Architecture: tried both true and false
EAS Build: cloud build
What happens:
expo-font conflict resolved via package.json override "expo-font": "14.0.12" — FontLoaderModule crash fixed
Map view renders black
Neither onDidFinishLoadingStyle nor onDidFailLoadingMap fires
MapboxGL.Logger.setLogCallback callback never fires
Zero native output of any kind
Token confirmed valid, correct scopes, no URL restrictions
setAccessToken called in useEffect in App.tsx
surfaceView={true} tried — no difference
styleURL tried as both string and enum — no difference
What was tried:
newArchEnabled true and false
surfaceView true
Multiple SDK versions including v11.21.5
setAccessToken at module level and in useEffect
styleURL as string and as MapboxGL.StyleURL enum
expo-font override confirmed applied
Working state:
Previous build without @rnmapbox/maps runs perfectly on same device
react-native-maps works correctly on same device
Conclusion:
Mapbox GL native renderer is not initialising on Pixel 9 + Android 15. No error output of any kind. Zero native callbacks or logger output.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue from App.tsx on a Pixel 9 running Android 15 with Expo SDK 54, React Native 0.81, and the reported @rnmapbox/maps versions. Compare new-architecture settings, surfaceView, styleURL forms, and token placement as listed, then use the absence of native callbacks and logger output to narrow the failure. Done means the map renders normally and native loading callbacks or logging provide output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100