Downloading and installing from App Store would fail? - ios

I just release a new version of my app. But unfortunately the new version app crashes every time it launches.
So I used a file tool, which could browse, copy and export files inside iPhone, to export the .ipa file of my app that crash.
Then I find the archive that submitted to App Store by Xcode, extract an .ipa file from the archive. And if I install the ipa file with the tool I used, it would launch and work properly.
After I got 2 ipa files, I unzip them and use some file merge tool to check the difference between folders and files in that two ipa files, finding that the failed one seemed not to be updated. Some new-added file didn't exist and some renamed file didn't change their names.
So I doubt if the process of downloading and installing app from App Store go wrong, though it sounds like impossible.
There is part of crash log on my device. But I can barely read useful information from it.
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x000000000000b6d2
Highlighted Thread: 1
Thread 0 name: Dispatch queue: com.apple.libdispatch-manager
Thread 0:
0 libsystem_kernel.dylib 0x39a71648 kevent64 + 24
1 libdispatch.dylib 0x399aa4ec _dispatch_mgr_invoke + 792
2 libdispatch.dylib 0x3999cdf4 _dispatch_mgr_thread$VARIANT$up + 32
Thread 1:
0 libsystem_kernel.dylib 0x39a81d98 __workq_kernreturn + 8
1 libsystem_c.dylib 0x399cfcf6 _pthread_workq_return + 14
2 libsystem_c.dylib 0x399cfa12 _pthread_wqthread + 362
3 libsystem_c.dylib 0x399cf8a0 start_wqthread + 4
Thread 2:
0 libsystem_kernel.dylib 0x39a81d98 __workq_kernreturn + 8
1 libsystem_c.dylib 0x399cfcf6 _pthread_workq_return + 14
2 libsystem_c.dylib 0x399cfa12 _pthread_wqthread + 362
3 libsystem_c.dylib 0x399cf8a0 start_wqthread + 4
Unknown thread crashed with ARM Thread State (32-bit):
r0: 0x0006c0f8 r1: 0x2fda1cd4 r2: 0x0006bfd4 r3: 0x2fda1d08
r4: 0x2ff0214c r5: 0x2ff020ec r6: 0x0006bebd r7: 0x0000002f
r8: 0x2ff046ac r9: 0x0000ab00 r10: 0x00000000 r11: 0x00000049
ip: 0x1f507620 sp: 0x2fda0a20 lr: 0x2feee51d pc: 0x0006be88
cpsr: 0x80000030
Need help. Thanks for reading.

Related

iOS app crashes due to unknown error NO_CRASH_STACK + 0

