Introduction
When our project is packaged and uploaded to the Apple Store, the crash problem does not seem so obvious in Xcode, so we have to analyze the crash log of the project so that the collapse analysis of the allies is reflected.
Premise
- Your project is integrated with the Friends League
- Can get the dSYM file to the project
What is a DSYM file
After Xcode compiles the project, we will see a DSYM file with the same name, DSYM is a transit file that holds the address mapping information of the 16 binary functions, the symbols we debug will be included in this file, and a new DSYM file will be generated each time the project is compiled, located in/users /< User name >/library/developer/xcode/archives directory, for each release we are very necessary to save the corresponding Archives file (automatically save the DSYM files This article describes the automatic saving of DSYM files after each compilation by the script.
What is the role of the DSYM file
When our software release mode is packaged or online, it will not be as intuitive as we are in Xcode to see the crash error, this time we need to analyze the crash report file, the IOS device will have a log file to save each of our application error function memory address, through Xcode Organizer can export the IOS device Devicelog to crash file, this time we can use the wrong function address to query the DSYM file of the program corresponding function name and file name. The premise is that we need to have a software version corresponding to the DSYM file, which is why it is necessary for us to save each release version of the Archives file.
how to get the dSYM file for a project
Archieves, Organization, Window, Xcode
Once the dSYM file is downloaded, the corresponding file is found directly in the show in finder
Of course, if the project package at that time is not the same way that you submit AppStore, the person who packaged the same method provides the dSYM file.
So far, the dSYM file is ready.
Get Friends League error messages
Login to the Friends League control background, select the corresponding project---AU statistics--Error analysis--Error List enter error details. Such as:
Type the command at the end of the line, enter, the relevant error message will come out, such as:
At this point, the line of code for the class that crashed is located.
Use Friends League to locate the crash location of the iOS online version project