iOS Friend League stats bug Tracker

At the beginning of the project, both Android and iOS were returned with a bugly to the bug in the late iOS online process, prompting for a conflicting approach to bugly's upload, and then iOS to the Allies, but the headache is that the captured iOS problem is not as clear as Android. Only memory addresses are shown, and no previous experience has led iOS packager to save xcarchive files and cannot be located. The latest version is on-line to send it to my current version of xcarchive to locate the analysis bug, search the Web, and use a tool (dSYM file Analysis tool) to analyze.

1. Prepare content

dSYM file Analysis tool, current release version of Xcarchive file, current release version of the Friend League bug record

2. Operating instructions

Open dsym File Analysis tool (Figure 1), drag the xcarchive file to the "Please drag and drop the dSYM file into the window and select any version for Analysis" and then click on the dragged file, which will appear in Figure 2 automatically fill in the UUID of the selected dSYM file.

Figure 1

Figure 2

Open Friend League Select a bug record, as follows:

-[nsnull Rangeofcharacterfromset:]: Unrecognized selector sent to instance 0x197941e70 (NULL) (0 corefoundation 0X00000001854802F4 <redacted> + 1601 LIBOBJC. A.dylib 0x0000000196ca40e4 Objc_exception_throw + 602 corefoundation 0x00000001 854873A4 <redacted> + corefoundation 0x0000000185484154 <redacted> + 9284 Corefoun Dation 0X0000000185386CCC _cf_forwarding_prep_0 + 925 UIKit 0x0000000                               18A236C44 <redacted> + 1046 UIKit 0x000000018a3a52c0 <redacted> + 767 UIKit 0x000000018a3a5380 <redacted> + 568 UIKit 0x000000018a                               3a5464 <redacted> + 369 quartzcore 0x0000000189800884 <redacted> + 32010 UIKit     0x0000000189ed1f94 <redacted> + 16011 UIKit                          0x0000000189f973d0 <redacted> + 34812 UIKit 0x000000018a1b5                               Be8 <redacted> + 322013 UIKit 0x0000000189fa1268 <redacted> + 17214 UIKit 0x0000000189ebd760 <redacted> + 58015 Quartzcore 0x0000000189805                          E1C <redacted> + 15216 quartzcore 0x0000000189800884 <redacted> + 32017 Quartzcore 0x0000000189800728 <redacted> + 3218 quartzcore 0x00000001897ffeb                          C <redacted> + 27619 Quartzcore 0x00000001897ffc3c <redacted> + 52820 Quartzcore 0x00000001897f9364 <redacted> + 8021 corefoundation 0x00000001854382a4                      <redacted> + 3222 corefoundation 0x0000000185435230 <redacted> + 36023 corefoundation 0x0000000185435610 <redacted> + 83624 corefoundation 0x00000001853612d4 cfrunlooprunspecific + 396 Graphicsservices 0X000000018EB776FC Gseventrunmodal + 16826 UIKit 0x                           0000000189F26FAC Uiapplicationmain + 148827????????? 0X00000001000450C4????????? + 20090028 libdyld.dylib 0x0000000197322a08 <redacted> + 4) DSYM uuid:95b2009c-c988-****-**** -8393e7003fa8cpu type:arm64slide address:0x0000000100000000binary Image:??? Base address:0x0000000100014000

First, the dSYM uuid in the bug corresponds to whether the UUID in the dSYM file Analysis tool is the same.

In the bug record usually with the project name or due to garbled cause??? The line of code is the project error row copy memory address

0x00000001000450c4

And

Slide address:0x0000000100000000

Toin the dSYM file Analysis tool, click the Analyze button to display the line of code that corresponds to the current memory address where it is likely to be wrong.

Finally, find the corresponding row in the project to find the problem is OK.

iOS Friends statistics bug tracking