Online application as long as the heart point can find some bugs, even, QQ is not listed outside. But the worst of the bugs is a flashback, which results in users not being able to use our app directly.
Our company is particularly focused on user feedback and experience, we will regularly call to consult the user's usage. We also have our own group of angels, these users will be with us in a timely manner to respond to the use of the application, the bug situation, as well as their needs.
The user is not a technician he can not tell you clearly how to produce a flashback, so we need a bug statistics function, our company uses Friends League statistics to implement the bug record. We have the ability to embed AU stats in iOS apps, and I also often check out the unstable points in the project for error statistics and error trending in Friends League. We all know that we can only see some 16-binary addresses and don't know exactly where the problem is.
The bug log on the friend League:
Application received signal SIGSEGV (NULL)(( 0Corefoundation0x2d539feb<redacted> +154 1LIBOBJC. A.dylib0X37DB2CCFObjc_exception_throw + - 2Corefoundation0x2d539f15<redacted> +0 3Thefirstclass0X2928A1Thefirstclass +2680993 4Libsystem_platform.dylib0x383d9f8b_sigtramp + the 5Libsystem_malloc.dylib0x3839c267<redacted> +2270 6Libsqlite3.dylib0x3805bc67Sqlite3_exec +2322 7Libsqlite3.dylib0x3805b9b5Sqlite3_exec +1632 8Libsqlite3.dylib0x38094c6bSQLITE3_PREPARE_V2 + - 9Thefirstclass0xc020dThefirstclass +770573 TenThefirstclass0xc0689Thefirstclass +771721 OneThefirstclass0x103457Thefirstclass +1045591 AThefirstclass0x103331Thefirstclass +1045297 -Thefirstclass0x18889dThefirstclass +1591453 -Libdispatch.dylib0X382A07CB<redacted> + - theThefirstclass0x188831Thefirstclass +1591345 -Thefirstclass0x10325dThefirstclass +1045085 -Thefirstclass0x1031e9Thefirstclass +1044969 -Thefirstclass0x10319dThefirstclass +1044893 +Libdispatch.dylib0x382a260f<redacted> + $ -Thefirstclass0x103157Thefirstclass +1044823 +Thefirstclass0x1209dThefirstclass +57501 AThefirstclass0X115A3Thefirstclass +54691 atThefirstclass0X10ACFThefirstclass +51919 -Thefirstclass0x16c03fThefirstclass +1474623 -Thefirstclass0x293efThefirstclass +152559 -Thefirstclass0x79d5bThefirstclass +482651 -Libdispatch.dylib0x3829a833<redacted> +Ten -Libdispatch.dylib0x3829a81f<redacted> + A inLibdispatch.dylib0x382a149f<redacted> +278 -Corefoundation0x2d5048f1<redacted> +8 toCorefoundation0x2d5031c5<redacted> +1300 +Corefoundation0x2d46df0fCfrunlooprunspecific +522 -Corefoundation0X2D46DCF3Cfrunloopruninmode +106 theGraphicsservices0x323c6663Gseventrunmodal +138 *UIKit0x2fdb916dUiapplicationmain +1136 $Thefirstclass0x122f01Thefirstclass +1175297 Panax NotoginsengLibdyld.dylib0x382bfab7<redacted> +2) DSYM uuid:1ed274b4-8d63-3247-8168-fb884b9e88dacpu type:armv7slide Address:0x00004000Binary image:thefirstclassbase Address:0x000bc000
The bug lookup steps are as follows:
1. In order to track the friend League bug log, we must save the packaged "Xx.xcarchive" at the same time when the app is packaged, display the package contents of xx.xcarchive, and then find the "project name App.dsym" in the Dsyms folder on the desktop.
2. Display the package contents of "Project name. App.dsym" and locate the "project name" file and copy it to the desktop.
3. Open the terminal
A. Enter CD DeskTop
B. Dwarfdump--1ed274b4-8d63-3247-8168-fb884b9e88da (This is the DSYM UUID) project name. App.dsym
C. dwarfdump--arch= armv7 (armv7 This is CPU Type)--lookup 0xc020d(0xc020d This is the address of the error message)/users/your computer/desktop/project name
The above steps will be able to locate the crash code, as to why this line of code crashes, this need to analyze the solution. This is my summary of the Friend League to find a simple method of the bug, using the terminal does not download the resolution of the image of the bug plugin, a few simple terminal code is not troublesome.
Online application bug tracking search-Friends League statistics