Quickly locate the error code! Friends League error analysis enlarged recruit

New error Analysis

Error analysis is a Crash collection and analysis tool for mobile developers that enables developers to monitor the health of apps on mobile devices, identify and resolve errors, and improve app stability. November, the new version of the error analysis full-on-line, the function has a great upgrade, friends of the new version of the error analysis to provide developers with quality perfect experience and service!

Features of the new version error analysis

1. You can filter errors by error type, app version. 2. You can label errors according to different conditions for quick sorting and finding errors. 3. Android can locate the Crash location by uploading the mapping file. IOS can be located using the Umcrashtool tool after downloading the Xx.csv file. 4. You can customize the error message (Android) (Hint: If you do not update to the new SDK, some features of the new version of error analysis will not be available.) ）

Friends League Error Analysis FAQs

Q: Why are there garbled characters in Android error details?

A: Do not upload Chinese when using custom upload errors.

Q: What is included in the error details?

A: The error summary that is shown in the errors list is generated by the first line of the stack information that will collect the Crash log through an algorithm that aggregates the error. The Error details page shows the error detailed stacktrace and the first occurrence time, the last occurrence time, the total number of times, the application version where the error occurred, and the terminal information. The list of unresolved errors shows the types of errors received in the last 15 days (including today); The fixed, processed, ignored errors list shows the types of errors received in the last 90 days (including today).

Q: Why is there no data after crash test?

A: The data sending policy for error analysis is sent when it is started again, so you need to start the app again after crash to receive the data. Other possible reasons: if you use other error statistics at the same time, if you register first, other error statistics will result in the Friend League error statistics being overwritten without data. (Android) If the statistics SDK is written in a sub-thread, and the user is crash on the main thread, it will not be counted. If you call the

[Mobclick Setcrashreportenabled:no]--ios;

Mobclickagent.setcatchuncaughtexceptions (False)--android

Turn off error statistics and you will not be able to receive data.

Q: How to locate the wrong location?

A:android can be used to locate the Crash by uploading the mapping file. IOS can be located using the Umcrashtool tool after downloading the Xx.csv file. For detailed usage See: http://www.umeng.com/umeng30_error_type

Q: How do I filter error messages by date?

A: Currently, in addition to receiving errors today, filter by date is not supported.

Q: Why are some errors not counted?

A: Possible causes are as follows ① today's errors show the total number of errors received today (number of error types after aggregation), and when today's error type exceeds 1000, the data will not continue to update.

② may have called this method: Mobclickagent.onkillprocess (context context). If a developer calls a method such as Process.kill or system.exit to kill a process, be sure to call this method before to save the statistics.

③ need to check the version that receives the error message. When a version is unchecked, the error message for that version will no longer continue to be received, but will not reduce the number of errors received on that day.

For more information on the use of the Friend League error analysis, please click on the "Friend Alliance Technology Forum" to view, if there is a product use problem, please send directly to the mailbox [email protected].

Quickly locate the error code! Friends League error analysis enlarged recruit