Users complained that the application began to crash at startup. Users use ios 9.3 or 10.3. Application crashes due to an unknown error. This error is not reported in Crashlytics. I see an error in Xcode - Window - Organizer - Crashes, but there are no details:
NO_CRASH_STACK + 0
Running the application on the iPhone 5 emulator with iOS 10.3.4 does not result in an error. I took a real iPhone 5 device with iOS 10.3.4. I launched my application from Xcode, the application does not crash. Installed the same application from the AppStore - the application crashes. I assume that the application does not crash if launched from Xcode, since the application does not have access to iTunes Connect under a real Apple ID in the debug mode. I added a sandbox account instead of a real account, I tested the purchase, the application does not crash when using the test environment and sandbox account.
If on iPhone 5 log in under a real Apple ID, cause a crash by launching the application, then in Xcode - Window - Devices and Simulators, I select iPhone 5, then View Device Logs. This window has the information below.
How can I determine exactly where an error occurs? Is it possible to test a connection to the iTunes Connect using real Apple ID on iPhone 5 iOS 10.3.4 on the XCode? I have iPhone XS max also and on this device I can connect to the iTunes Connect using real Apple ID in the XCode debug mode, but can't on iPhone 5.
Date / Time: 2020-05-13 11: 21: 41.2938 +0300
Launch Time: 2020-05-13 11: 21: 40.0000 +0300
OS Version: iPhone OS 10.3.4 (14G61)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Subtype: KERN_PROTECTION_FAILURE at 0x00b485b0
Termination Signal: Bus error: 10
Termination Reason: Namespace SIGNAL, Code 0xa
Terminating Process: exc handler [0]
Triggered by Thread: 0
Filtered syslog:
None found
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 ??? 0x00b485b0 0 + 11830704
1 ??? 0x17e57c04 0 + 400915460
2 dyld 0x004d6da4 0x4b2000 + 150948
3 dyld 0x004be150 ImageLoaderMegaDylib :: incrementCoalIterator + 49488 (ImageLoader :: CoalIterator &) + 0
Thread 1:
0 libsystem_pthread.dylib 0x1a84e454 start_wqthread + 0
Thread 2:
0 libsystem_pthread.dylib 0x1a84e454 start_wqthread + 0
Thread 3:
0 libsystem_pthread.dylib 0x1a84e454 start_wqthread + 0
Thread 4 name: com.apple.uikit.eventfetch-thread
Thread 4:
0 libsystem_kernel.dylib 0x1a784900 mach_msg_trap + 20
1 libsystem_kernel.dylib 0x1a7846e0 mach_msg + 44
2 CoreFoundation 0x1af87be2 __CFRunLoopServiceMachPort + 144
3 CoreFoundation 0x1af86064 __CFRunLoopRun + 1436
4 CoreFoundation 0x1aed91ae CFRunLoopRunSpecific + 470
5 CoreFoundation 0x1aed8fd0 CFRunLoopRunInMode + 104
6 Foundation 0x1b82daf4 - [NSRunLoop + 47860 (NSRunLoop) runMode: beforeDate:] + 258
7 Foundation 0x1b84a76c - [NSRunLoop + 165740 (NSRunLoop) runUntilDate:] + 86
8 UIKit 0x20b62ad8 - [UIEventFetcher threadMain] + 128
9 Foundation 0x1b9118ea __NSThread__start__ + 1122
10 libsystem_pthread.dylib 0x1a85093a _pthread_body + 216
11 libsystem_pthread.dylib 0x1a85085c _pthread_start + 234
12 libsystem_pthread.dylib 0x1a84e468 thread_start + 8
Thread 0 crashed with ARM Thread State (32-bit):
    r0: 0x00000000 r1: 0x00000004 r2: 0x00000003 r3: 0x0061c200
    r4: 0x00000005 r5: 0x00000000 r6: 0x00000001 r7: 0x0061c09c
    r8: 0x0061c060 r9: 0x00000000 r10: 0x004c972d r11: 0x004e34dc
    ip: 0x00b32f68 sp: 0x0061c044 lr: 0x00000000 pc: 0x00b485b0
  cpsr: 0x60000010
Binary Images:...
In my case was problems with dependencies.
We use CocoaPods and SPM.SnapKit added by SPM were crashes on Iphone 5, ios 9.
Try to check dependencies if you use SPM.
Here are a lists of things you can do
Clean the build folder
Delete the detrieved data
Delete xcode followed by the developer folder in you library
If that does work, comment
Problem was solved with help from Apple Support
there is a bug in the compiler that is producing bad armv7 code,
causing this crash. It is addressed in the Xcode 11.5 beta. To avoid
this bug, please compile with Xcode 11.3 instead of Xcode 11.4, and
disable bitcode so the App Store doesn’t recompile your app with the
compiler that has this issue. When Xcode 11.5 is released, please
re-enable bitcode.

iOS React Native Testflight EXC_CRASH(SIGABRT) only for the Apple Tester

