App crashes with cryptic error #1253
Labels
bug 🪲
Something isn't working
Comments
|
@SamuelBrucksch thanks for the ticket, could you provide the full crash report so that we can symbolicate it from our side? Also would like to know the Android Maps SDK version that I tried to symbolicate the address using v10.3.0-rc.1's debug symbol, but it failed to resolve to meaningful line numbers. |
|
Hi @pengdev thanks for looking into this. Here are the mapbox related dependencies: Does it contain everything you need? @react-native-mapbox-gl/maps is 8.5.0 The related mapbox versions should be these: The error I pasted above is everything i can see. Unfortunately no other error or additional information available. |
|
Same issue here. com.mapbox.navigation:core:2.4.0-rc.1 Occurrences Last 30 days: 528 Another one : Android 7 We get a lot of bad reviews, 1 stars mentionning those crashes |
|
The crashes listed symbolicates to: Where you can see We are aware that this developer experience isn't great and we should check for crashes in these observable handlers and cleanly handle them (eg. rethrowing them on the java end without having the native trace crashing them). Will ticket this out. @SamuelBrucksch do you have other traces that I could try symbolizing? The one shared above didn't meet the requirements of ndk-stack to be resolved. |
Thank you, that would be great. We don't have the full stack trace when we get those native crashes on the Google Play platform unfortunately, si indeed we are missing the context unfortunately |
|
Hi, we still see errors like these. Newest ones on a Samsung Galaxy S22+ (SM-S906B) Android 12 API 31: Unfortunately not much more to share... When will #1363 be available? Maybe that helps in finding the problem... I asked the affected user to create a bugreport on android and send it to us, maybe it contains something more useful. Looks like he can reproduce this fairly easy, so maybe the bugreport contains the expected log output. |
|
Maybe related to #1397 in my case |
|
@tobrun just got this one: Does this contain anything useful? |
|
@SamuelBrucksch this one is great, it seems the device is unable to create the GL setup, we need to handle such cases more gracefully by 1) not crashing with a native crash 2) exposing a callback for developers to recover from this. One additional question Samuel, is do you have more context why the system wasn't able to create the GL setup? was it resource constrained? (eg. out of memory) or something else that might be interesting? |
|
No the user switched to another app and then back to our app in AA. I opened a seperate issue on that, as i saw this log only later, so i guess it is the same: #1397 I also found this one: Which describes a bit about the lifecycle and AA destroying the surface while leaving the app and recreates it when coming back. It has a similiar error, but i already checked your AA implementation again and we do the same with regards to calling onStop / onStart andf so on as far as i can see. Maybe we continue in #1397 as it seems to be more specific to the actual problem. |
|
So @tobrun about the better error handling... Is that something that could be added soon and helps in finding where the error occurs? |
|
@SamuelBrucksch #1363 has been released with 10.6.0-beta.1 thus will be available as part of the stable 10.6.0 (expected next week). At the same time seems it won't help with the EGL issue you're facing with AA, since 1363 only rethrows exception happening in the MapEvents callbacks |
|
Closing this ticket in favor of #1397 where the conversation is continued. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
we get following crash on bugsnag:
Unfortunately I can not reproduce on my Pixel 3 with Andropid 12, however it seems to be related to Pixel 5 and Pixel 4a on Android 12 only at the moment. We did not get reports for other phones and Android OS (yet).
We use mapbox sdk
10.3.0-rc.1for Android Auto, but also@react-native-mapbox-gl/mapson app side that is based on react native, so not really sure, from which side the error comes. Is there anything you can do to decode the exception and get more information where the error comes from?Thanks!
Samuel
The text was updated successfully, but these errors were encountered: