Crash error feedback after iOS development was released (i)

iOS program in the debugging phase of the crash, you can directly by looking at the console printed error messages to locate? and fixed. But! But! But! The important thing to say three times, after the release of the program? in the background of itunes Connect there is no crash information, and actually a crash, real pain, Apple's own crash report can not be used! Can only use the current market crash feedback tool, one means is to use Umeng.

In view of the fact that we are now adding Umeng Mobile Developer Service platform in your app, it is common to use his friends League to share and the Friends Union daily Statistics these features more. But it also integrates a function of comparison to force, that is, error analysis, white point is the user in the process of using your app crash sent back after the error report. Click here for my product, error analysis: Error List to see the wrong message, such as:

Step one: Click on the right side of the small notebook button, the error message is directed out;

Step Two: Open Xcode, in the menu bar Windows->organizer pop-up interface, find the version you uploaded to the App Store before, determine the good version,

/users/< User name >/library/developer/xcode/archives directory, locate the xxxx.xcarchive file, but remember to remove the file name space! Or you'll get an error when you use it later! Copy it out.

Step three: Download dSYM tool tool, Baidu Network disk under the download: Http://pan.baidu.com/s/1bnkxPvT, the xxxx. xcarchive file dragged in, remember to remove the file name of the space! Click on the file that corresponds to the edit type selected in the following

Then fill in the pan-green memory address that appears in the Umeng error statistics, click Analysis, you can get the wrong reason and the wrong thing first few lines

As shown in the following:

Crash error feedback after iOS development was released (i)