-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fatal signal with map in Activity #14001
Comments
Having the same problem |
I'm seeing that your are using both the LocationLayerPlugin in combination with v7.x of the Mapbox Maps SDK for Android. With 7.x we migrated this plugin to be part of the SDK as part of the LocationComponent. See our migration guide for more information here. Afaik this should solve the issue you are seeing, closing this issue as answered and please do reach out if this doesn't fix the crash. |
Thank you for answer @tobrun . We have not been using this plugin, I still get error on the same screen after removing it.
|
This is another error
|
Also got this type of error
|
Would you be able to provide an minimal reproducible example? I'm not able to reproduce with the information given. |
Actually it is complicated to provide you code, but i can describe flow. We have ShowTaskActivity where map layout is inflated on open. Switching to next tasks is held inside this activity. When next task is opened map clears and redraws corresponding data. Also we have a menu activity (ShowTaskList) from where user can switch to any other task, this is made by sending new intent to existing ShowTaskActivity, which handles it in onNewIntent method. After getting intent we re-add map layout and reinitialize all styles, layers, etc. |
Since you aren't able to give more information, I can only indicate that you are probably calling methods on Mapbox SDK components when you aren't allowed. You will have to debug which line at what time is triggering this crash. This can be a number of things as calling updates on sources/layers while the underlying style has been removed. or trying to update when the map isn't ready or .. Happy to look more and reopen if a minimal reproducible example can be provided. |
My problem was that I was reinitializing the map each time in the
|
@Pomis most important takeaways when trying to recreate the viewhiearchy you need to call the required lifecylce methods to stop/start rendering. Concretely when a view is being attached you will need to call:
When that view will be detached (before the actual detach)
When that view gets reattached
When that view can be disposed
|
i got this error Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6579616c in tid 25014 (FinalizerDaemon), pid 24997 |
Maybe if you provide a little bit more information, there will be higher chance to resolve your problem |
i previously used mapbox 6.5+ version. i got fatal signal error. they suggested upgrade version 7.+. so i just updated my mapbox lib project( navigation lib and navigationUI library) project. |
Steps to reproduce
Expected behavior
Actual behavior
App crashes with fatal signal 11.
Configuration
Android versions: 25, 28
Device models: Pixel 2 emulator, Nexus 5x emulator, Galaxy s9 (real device)
Mapbox SDK versions:
mapbox-sdk-services:4.3.0
mapbox-android-sdk:7.1.2
mapbox-android-plugin-locationlayer:0.7.0
mapbox-android-plugin-annotation-v7:0.5.0
All mapView lifecycle methods are being called including onDestroy.
The text was updated successfully, but these errors were encountered: