Statistical error analysis of the League of friends

Export error

  1. You can choose to export all error lists or enter an error. Export this error,
    , Statistical error analysis of the League of friends,
  2. Download the newly exported error in the report center. The file format is CSV (open with Excel)
    Statistical error analysis of the League of friends

Resolve errors using tools provided by the League of friends

  1. Download the error analysis tool, and extract the zip to get the umcrashtool file. You can put the umcrashtool and the downloaded xxx.csv file in the same directory.
    Statistical error analysis of the League of friends
  2. In the terminal into the umcrashtool file directory, and run the umcrashtool command, the parameter is error analysis of the.Csv file, the absolute path is as follows:
    ./umcrashtool [path_of_csv_file]
Statistical error analysis of the League of friends

Note: if the error is analyzed, the.Csv file is not in the umcrashtool sibling directory, and the parameter must be the absolute path of the.Csv file

  1. After parsing, the error code and the number of rows will be written to the error analysis xxx-symbol.csv file, and the original file in the same directory under
    Statistical error analysis of the League of friends

View analysis results, location error, location

  1. Using the tool to open the xxx-symbol.csv file, you can see the error occurred source file and the number of rows
    , Statistical error analysis of the League of friends,
  2. Note: if the error analysis fails, make sure that the corresponding xxx.dSYM file is in the subdirectory of the ~/Library/Developer/Xcode/ or the path. (for each product release archive will dsym files stored in the ~/Library/Developer/Xcode/Archives path, therefore recommended to keep the path of the file, in order to follow with the tools of analysis error.)
    Statistical error analysis of the League of friends
Details for reference

[statistical error analysis of iOS function description] (http://dev.umeng.com/analytics/reports/errors#2)