For some reasons our internal testers was able to run the app but somehow the apple beta tester says the app crashes as soon as the app launches. They provided me with this error
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 1
Application Specific Information:
abort() called
Last Exception Backtrace:
(0x18d80827c 0x18c9e29f8 0x101124b94 0x101121108 0x18d80f900 0x18d6f14d0 0x18d6f2104 0x101137f20 0x1011778b4 0x101177614 0x18d247a38 0x18d2487d4 0x18d1f1324 0x18d1f1e40 0x18d1fa4ac 0x18d428114 0x18d42acd4)
Thread 1 name: Dispatch queue:com.facebook.react.ExceptionsManagerQueue
Thread 1 Crashed:
0 libsystem_kernel.dylib 0x000000018d3a50dc 0x18d382000 + 143580
1 libsystem_pthread.dylib 0x000000018d41e094 0x18d41c000 + 8340
2 libsystem_c.dylib 0x000000018d2feea8 0x18d2a4000 + 372392
3 libc++abi.dylib 0x000000018c9cb788 0x18c9ca000 + 6024
4 libc++abi.dylib 0x000000018c9cb934 0x18c9ca000 + 6452
5 libobjc.A.dylib 0x000000018c9e2e00 0x18c9dd000 + 24064
6 libc++abi.dylib 0x000000018c9d7838 0x18c9ca000 + 55352
7 libc++abi.dylib 0x000000018c9d78c4 0x18c9ca000 + 55492
8 libdispatch.dylib 0x000000018d2487e8 0x18d1e8000 + 395240
9 libdispatch.dylib 0x000000018d1f1324 0x18d1e8000 + 37668
10 libdispatch.dylib 0x000000018d1f1e40 0x18d1e8000 + 40512
11 libdispatch.dylib 0x000000018d1fa4ac 0x18d1e8000 + 74924
12 libsystem_pthread.dylib 0x000000018d428114 0x18d41c000 + 49428
13 libsystem_pthread.dylib 0x000000018d42acd4 0x18d41c000 + 60628
im really not sure why the apple developer is experiencing crashes while the rest of the team was able to run the app normally through the testflight

Watch 2 Language Specific Issue

