You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
importReactfrom'react';import{Text,View}from'react-native';import{Camera,LocationPuck,MapView,MarkerView}from'@rnmapbox/maps';exportdefaultfunctionRNMapboxMarkerViewScreen(){constlocation=[0,0];// change this to reproducereturn(<MapViewprojection="mercator"style={{flex: 1}}><CameracenterCoordinate={location}zoomLevel={10}animationDuration={0}/><LocationPuckvisible={true}puckBearingEnabledpuckBearing="heading"/><MarkerViewid="mv"coordinate={location}><Viewstyle={{padding: 20,backgroundColor: '#FFF',}}><Text>Marker View</Text></View></MarkerView></MapView>);}
Observed behavior and steps to reproduce
We're seeing MarkerView's hiding from the map anytime they collide with the user's LocationPuck. Having the LocationPuck mounted but with visible={false} makes the MarkerView behave correctly.
ScreenRecording_06-28-2026.22-01-47_1.MP4
Expected behavior
The MarkerView's should stay visible and render on top of the user's LocationPuck.
Notes / preliminary analysis
This only happens on iOS with the new architecture and @rnmapbox 10.3.X. We have not seen this issue on 10.1.X with Mapbox V11, and we're unsure if this bug exists in 10.2.X. This occurs in both standalone React Native apps and Expo apps.
Mapbox Version
11.20.1
React Native Version
0.79.1
Platform
iOS
@rnmapbox/mapsversion10.3.0-rc.0
Standalone component to reproduce
Observed behavior and steps to reproduce
We're seeing MarkerView's hiding from the map anytime they collide with the user's LocationPuck. Having the LocationPuck mounted but with
visible={false}makes the MarkerView behave correctly.ScreenRecording_06-28-2026.22-01-47_1.MP4
Expected behavior
The MarkerView's should stay visible and render on top of the user's LocationPuck.
Notes / preliminary analysis
This only happens on iOS with the new architecture and @rnmapbox 10.3.X. We have not seen this issue on 10.1.X with Mapbox V11, and we're unsure if this bug exists in 10.2.X. This occurs in both standalone React Native apps and Expo apps.
Additional links and references
No response