mapbox-maps-android
mapbox-maps-android copied to clipboard
Fatal Exception: java.lang.Error unordered_map::at: key not found
Fatal Exception: java.lang.Error unordered_map::at: key not found com.mapbox.maps.Map.render (Map.java) com.mapbox.maps.NativeMapImpl.render (NativeMapImpl.java:2) com.mapbox.maps.renderer.MapboxRenderer.render (MapboxRenderer.java:5) com.mapbox.maps.renderer.MapboxRenderThread.draw (MapboxRenderThread.java:77) com.mapbox.maps.renderer.MapboxRenderThread.doFrame (MapboxRenderThread.java:10)
**Mapbox Navigation SDK version:**com.mapbox.navigation:android:2.6.0-rc.2
I am having this Crash showing up in my Crashlytics
@BenCooke can you please provide the following information so we can investigate this behavior:
- When are you receiving this crash?
- Is this a consistent crash or does it happen intermittently?
- What version and which SDK are you running?
Hello,
This is an intermittent crash while the Map is on screen Using Mapbox Navigation SDK version: 2.6.0 Another stack trace Fatal Exception: java.lang.Error: unordered_map::at: key not found at com.mapbox.maps.Map.render(Map.java) at com.mapbox.maps.NativeMapImpl.render(NativeMapImpl.java:2) at com.mapbox.maps.renderer.MapboxRenderer.render(MapboxRenderer.java:5) at com.mapbox.maps.renderer.MapboxRenderThread.draw(MapboxRenderThread.java:77) at com.mapbox.maps.renderer.MapboxRenderThread.doFrame(MapboxRenderThread.java:10) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1035) at android.view.Choreographer.doCallbacks(Choreographer.java:845) at android.view.Choreographer.doFrame(Choreographer.java:775) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1022) at android.os.Handler.handleCallback(Handler.java:938) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.os.HandlerThread.run(HandlerThread.java:67)
@BenCooke to help the team investigate this issue further, can you please provide a minimal test case that reproduces this behavior.
Closing this ticket, but please feel free to reopen if the issue persists.