In App Dashboard, click “Crash” enter the App’s Crash page, as shown:
In App Crash Exception homepage, developer can check the App’s Crash Statistics, including error rate, pending issues, processed issues, the number of Crashes and affected users.
By checking the Crash Trend Graph, developer can not only acquaint the changes of Crash, but also grasp the quality of the ready-to-release version, thus decide which problems have to be solved before the release. As shown in fig.1.‘3’
Pgyer provides developer with Crash State Mark function, there are two types of Crash state:
As “1” shown in fig.1, developer needs to tick the state which needs converting first and then to modify by clicking “2” in fig.1 after determining the Crash state.
In the Crash list, developer can select specific version, state and time node not only by refreshing Crash list automatically and inputting key words but also filtering the concerned Crashes. As shown in fig.1 “4”.
You can make Crash Log show more detailed information after symbolization, which is very advantageous for developer to carry on error analysis and localization.
Developer needs to upload symbol table problems in order to display Crash Log in symbolic form. For iOS, developer can only check the Log information for now. For Android, uploading mapping files is required, as shown in fig.1 “5”.
Crash Log can be symbolically displayed after uploading the symbol table files.
In the Crash Log list, tick the Crash Log you want to check enter the detailed page (as shown in fig.1 “6”), in which you can see the crash device and system information, crash error thread stack, system log and other information.
Click “1” in fig.2 to modify Crash Log process state.
Click “2” in fig.2 to display in symbolization.
Click “3” in fig.2 to check Crash Log.