objective c - iOS app crash, symbolicated logs are opaque -
I believe I am looking at the symbolic logs properly, but please let me know that this is not the case. This is a part of the crash log since Apple has been rejected due to the accident on the launch, which I am unable to replicate completely.
I have installed a Crash Reporting System called Crashlytics, during which no crash report was received during the app, I believe that to start crashlitics, AppDelegate's Like the symbol is not enough to wait for it, i.e. With the names of your actions on 14 and 1, and with the last exception backtrack, you need the DSYM file which was when you created the app and deposit it in the same folder as your app bundle Kept If you use Xcode's collection functionality, then I believe that DSYM is included in the archive. I say line 1 and 14 because these are those which have the name of your app (Luff). What you need to do is crash report, dvm file and app file (not IPA) in the same folder (I'm not sure that the ap files for xcode are really necessary, so make sure that Only if it does not work with crash reports and DSYM only) Then, import the crash report into the Xcode Organizer and click on the "re-symbolism". What is up to you is as good as 100% waste without dSYM, unless you map any type of address to the symbols (work, methods) report. Besides, there is no stack trace of the accidental thread, where there is relevant information , I can tell you a few things about that stack trace, though on Line 14 The symbol is likely to have your main () function. Nothing special Rows between 1 and 14 show exceptions for a bunch of reinstallation and capture, that is, it is not a stack trace which caused the accident, but the stacktrace of the exception is passing around. Since you mentioned that you are a crashcatics, I can bet that 14 is just this. This is not a laugh or a crashcatics because CrashKitics is a static library embedded in your app. For all purposes and purposes, iOS is just one part of your app. I say that it is a crashcatics, when you are crashing, what causes crashes (exception, signal, etc.) is sometimes re-emerging and it will ultimately result in your custom crash reporting code Reaches. Relevant information is at the As you said, CrashKitics are not real time. The user will have to open the app again I know this because I am working on my own project named Real Time , provided there is an internet connection. didFinishLaunchingWithOptions . He said that, after the accident, the crashtix only sends the report when the app reopens, then the Apple reviewer may have encountered an accident and did not bother to try again, I probably do not have any CrashCat report.
Exception Type: EXC_CRASH (SIGABRT) Exception Code: 0x0000000000000000, 0x0000000000000000 0 Prev exception backtrace: (0xl8lf9a084 0xl929ec0e4 0xl808l9674 0xl0009l3l8 0xl00084fe4 0xl00084098 0xl867ldl58 0xl867lce68 0xl867d0ee8 0xl869dlda8 0xl8679l938 0xl867le88c 0xl867906f8 0xl0006l87c 0xl8678e5d0 0xl869a4de8 0xl869a7568 0xl869a5c00 0xl8al7l640 0x181f52360 0x181f51468 0x181f4fa8c 0x181e7d664 0x18678798c 0x186782984 0x100061c28 0x19305aa08) Thread 0 name: Dispatch queue: triggered by com.apple.main thread -thread Thread 0 crashed: 0 libsystem_kernel.dylib 0x0000000193172964 __kill + 8 1 LUFF 0x00000001001330dc 0x10005c000 + 880,860 2 libsystem_platform. Dylib 0x0000000193208958 _sigtramp + 64 3 libsystem_pthread.dylib 0x0000000193211224 pthread_kill + 108 4 libsystem_c.dylib 0x00000001930eab1 4 Abortion + 108 5 libc ++ Abi. Daileyib 0x00000001 921d 1414 abort_message + 112 6 libc ++ abi.dylib 0x00000001921f0b88 default_terminate_handler () + 300 7 libobjc.A.dylib 0x00000001929ec3bc _objc_terminate () + 124 8 libc ++ abi.dylib 0x00000001921edbb0 std :: __cancel (zero ( *) ()) + 12 9 libc ++ Abikdilib 0x00000001921ed738 __sksa_rethrov + 140 10 Libobjckakdilib 0x00000001929ec290 Objc_aksepshn_rethrov + 40 11 CoreFoundation 0x0000000181e7d710 CFRunLoopRunSpecific + 568 12 UIKit 0x0000000186787988 - [Uiappliction _rn] 548 13 UIKit 0x0000000186782980 UIApplicationMain + 1484 14 LUFF 0x0000000100061c24 0x10005c000 + 23,588 15 libdyld.dylib 0x000000019305aa04 Start + 0
last exception backtrack given to you but to read it, it should be a symbol with a DSIM file.
Comments
Post a Comment