DSYM file
The dSYM file saves the debugging information file, which is convenient for App users to restore the function call stack and locate the cause of the Crash when a Crash occurs. The file name is usually: Xxx.app.dsym, files can usually be viewed through Xcode, Window -> Organizer -> Archives -> Select the corresponding Archives package -> Show in Finder -> Select the corresponding. Xcarchive file -> Display package contents -> Open the dSYMs folder. Find the corresponding project name.app.dsym file. So usually we should back up the packages after the Archives for the online version of the app. Such as:
The dSYM file is missing
To generate dSYM files for the packaged App, it needs to be configured correctly in Xcode. If the configuration is incorrect, the dSYM file may be regarded as missing, so Crash problem cannot be located. For example:
Handle missing dSYM files
- To deal with the missing dSYM file, it is usually necessary to check two configurations in Xcode. First, check whether the Generate Debug Symbols configuration under Project -> Build Settings is set to YES. If it is set to NO, the Debug symbol file will not be generated. The xxx.app.dSYM file will not be generated. Such as:
- While making sure Generate Debug Symbols is set to YES, also check that the Debug Information Format value under Project -> Build Settings is set to DWARF. If the dSYM File is DWARF with dSYM File, a new dSYM File is generated. However, if Generate Debug Symbols is set to NO, even if the Debug Information Format is set to DWARF with dSYM File, the xxx.app.dSYM File will not be generated. Such as:
Note: When Generate Debug Symbols is enabled, the size of the package will increase after the Archives is packaged. Such as:
Crash Location
You can use an open source tool, dSYMTools, to locate crashes. The Git address is github.com/answer-huan…