Symbolicating Crash Reports MapLibre Native (Android)

Note

For information on symbolicating iOS crash reports, see this page.

---

You may use tools like Firebase Crashlytics to gather crash reports from the field. These crashes may not be easily reproducible and happen only for a small number of users. Since stability has a very high priority, we still appreciate receiving crash reports of this kind.

We include debug symbols with every Android release.

You can use ndk-stack, a tool that comes with every Android NDK install, to symbolicate crash reports. For example with a tombstone from a device with the arm64-v8a architecture:

./sdk/ndk/26.1.10909125/ndk-stack -dump /Users/bart/Downloads/bugreport/FS/data/tombstones/tombstone_49 --sym debug-symbols/arm64-v8a/libmaplibre.so

You can also copy the stack trace from your logcat window (often easier if it's a crash during development) and save it in a file. Note that logcat hides stack traces in the default view (scoped to your package); you'll need to remove the filter to see the stack trace after your app crashes. Begin copying at the initial line of asterisks as noted in the Google documentation.