-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Crash on NativeMapView create with React Native #7587
Comments
Just wanted to clarify, the title of the issue referenced above is misleading - this is still an issue we're having. There has been no change or PR to react-native-mapbox-gl that resolves it. |
I symbolicated the crash log from 4.2.2 - anyone has an idea what could solve this? It's also present in 4.2.2 cc: @tobrun |
I'm still stuck with this... i've no idea how to proceed debugging this and it's by far the largest crash i'm experiencing. Can u give me a hint how to proceed @tobrun? |
Anybody found anything on this? This is still a huge blocker for android with react native mapbox. |
I was able to reproduce the crash shown in the OP and debugged it to the mbgl::Map creation. I'm now trying to migrate to a 5.0.0 version of the SDK and see if that resolves the issue. |
Hitting:
this symbolicates to:
|
The symbolicated stack trace is nonsense, e.g. there's no way that |
@jfirebaugh thank you for 👀 , I thought it would be valid to build the release tag and use that with ndk-stack. As you point out the addresses don't match, though this has given me the indication that something is wrong with the thread we are loading the native library with. After making sure that the library is loaded on the main thread, I'm not seeing the crashes anymore. Currently still seeing a blank map. Working now on resolving this. |
Crash has been identified, I created a ticket downstream covering all the requirements to update the react-native module to the latest Android SDK in nitaliano/react-native-mapbox-gl#516. Closing as resolved. |
I'm using this library through the react-native-mapbox-gl repo, and I'm attempting to upgrade to version 4.2.x (the repo still uses 4.1.1). Everything goes fine if I upgrade to 4.2.0-beta.3, but starting with 4.2.0-beta.4, my app crashes as soon as the
MapView
component mounts. I have reproduced this minimally using the test app provided in the react-native-mapbox-gl repo, which I've forked and provided instructions for below, in case anyone wants to try reproducing this themselves.I'm aware this is likely an issue in the react native component repo and how it handles the
MapView
lifecycle, but I'm unsure where to begin looking. Any insight into what might have changed between SDK betas 3 and 4 would be extremely helpful.Thanks very much!
Platform: Android
Mapbox SDK version: 4.2.0-beta.4 or later, including stable releases
Steps to trigger behavior
index.android.js
npm
/yarn install
node_modules/react-native-mapbox-gl/android/build.gradle
to require mapbox SDK version 4.2.0-beta.4 (or later) [note: the project should run fine if you instead require 4.2.0-beta.3]react-native run-android
Expected behavior
Map is mounted and app is usable
Actual behavior
App crashes with the following log
The text was updated successfully, but these errors were encountered: