I am getting occasional SIGSEGV errors like below in my app (c# Xamarin iOS app with latest version of Xamarin Studio=5.8.3, Xamarin.iOS=8.9.1.3
It looks like in crashed in UIKit and from my own app "ObymobiMobileAppiOS" it's just in "main".
What kind of problem it is?
How can I get more info or debug it?
I can reproduce it by using the app for about 5 mins.
Stacktrace:
at <unknown> <0xffffffff>
at (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr) <0xffffffff>
at UIKit.UIApplication.Main (string[],intptr,intptr) [0x00005] in /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:62
at UIKit.UIApplication.Main (string[],string,string) [0x0001c] in /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:45
at Obymobi.Mobile.App.iOS.Application.Main (string[]) [0x000b9] in /Users/billbatchelor/Documents/Mobile Development/AllInOne/Obymobi.Xamarin/Obymobi.Mobile.App.iOS/Main.cs:52
at (wrapper runtime-invoke) object.runtime_invoke_dynamic (intptr,intptr,intptr,intptr) <0xffffffff>
Native stacktrace:
0 ObymobiMobileAppiOS 0x00000001024ef9ac mono_handle_native_sigsegv + 264
1 ObymobiMobileAppiOS 0x00000001024f97cc mono_sigsegv_signal_handler + 316
2 libsystem_platform.dylib 0x000000019890895c _sigtramp + 68
3 UIKit 0x000000018b535540 <redacted> + 216
4 UIKit 0x000000018b535030 <redacted> + 452
5 UIKit 0x000000018b534e38 <redacted> + 216
6 UIKit 0x000000018b534d4c <redacted> + 468
7 UIKit 0x000000018b48fd8c <redacted> + 264
8 UIKit 0x000000018b32ca2c <redacted> + 700
9 UIKit 0x000000018b325f68 <redacted> + 684
10 UIKit 0x000000018b2f918c <redacted> + 264
11 UIKit 0x000000018b59a324 <redacted> + 15424
12 UIKit 0x000000018b2f76a0 <redacted> + 1716
13 CoreFoundation 0x0000000186870240 <redacted> + 24
14 CoreFoundation 0x000000018686f4e4 <redacted> + 264
15 CoreFoundation 0x000000018686d594 <redacted> + 712
16 CoreFoundation 0x00000001867992d4 CFRunLoopRunSpecific + 396
17 GraphicsServices 0x000000018ffaf6fc GSEventRunModal + 168
18 UIKit 0x000000018b35efac UIApplicationMain + 1488
19 ObymobiMobileAppiOS 0x0000000100b61f28 wrapper_managed_to_native_UIKit_UIApplication_UIApplicationMain_int_string___intptr_intptr + 344
20 ObymobiMobileAppiOS 0x00000001005387c0 UIKit_UIApplication_Main_string___intptr_intptr + 48
21 ObymobiMobileAppiOS 0x000000010053865c UIKit_UIApplication_Main_string___string_string + 188
22 ObymobiMobileAppiOS 0x000000010009c654 Obymobi_Mobile_App_iOS_Application_Main_string__ + 1508
23 ObymobiMobileAppiOS 0x0000000101007130 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 160
24 ObymobiMobileAppiOS 0x00000001024fb88c mono_jit_runtime_invoke + 1260
25 ObymobiMobileAppiOS 0x00000001025511e0 mono_runtime_invoke + 128
26 ObymobiMobileAppiOS 0x00000001025553c4 mono_runtime_exec_main + 404
27 ObymobiMobileAppiOS 0x00000001025c6a50 xamarin_main + 1812
28 ObymobiMobileAppiOS 0x00000001024b9688 main + 96
29 libdyld.dylib 0x000000019875aa08 <redacted> + 4
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries used by your application.
Update
Here is another example of SIGSEGVs I get (this was on simulator) which doesn't have "redacted":-
Any more ideas how to find the problem? Or is it a possible bug in Xamarin?
Native stacktrace:
0 ObymobiMobileAppiOS 0x0011d4f7 mono_handle_native_sigsegv + 311
1 ObymobiMobileAppiOS 0x0014c505 mono_sigsegv_signal_handler + 213
2 libsystem_platform.dylib 0x08c8003b _sigtramp + 43
3 ??? 0xffffffff 0x0 + 4294967295
4 VectorKit 0x10663fe9 -[VKTileProvider tileSource:didFetchTile:forKey:] + 105
5 VectorKit 0x1067140e -[VKTileSource fetchedTile:forKey:] + 62
6 VectorKit 0x106c2617 -[VKTileSetBackedTileSource fetchedTile:forKey:] + 247
7 VectorKit 0x106705b5 -[VKTileSource _fetchedTile:] + 309
8 VectorKit 0x10671985 __49-[VKTileSource decodeData:downloadKey:sourceKey:]_block_invoke_2 + 181
9 libdispatch.dylib 0x08930d8a _dispatch_call_block_and_release + 15
10 libdispatch.dylib 0x0894decf _dispatch_client_callout + 14
11 libdispatch.dylib 0x0893602e _dispatch_queue_drain + 411
12 libdispatch.dylib 0x08935d33 _dispatch_queue_invoke + 197
13 libdispatch.dylib 0x0893820b _dispatch_root_queue_drain + 428
14 libdispatch.dylib 0x089393e7 _dispatch_worker_thread3 + 108
15 libsystem_pthread.dylib 0x08c8d1da _pthread_wqthread + 724
16 libsystem_pthread.dylib 0x08c8ae2e start_wqthread + 30
I came across the same problem. In my case I found some solutions:
If project referenced to wrapper above native library. Check that wrapper and your project have the same architecture - Classic API or Unified API.
1.1 Try to rebuild native project.
1.2 Remove project wrapper from solution and add reference only to output library.
Sometimes, native object are destroyed earlier than .NET. In this case, .NET object have exceptions inside and this error cannot catch with try-catch.
Need to dispose objects correctly.
Try to look crash report inside xcode to get more detailed information.
I faced this problem while using UIDocumentInteractionController. I was using instance of this class as a local parameter and garbage collector was flushing that instance even before the function execution completes. Taking that instance to Global scope solved my problem.
Are the version of Xamarin equal on OS X and Windows? I had similar error. When I updated Xamarin, everything was fine.
Related
I am seeing some crashes that I cannot properly read.
Background: The app has a react native part. Below the regular react native objc code with some additional modules. The there is lot of custom objc and swift code. And on the very bottom we have a c/c++ engine doing their voodoo.
Note: Those stack traces are taken from Firebase / Crashlytics. Are these logs looking like DSYM files are missing? Or am I just not able to read them?
First stacktrace
Crashed: com.apple.main-thread
0 Objc/C++Part 0x104052a6c Engine::setTask(Task const*) + 408
1 SwiftPart 0x102dc14a8 __swift_memcpy2_1 + 3268
2 SwiftPart 0x102d89c2c globalinit_33_D059BB15480DF7E417659EA3E0158837_func83 + 2880
3 SwiftPart 0x102dc6a28 globalinit_33_164233930FF8443B67F99609B74287FF_func109 + 496
4 SwiftPart 0x102dc2ff4 globalinit_33_F9D0611596767A886B653DD36AB555FE_func108 + 2208
5 Foundation 0x196131050 __NSFireTimer + 64
6 CoreFoundation 0x195cc5e00 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 28
7 CoreFoundation 0x195cc5b3c __CFRunLoopDoTimer + 880
8 CoreFoundation 0x195cc520c __CFRunLoopDoTimers + 276
9 CoreFoundation 0x195cc0348 __CFRunLoopRun + 1920
10 CoreFoundation 0x195cbf8a0 CFRunLoopRunSpecific + 464
11 GraphicsServices 0x19fc17328 GSEventRunModal + 104
12 UIKitCore 0x199db0740 UIApplicationMain + 1936
13 MainApplication 0x1023390e4 main + 16 (main.m:16)
14 libdyld.dylib 0x195b4a360 start + 4
What does the line 2 SwiftPart 0x102d89c2c globalinit_33_D059BB15480DF7E417659EA3E0158837_func83 + 2880 mean for example? How can I find out what line Engine::setTask(Task const*) + 408 exactly means?
Second stacktrace
Crashed: com.apple.main-thread
0 libswiftCore.dylib 0x1aba7b440 swift_isUniquelyReferenced_nonNull_native + 34
1 MainApplication 0x100bb6f60 thunk for #escaping #callee_guaranteed () -> () + 4309315424 (<compiler-generated>:4309315424)
2 libdispatch.dylib 0x19e18b7dc _dispatch_block_async_invoke2 + 104
3 libdispatch.dylib 0x19e1d9184 _dispatch_client_callout + 16
4 libdispatch.dylib 0x19e18b190 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1044
5 CoreFoundation 0x19e48a5e4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
6 CoreFoundation 0x19e4855d8 __CFRunLoopRun + 2004
7 CoreFoundation 0x19e484adc CFRunLoopRunSpecific + 464
8 GraphicsServices 0x1a840a328 GSEventRunModal + 104
9 UIKitCore 0x1a257fae0 UIApplicationMain + 1936
10 MainApplication 0x100b310e4 main + 16 (main.m:16)
11 libdyld.dylib 0x19e30e360 start + 4
Same here. How to read this?
Here is the crash report and the crash is only happening on iOS 13 beta version :-
Crashed: com.apple.main-thread
0 libsystem_pthread.dylib 0x1ae056484 pthread_get_qos_class_np + 8
1 Foundation 0x1ae664340 -[NSThread qualityOfService] + 80
2 Foundation 0x1ae626ebc -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 280
3 Foundation 0x1ae628df8 -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:] + 116
4 libAXSpeechManager.dylib 0x1d0176884 -[AXSpeechManager isSpeaking] + 112
5 libAXSpeechManager.dylib 0x1d0171b60 -[AXSpeechManager _didBeginInterruption] + 52
6 libAXSpeechManager.dylib 0x1d0171f1c -[AXSpeechManager _handleAudioInterruption:] + 504
7 CoreFoundation 0x1ae2929ac __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 20
8 CoreFoundation 0x1ae2929f4 ___CFXRegistrationPost1_block_invoke + 64
9 CoreFoundation 0x1ae291d54 _CFXRegistrationPost1 + 368
10 CoreFoundation 0x1ae291a20 ___CFXNotificationPost_block_invoke + 104
11 CoreFoundation 0x1ae20dd38 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1416
12 CoreFoundation 0x1ae291370 _CFXNotificationPost + 1244
13 Foundation 0x1ae5edcf8 -[NSNotificationCenter postNotificationName:object:userInfo:] + 60
14 AVFAudio 0x1bac4603c -[AVAudioSession privateInterruptionWithInfo:] + 988
15 AVFAudio 0x1bac4880c (anonymous namespace)::HandlePropertyListenerCallback(unsigned int, objc_selector*, NSObject*) + 68
16 libdispatch.dylib 0x1ae004658 _dispatch_call_block_and_release + 24
17 libdispatch.dylib 0x1ae0051cc _dispatch_client_callout + 16
18 libdispatch.dylib 0x1adfe83e0 _dispatch_main_queue_callback_4CF$VARIANT$armv81 + 996
19 CoreFoundation 0x1ae2b4c74 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
20 CoreFoundation 0x1ae2afc68 __CFRunLoopRun + 2004
21 CoreFoundation 0x1ae2af16c CFRunLoopRunSpecific + 464
22 GraphicsServices 0x1b80d9328 GSEventRunModal + 104
23 UIKitCore 0x1b2317f6c UIApplicationMain + 1936
24 Quickride 0x10086803c main + 37 (AppDelegate.swift:37)
25 libdyld.dylib 0x1ae13a424 start + 4
I have checked on various platforms for this issue. But have not found any solution related to it.Please provide any solution related to it.
It is crashing on app launch itself and this is the report it shows on fabric
I've the same issue on iOS 13 and it's my most serious crash on Crashlytics.
It occurs only in iOS 13 and above. Unfortunately also in the latest 13.1.2.
Starting by the iOS 13 release I've detected a strange warning when I put my app in background the debug console print Can't end BackgroundTask: no background task exists with identifier x, or it may have already been ended. Break in UIApplicationEndBackgroundTaskError() to debug.
Maybe the issues are related.
Our Xamarin Forms app is crashing intermittently on one of our iOS test devices, and I'm having a very hard time finding anything useful in the crash report.
All of the tutorials and examples I have found seem to reference line numbers and methods/properties from the application itself but all I am seeing here are mono library calls.
I'm also unable to reproduce the issue locally. Can anyone offer any guidance, or suggest a good resource I could use to determine what this crash report is actually reporting:
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Thread 0 name:
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x0000000189423014 __pthread_kill + 8
1 libsystem_pthread.dylib 0x00000001894eb450 pthread_kill + 112 (pthread.c:1366)
2 libsystem_c.dylib 0x0000000189397400 abort + 140 (abort.c:91)
3 ESPMobileiOS 0x00000001000476a8 mono_handle_native_sigsegv (mini-exceptions.c:2420)
4 libsystem_platform.dylib 0x00000001894e5348 _sigtramp + 52 (sigtramp.c:115)
5 libsystem_pthread.dylib 0x00000001894eb450 pthread_kill + 112 (pthread.c:1366)
6 libsystem_c.dylib 0x0000000189397400 abort + 140 (abort.c:91)
7 ESPMobileiOS 0x000000010012fa04 print_all_exceptions(MonoObject*) (runtime.m:997)
8 ESPMobileiOS 0x0000000100047de0 mono_invoke_unhandled_exception_hook (mini-exceptions.c:2873)
9 ESPMobileiOS 0x000000010004733c mono_handle_exception_internal (mini-exceptions.c:1798)
10 ESPMobileiOS 0x000000010004641c mono_handle_exception (mini-exceptions.c:2027)
11 ESPMobileiOS 0x000000010003ef18 mono_arm_throw_exception (exceptions-arm64.c:390)
12 ESPMobileiOS 0x00000001004de4e8 throw_exception + 168
13 ESPMobileiOS 0x00000001002f67cc System_Runtime_ExceptionServices_ExceptionDispatchInfo_Throw + 44
14 ESPMobileiOS 0x00000001002f4d20 System_Runtime_CompilerServices_AsyncMethodBuilderCore__ThrowAsyncm__0_object + 80
15 ESPMobileiOS 0x000000010018cbd8 UIKit_UIKitSynchronizationContext__Postc__AnonStorey0__m__0 (UIKitSynchronizationContext.cs:24)
16 ESPMobileiOS 0x00000001001aa3a4 Foundation_NSAsyncActionDispatcher_Apply (NSAction.cs:163)
17 ESPMobileiOS 0x00000001004a9f94 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 244
18 ESPMobileiOS 0x000000010005433c mono_jit_runtime_invoke (mini-runtime.c:2524)
19 ESPMobileiOS 0x00000001000b0918 do_runtime_invoke (object.c:2809)
20 ESPMobileiOS 0x00000001000b0874 mono_runtime_invoke (object.c:2967)
21 ESPMobileiOS 0x00000001011a98e4 native_to_managed_trampoline_3(objc_object*, objc_selector*, _MonoMethod**, char const*, char const*) (registrar.m:103)
22 ESPMobileiOS 0x00000001011a9fdc -[__MonoMac_NSAsyncActionDispatcher xamarinApplySelector] (registrar.m:6678)
23 Foundation 0x000000018af69048 __NSThreadPerformPerform + 340 (NSThread.m:1247)
24 CoreFoundation 0x000000018a402b5c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 (CFRunLoop.c:1943)
25 CoreFoundation 0x000000018a4024a4 __CFRunLoopDoSources0 + 524 (CFRunLoop.c:1989)
26 CoreFoundation 0x000000018a4000a4 __CFRunLoopRun + 804 (CFRunLoop.c:2821)
27 CoreFoundation 0x000000018a32e2b8 CFRunLoopRunSpecific + 444 (CFRunLoop.c:3113)
28 GraphicsServices 0x000000018bde2198 GSEventRunModal + 180 (GSEvent.c:2245)
29 UIKit 0x00000001903757fc -[UIApplication _run] + 684 (UIApplication.m:2650)
30 UIKit 0x0000000190370534 UIApplicationMain + 208 (UIApplication.m:4092)
31 ESPMobileiOS 0x00000001001f7de4 wrapper_managed_to_native_UIKit_UIApplication_UIApplicationMain_int_string___intptr_intptr (/<unknown>:1)
32 ESPMobileiOS 0x000000010016a55c UIKit_UIApplication_Main_string___intptr_intptr (UIApplication.cs:79)
33 ESPMobileiOS 0x000000010016a51c UIKit_UIApplication_Main_string___string_string (UIApplication.cs:63)
34 ESPMobileiOS 0x0000000100134214 ESPMobile_iOS_Application_Main_string__ (Main.cs:13)
35 ESPMobileiOS 0x00000001004a9f94 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 244
36 ESPMobileiOS 0x000000010005433c mono_jit_runtime_invoke (mini-runtime.c:2524)
37 ESPMobileiOS 0x00000001000b0918 do_runtime_invoke (object.c:2809)
38 ESPMobileiOS 0x00000001000b293c mono_runtime_exec_main (object.c:4585)
39 ESPMobileiOS 0x00000001000b2558 mono_runtime_run_main (object.c:4134)
40 ESPMobileiOS 0x000000010003e738 mono_jit_exec (driver.g.c:1048)
41 ESPMobileiOS 0x0000000100133b68 xamarin_main (monotouch-main.m:487)
42 ESPMobileiOS 0x00000001011cef80 main (main.arm64.m:115)
43 libdyld.dylib 0x00000001893115b8 start + 4
What I can see, is that something is going wrong when you try to run some code on the ui thread. The following line tells me this UIKit_UIKitSynchronizationContext__Postc__AnonStorey0__m__0 (UIKitSynchronizationContext.cs:24).
It's very hard to tell exactly what the problem is or in which file the problem is. Maybe implement insights are another crash logger. So you get more info about the crash.
I have been getting crash reports like this for a keyboard extension I have developed and am either confused about how to read the stack trace or why it is occurring or both and I was hoping someone could help me clear this up.
Below is the stack trace:
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0xd15db9df
Thread : Crashed: com.apple.main-thread
0 libobjc.A.dylib 0x37949f66 objc_msgSend + 5
1 UIKit 0x2cd57f05 -[_UIViewControllerTransitionContext completeTransition:] + 52
2 UIKit 0x2d10ac1f __95-[_UIWindowAnimationController _performLayoutAnimationWithContext:windowGeometryUpdatingBlock:]_block_invoke88 + 26
3 UIKit 0x2cc7b8e1 -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:] + 308
4 UIKit 0x2cc7b4f9 -[UIViewAnimationState sendDelegateAnimationDidStop:finished:] + 184
5 UIKit 0x2cc7b40f -[UIViewAnimationState animationDidStop:finished:] + 70
6 QuartzCore 0x2c660fe7 CA::Layer::run_animation_callbacks(void*) + 234
7 libdispatch.dylib 0x37ecdc6f _dispatch_client_callout + 22
8 libdispatch.dylib 0x37ed9553 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1322
9 CoreFoundation 0x295ac889 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 8
10 CoreFoundation 0x295aafa9 __CFRunLoopRun + 1512
11 CoreFoundation 0x294f69a1 CFRunLoopRunSpecific + 476
12 CoreFoundation 0x294f67b3 CFRunLoopRunInMode + 106
13 GraphicsServices 0x30e911a9 GSEventRunModal + 136
14 UIKit 0x2cca7635 UIApplicationMain + 1440
15 libxpc.dylib 0x3806f9e3 _xpc_objc_main + 706
16 libxpc.dylib 0x38071009 xpc_main + 168
17 Foundation 0x2a3ec289 service_connection_handler + 162
18 PlugInKit 0x32c5ff75 -[PKService run] + 508
19 PlugInKit 0x32c5fc4b +[PKService main] + 58
20 PlugInKit 0x32c5ffa9 +[PKService _defaultRun:arguments:] + 20
21 libextension.dylib 0x371b60c5 NSExtensionMain + 48
22 libdyld.dylib 0x37f0baaf start + 2
In the left column where it lists the libraries (correct term?) I don't see any reference to my code. In other crash logs there is always some reference to a class in my app or something but I don't see that in this one. What does that mean? Is the crash occurring before my code executes and this is an Apple issue I can ignore?
It's an Apple Bug. The keyboard extension I work on has a nearly identical crash report. Fortunately, this only seems to happen on iOS 8, though I have seen a similar one that affects iOS 9.
I would file a bug report with Apple, and include a copy of the stack trace.
I am getting this crash for my iOS app and it doesn't show any relevant file name (just shows main.m) that I can look at. Any pointers on what the issue could be?
Exception Type: SIGSEGV
Exception Codes: SEGV_ACCERR at 0x7ebf14b8
Crashed Thread: 0
Thread 0 Crashed:
0 libobjc.A.dylib 0x3892860c objc_retain + 12
1 CoreData 0x2defa915 -[NSFetchedResultsController(PrivateMethods) _managedObjectContextDidChange:] + 4013
2 CoreFoundation 0x2e144f41 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 13
3 CoreFoundation 0x2e0b8da9 _CFXNotificationPost + 1721
4 Foundation 0x2eaa3cc5 -[NSNotificationCenter postNotificationName:object:userInfo:] + 73
5 CoreData 0x2def994b -[NSManagedObjectContext(_NSInternalNotificationHandling) _postObjectsDidChangeNotificationWithUserInfo:] + 79
6 CoreData 0x2def98e3 -[NSManagedObjectContext(_NSInternalChangeProcessing) _createAndPostChangeNotification:withDeletions:withUpdates:withRefreshes:] + 299
7 CoreData 0x2def7f9f -[NSManagedObjectContext(_NSInternalChangeProcessing) _processRecentChanges:] + 2323
8 CoreData 0x2df61c21 -[NSManagedObjectContext(_NestedContextSupport) _parentProcessSaveRequest:inContext:error:] + 1313
9 CoreData 0x2df6256f __82-[NSManagedObjectContext(_NestedContextSupport) executeRequest:withContext:error:]_block_invoke + 563
10 libdispatch.dylib 0x38e08b3b _dispatch_barrier_sync_f_slow_invoke + 71
11 libdispatch.dylib 0x38e02d3f _dispatch_client_callout + 23
12 libdispatch.dylib 0x38e056c3 _dispatch_main_queue_callback_4CF + 279
13 CoreFoundation 0x2e14d681 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
14 CoreFoundation 0x2e14bf4d __CFRunLoopRun + 1309
15 CoreFoundation 0x2e0b6769 CFRunLoopRunSpecific + 525
16 CoreFoundation 0x2e0b654b CFRunLoopRunInMode + 107
17 GraphicsServices 0x330236d3 GSEventRunModal + 139
18 UIKit 0x30a15891 UIApplicationMain + 1137
19 MyApp 0x00034f7f main (main.m:18)
You need to enable the symbolication in order to see where the crash was caused in your code.
For further info check this Apple Documentation or this answer on Stack Overflow