Symbols and mapping
Overview
Debug symbol files are generated for every build of your app, and they contain information about the original stack traces and the exact location of libraries and code lines for a particular build version.
These files later help developers symbolicate/deobfuscate the crash reports and error logs into a human-readable format. This helps to troubleshoot, identify, and debug issues faster by restoring original stack traces and mapping obfuscated symbols and code to the exact code lines. The debug symbol files vary for each platform:
Platform | Debug symbol file |
Android | ProGuard Mapping files |
Apple apps (iOS/iPadOS/watchOS/tvOS/vision OS) | dSYM files |
React Native | Source maps |
Flutter | Mapping files |
In Apptics, you can automatically upload, manage, and manually add any missing files for your apps across multiple platforms from the Symbols & mapping module. You need to enable automatic upload of dSYM/Mapping files while you configure crash reporting in the SDK.
For SDK implementation, refer to:
Upload debug symbols files manually
- Navigate to Quality > Symbols & Mapping. Select the type of debug symbol file and the application ID for which you want to upload from the drop-down menu.
- Click Upload and a popup will appear.
- Select the appropriate app version and build version from the drop down.
- Click on Choose file and select the .zip file (or .txt file for Android).
- Click Upload and the debug symbol file will be listed in the console.
- Once the dSYM file gets uploaded automatically or added manually, you can see the list of all the files along with details like file name, app version, build version, build UUID, Uploaded date and time, and status.
Manage debug symbol files
- Click on the edit icon to update the debug symbol file.
- You can download an uploaded debug symbol file or delete a file from here.