BugSnag is now Insight Hub - we're making some changes to how the product looks, but this won't impact the way you use BugSnag or any of your integrations.
Showing full stacktraces
BugSnag supports unminifying and demangling stacktraces using ProGuard files, NDK mapping files and LLVM debug symbol files (dSYMs) to show a full stacktrace with methods, file paths, and line numbers for errors.
Android ProGuard and NDK mappings
Follow the Android Showing full stacktraces guide for instructions on uploading ProGuard and NDK mappings from your Android builds.
iOS debug symbol files (dSYMs)
For Shipping builds of your application, you will need to upload dSYM files to BugSnag in order for stack traces to show file, line and function information.
To generate the necessary symbol files, we recommend enabling both
- “Generate dSYM file for code debugging and profiling” (
bGeneratedSYMFile) and - “Generate dSYM bundle for third party crash tools” (
bGeneratedSYMBundle)
in Project Settings → Platforms → iOS → Build (or in your Config/DefaultEngine.ini file).
After completing each app build, a dSYM bundle will be generated in the Binaries/IOS folder. We recommend using the BugSnag CLI to upload these files to BugSnag.
With the default settings, Shipping builds will generate a non-bundled dSYM file — the same result as when bGeneratedSYMFile is enabled but bGeneratedSYMBundle is not. This file is in fact the DWARF information that BugSnag requires for symbolication.
macOS debug symbol files (dSYMs)
For Shipping builds of your application, you will need to upload dSYM files to BugSnag in order for stack traces to show file, line and function information.
After completing each app build, a dSYM file will be generated in the Binaries/Mac folder as long as bDisableDebugInfo has not been set to true in your target file (.Target.cs)
This file can then be uploaded to BugSnag using the BugSnag CLI.
Further reading
For further information see our iOS or macOS symbolication guides.