Skip to main content
Version: 1.0.0

Release Build

  • Exclude log() API from execution in release builds to avoid unnecessary debug data in production.

When preparing your application for release, it is critical to back up the dSYM file. This file is required to symbolicate crash reports and make them readable in the Appxiom dashboard.

  • Always save the dSYM file generated during the build process.
  • Symbolication allows you to trace crashes back to your source code for faster debugging.
  • For detailed instructions, see Locating dSYM file.

Best Practices​

  • Automate dSYM backup as part of your release pipeline.
  • Store dSYM files securely and organize them by app version/build number.
  • Test crash reporting in a staging/release environment before public release.
  • Regularly review crash reports in the Appxiom dashboard and address critical issues promptly.

Frequently Asked Questions (FAQ)​

Q: What is a dSYM file and why is it important?
A: A dSYM file contains debug symbols that allow crash reports to be symbolicated, making stack traces human-readable and actionable.

Q: Where can I find the dSYM file after building my app?
A: The dSYM file is generated by Xcode during the build process. See the Locating dSYM file guide for details.

Q: What happens if I lose the dSYM file?
A: Without the dSYM file, crash reports will be difficult or impossible to interpret, making debugging much harder.

Q: Do I need to upload the dSYM file to Appxiom?
A: No, we have detailed documentation on how to symbolicate crash reports without needing to upload the dSYM file to Appxiom.

Q: Can I symbolicate crashes from previous app versions?
A: Only if you have the corresponding dSYM file for that version/build. Always keep backups for each release.