I'm working on a watch App. The Xcode version is 7.3, Swift 2 , iPhone 5 and watch version 3.1.3
First thing Mobile app and watch App both works properly on simulator.The App has two version (English/ Chinese). Now the problem is When I select the english Language for watch, App Works as I needed. But if I change the watch Language to Chinese or any other language then the App Shows a Spinner for long time and then return a black screen. Is anyone facing Same Issue??Please suggest me what is wrong with this app?? Thanks in advance.
Incident Identifier: 9611567E-C66A-4016-A07D-464B0D0F46CB
CrashReporter Key: f90545bedbe3c3364591ded5495f1209af31a874
Hardware Model: Watch2,4
Process: iCE Angel ID WatchApp [276]
Path: /private/var/containers/Bundle/Application/5DC3CFAC-91A8-475D-8B36-60D5353F38E3/iCE Angel ID WatchApp.app/iCE Angel ID WatchApp
Identifier: com.iceangelid.app.watchkit
Version: 1.1.1 (1.1.1)
Code Type: ARM (Native)
Role: Non UI
Parent Process: launchd [1]
Coalition: com.iceangelid.app.watchkit [343]
Date/Time: 2017-10-25 15:26:48.9193 +0530
Launch Time: 2017-10-25 15:25:56.0000 +0530
OS Version: Watch OS 3.1.3 (14S960)
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Triggered by Thread: 0
Filtered syslog:
None found
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x1f1896e0 0x1f185000 + 18144
1 libsystem_kernel.dylib 0x1f1894ac 0x1f185000 + 17580
2 CoreFoundation 0x1f516818 0x1f45d000 + 759832
3 CoreFoundation 0x1f514adc 0x1f45d000 + 752348
4 CoreFoundation 0x1f469414 0x1f45d000 + 50196
5 GraphicsServices 0x20c04e1e 0x20bf9000 + 48670
6 UIKit 0x23ea20be 0x23e2d000 + 479422
7 UIKit 0x23e9cf08 0x23e2d000 + 458504
8 SockPuppetGizmo 0x2a4d0ace 0x2a4c9000 + 31438
9 libdyld.dylib 0x1f0ac566 0x1f0a9000 + 13670
Thread 16:
0 libsystem_pthread.dylib 0x1f25d1a0 0x1f259000 + 16800
Thread 0 crashed with ARM Thread State (32-bit):
r0: 0x10004005 r1: 0x07000806 r2: 0x00000000 r3: 0x00000c00
r4: 0x00001b03 r5: 0xffffffff r6: 0x00000000 r7: 0x002b6e08
r8: 0x14e5dd88 r9: 0x014dccdc r10: 0x07000806 r11: 0x07000806
ip: 0xffffffe1 sp: 0x002b6dc0 lr: 0x1f1894ad pc: 0x1f1896e0
cpsr: 0x60000010
Binary Images:
0x100000 - 0x103fff iCE Angel ID WatchApp armv7k <7c65269026583b9eb4c246f5eb0d09ce> /var/containers/Bundle/Application/5DC3CFAC-91A8-475D-8B36-60D5353F38E3/iCE Angel ID WatchApp.app/iCE Angel ID WatchApp
0x140000 - 0x16ffff dyld armv7k <40c16d46fa443776b664db9a54fcd325> /usr/lib/dyld
0x1eb9c000 - 0x1eb9ffff libSystem.B.dylib armv7k <acc06d05ed6537c2a5f58cf93c84188b> /usr/lib/libSystem.B.dylib
0x1eba0000 - 0x1ebe3fff libc++.1.dylib armv7k <97e755cc71ae3b86b896f3ac8408fe1a> /usr/lib/libc++.1.dylib
0x1ebe4000 - 0x1ebfffff libc++abi.dylib armv7k <10a460aa3dbc3a2e929eea18e8e9f2a3> /usr/lib/libc++abi.dylib
[https://i.stack.imgur.com/Sr7m9.png][1]
One more thing that i forgot to mention is the app works properly on real devices when installed first time but if I uninstall the app and then reinstall it this produce the same issue as mentioned above.

How to understand EXC_BAC_ACCESS (SIGSEGV) KERN_INVALID_ADDRESS log?

I'm doing an app in Titanium for Android and IOS. When I navigate a lot in the application I have a random exception and the app crashes.
How can I know where is the problem?
The app is a little complex to explain:
It has two windows, first window is for "home" view that is only in portrait mode, and when I click to go to another view, I close the first window, I open another window and I add a view with the content to this window. The content view load the same web view with different url.
The app loads ok and I can navigate for the different views and windows ok. But when I navigate a lot, finally I have a EXC_BAC_ACCESS (SIGSEGV) and KERN_INVALID_ADDRESS
This only happens on device (on simulator it works ok) with iPad os 5.1.1 and os 7.0.2.
This is the log where the thread crashes:
Incident Identifier: 1A3E94A0-E6FC-4BFF-BB3B-7651D66664DE
CrashReporter Key: d4422d11c83ca9acf2212996b20dd1078f00f36c
Hardware Model: iPad3,3
Process: Appname [16747]
Path: /var/mobile/Applications/1BACB160-AED8-4F5F-A599-4F7F1F4A4DC4/Appname.app/Appname
Identifier: Appname
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2013-10-31 11:56:58.680 +0100
OS Version: iPhone OS 5.1.1 (9B206)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libicucore.A.dylib 0x37953fb2 utext_setNativeIndex + 122
1 libicucore.A.dylib 0x379542a6 icu::RuleBasedBreakIterator::following(int) + 246
2 WebKit 0x35f20b2c -[NSString(WebStringDrawing) __web_drawInRect:withFont:ellipsis:alignment:letterSpacing:lineSpacing:includeEmoji:truncationRect:measureOnly:renderedStringOut:drawUnderline:] + 2176
3 WebKit 0x35e99078 -[NSString(WebStringDrawing) __web_drawInRect:withFont:ellipsis:alignment:letterSpacing:lineSpacing:includeEmoji:truncationRect:measureOnly:renderedStringOut:] + 108
4 WebKit 0x35e98ffc -[NSString(WebStringDrawing) __web_drawInRect:withFont:ellipsis:alignment:letterSpacing:lineSpacing:includeEmoji:truncationRect:measureOnly:] + 100
5 WebKit 0x35e98f88 -[NSString(WebStringDrawing) _web_drawInRect:withFont:ellipsis:alignment:lineSpacing:includeEmoji:truncationRect:measureOnly:] + 100
6 WebKit 0x35e98f14 -[NSString(WebStringDrawing) _web_sizeInRect:withFont:ellipsis:lineSpacing:] + 80
7 UIKit 0x34fba65c -[NSString(UIStringDrawing) sizeWithFont:constrainedToSize:lineBreakMode:lineSpacing:] + 108
8 UIKit 0x3512ee0e -[NSString(UIStringDrawing) sizeWithFont:constrainedToSize:lineBreakMode:] + 46
9 Appname 0x0014528c -[TiUILabel sizeForFont:] (TiUILabel.m:57)
10 Appname 0x0014537a -[TiUILabel contentWidthForWidth:] (TiUILabel.m:69)
11 Appname 0x001449bc -[TiUILabelProxy contentWidthForWidth:] (TiUILabelProxy.m:17)
12 Appname 0x00116fb4 -[TiViewProxy autoWidthForSize:] (TiViewProxy.m:756)
13 Appname 0x00120dbc -[TiViewProxy computeChildSandbox:withBounds:] (TiViewProxy.m:2543)
14 Appname 0x0011fbb8 -[TiViewProxy measureChildren:] (TiViewProxy.m:2352)
15 Appname 0x00121e36 -[TiViewProxy layoutChildren:] (TiViewProxy.m:2818)
16 Appname 0x0011dd9a -[TiViewProxy refreshView:] (TiViewProxy.m:2061)
17 Appname 0x0011f25c -[TiViewProxy layoutChildrenIfNeeded] (TiViewProxy.m:2264)
18 Appname 0x001d5ba0 +[TiLayoutQueue layoutProxy:] (TiLayoutQueue.m:79)
19 Appname 0x001d59b0 performLayoutRefresh (TiLayoutQueue.m:46)
20 CoreFoundation 0x32a5fa2c __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 8
21 CoreFoundation 0x32a5f692 __CFRunLoopDoTimer + 358
22 CoreFoundation 0x32a5e268 __CFRunLoopRun + 1200
23 CoreFoundation 0x329e149e CFRunLoopRunSpecific + 294
24 CoreFoundation 0x329e1366 CFRunLoopRunInMode + 98
25 GraphicsServices 0x32b2e432 GSEventRunModal + 130
26 UIKit 0x34fc0cce UIApplicationMain + 1074
27 Appname 0x000b8c34 main (main.m:36)
28 Appname 0x000b8470 ___lldb_unnamed_function1$$Appname + 32
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x00000000 r3: 0x00000000
r4: 0x0d65c6b0 r5: 0x0d65c690 r6: 0x00000000 r7: 0x2feabfac
r8: 0x00000003 r9: 0x2feabf6c r10: 0x00000003 r11: 0x08052950
ip: 0x00000000 sp: 0x2feabfa4 lr: 0x00000000 pc: 0x37953fb2
cpsr: 0x80000030
I've also had the log of other threads and information about Binary Images. If it's useful I can paste it.
How can I know what is the cause of the problem and where is the problem?
Thank you very much
You get EXC_BAC_ACCESS because you are trying to access object which was removed from memory. It happens only on device when you navigate to many windows because every window takes some part of memory and when there is no more space for new windows iOS clears old objects who were deleted by you previously.
You can replicate this issue on simulator by forcing Memory Warning pressing ⇧ + ⌘ + M.
To solve your issue you have to store variable pointing to window object which you want to reopen later in some global dictionary.
Finally, I think it was a problem with webview component. I created a web view in each view (I need it to show some graphs) and when I return to home view, I tried to remove it. I think the problem is that you can't remove it completely and it takes a lot of memory.
Finally I solved it creating a webview in app.js and using it in all views changing the url and dimensions.

What does this crash log means?

I have already done some research on identifying crash logs but couldn't find solution:
Here are my references:
http://www.raywenderlich.com/23704/demystifying-ios-application-crash-logs
http://developer.apple.com/library/ios/#qa/qa1747/_index.html
How to view crash report on xcode 4.2
I do come to know that it is because of Memory Issue but how to find that particular? In my project there are 200 files also there are 4-5 third party libraries are being used.
Here is crash log:
Incident Identifier: BD0F0F41-C60A-4D9C-8386-1B10796CF835
CrashReporter Key: 43c75986a25cae4226726a78b4bf5b543ab87caa
Hardware Model: iPad3,3
Process: BLSOffline [10824]
Path: /var/mobile/Applications/54AAF195-FD1D-4426-BC20-939662ECC56B/BLSOffline.app/BLSOffline
Identifier: BLSOffline
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2013-07-12 15:24:05.680 +0530
OS Version: iOS 6.1.3 (10B329)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000013
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libobjc.A.dylib 0x3aadd526 0x3aad8000 + 21798
1 BLSOffline 0x000dbb6a 0xc8000 + 80746
2 CoreFoundation 0x32c3f9c0 0x32b7a000 + 809408
3 CoreFoundation 0x32b96fe6 0x32b7a000 + 118758
4 Foundation 0x335530f0 0x334a2000 + 725232
5 CoreFoundation 0x32c11680 0x32b7a000 + 620160
6 CoreFoundation 0x32c10f7a 0x32b7a000 + 618362
7 CoreFoundation 0x32c0fcb2 0x32b7a000 + 613554
8 CoreFoundation 0x32b82eb8 0x32b7a000 + 36536
9 CoreFoundation 0x32b82d44 0x32b7a000 + 36164
10 GraphicsServices 0x367372e6 0x36732000 + 21222
11 UIKit 0x34a982fc 0x34a41000 + 357116
12 BLSOffline 0x000db5fe 0xc8000 + 79358
13 libdyld.dylib 0x3af17b1c 0x3af16000 + 6940
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib 0x3afce648 0x3afcd000 + 5704
1 libdispatch.dylib 0x3aefe974 0x3aef6000 + 35188
2 libdispatch.dylib 0x3aefe654 0x3aef6000 + 34388
Thread 2 name: WebThread
Thread 3 name: JavaScriptCore::BlockFree
Thread 4 name: JavaScriptCore::Marking
Thread 5 name: com.apple.NSURLConnectionLoader
Thread 6 name: WebCore: CFNetwork Loader
Thread 7 name: WebCore: LocalStorage
Thread 8 name: com.apple.CFSocket.private
Thread 9 name: com.apple.coremedia.player.async
Thread 10 name: com.apple.coremedia.player.remote
Please let me know how to find cause out of this.
If my application is crashing at random point of times, still can it be possible to upload on AppStore? Will Apple allow such application?
Edit: The major problem is application is not crashing over simulator, it does only on devices. Also on device, when we debug the app, it crashes on curl library code, which is working fine since first day. Then how come sudden crash occurs in application?
If your application is crashing randomly then you need to analyze your code. That you can do in XCode only.Open your Project in XCode and in Product menu you will find the Analyze option (cmd+shift+B) .make sure you have selected "iOS Device" before analyzing it.
other than this you can use the this link:
http://www.raywenderlich.com/23037/how-to-use-instruments-in-xcode
apple will not accept your app if it is crashing.
No, Apple will probably get the crash too and reject your app (it's a risk).
About the crash, it's hard to say, you'll have to run the app from XCode and check there where the crash was.
If it's a memory issue, profile the app from XCode and you'll see there which component is crashing.

Resources