Symbolication is the process of replacing memory addresses in a crash or energy log with human-readable function names and line numbers. Where symbolication occurs depends on the distribution options you select when you upload your app to App Store Connect.
Distribution options | Where symbolication occurs | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Don’t include bitcode Upload symbols | The service symbolicates the logs. | ||||||||||
Include bitcode Upload symbols | The App Store compiles the bitcode and generates the dSYM files with full symbol names. Then the service symbolicates the logs. | ||||||||||
Include bitcode Don’t upload symbols | The App Store compiles the bitcode and generates the dSYM files with obfuscated symbols. When you download the dSYM files, Xcode de-obfuscates the symbols using the | ||||||||||
Don’t include bitcode Don’t upload symbols | Xcode symbolicates logs using the dSYM files in your archive or dSYM files it finds on your Mac that are indexed by Spotlight. If Xcode can’t find the dSYM files, the log will not be symbolicated. If you can provide the dSYM files later, you can try to symbolicate the crash log again. | ||||||||||