Bugsnag does not report All types of metadata for native crashes about bugsnag-android

[mattdyoung]

Hi @pavlos-lyft

Currently for native NDK crashes the only types of metadata which are supported are boolean, number, and string values. Although more complex metadata types such as List and Map can be added to JVM crashes, this metadata won't appear on NDK crashes.

We do have plans on our roadmap to support more complex metadata types on NDK crashes as well, but there is significant work to support this reliably across all cases and ensure that metadata added or modified in either layer is included in all crashes. We don't have a planned timeline for this yet but we'll be sure to provide an update here when this becomes available.

The most common use case for adding List metadata to crashes is to provide sets of feature flags or experiments active when the crash occurred. This is now supported by bugsnag-android using the addFeatureFlags API, and although feature flags / experiments can only be added in JVM code they will be included on all errors including native NDK crashes.

[luke-belton]

Hi @pavlos-lyft - just letting you know that we've released v5.24.0 of bugsnag-android, which includes some enhancements to now allow reporting of complex metadata (including Lists and Maps) on NDK crashes 🎉