iOS Crash on startup on iOS 15.1

My app is crashing on startup and this is the crash log I get. Can anyone help me interpret whats going on here?

vStores.iOS 1-18-22, 12-28 PM.crash
Up vote post of jcookVF Down vote post of jcookVF
1.4k views
Posted by
jcookVF
Reply
Add a Comment

Accepted Reply

here is the symbolicated crash report

Thanks.

Looking at the crashed thread I see this:

Thread 0 name:  tid_103 Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libsystem_kernel.dylib  … __pthread_kill + 8
1   libsystem_pthread.dylib … pthread_kill + 208
2   libsystem_c.dylib       … abort + 120
3   vStores.iOS             … xamarin_unhandled_exception_handler + 60
4   vStores.iOS             … mono_invoke_unhandled_exception_hook + 132
5   vStores.iOS             … mono_handle_exception_internal + 5664
6   vStores.iOS             … mono_handle_exception + 56
7   vStores.iOS             … mono_arm_throw_exception + 360
8   vStores.iOS             … throw_exception + 172
9   vStores.iOS             … vStores_iOS_Application_Main_string__ + 52
10  vStores.iOS             … wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 272
11  vStores.iOS             … mono_jit_runtime_invoke + 1136
12  vStores.iOS             … mono_runtime_invoke_checked + 148
13  vStores.iOS             … mono_runtime_exec_main_checked + 128
14  vStores.iOS             … mono_jit_exec + 376
15  vStores.iOS             … xamarin_main + 1052
16  vStores.iOS             … main + 76
17  dyld                    … start + 444

Based on the symbol names in the backtrace it seems that your C# code has thrown an unhandled language exception which has caused its runtime to call abort. I don’t know enough about this third-party runtime to offer further advice here. I recommend you escalate this via their support channel.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Post marked as solved

  • Thank you, I will try that

    —
    jcookVF
Add a Comment

Replies

Exception Type:  EXC_CRASH (SIGABRT)

This means that your app deliberately crashed itself by calling abort. Usually this is the result of an unhandled language exception. However, your crash report doesn’t include a Last Exception Backtrace section, so that’s not the case here. Instead we need to focus on the crashing thread’s backtrace:

Thread 0 name:  tid_103 Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libsystem_kernel.dylib  … __pthread_kill + 8
1   libsystem_pthread.dylib … pthread_kill + 208
2   libsystem_c.dylib       … abort + 120
3   vStores.iOS             … 0x1006b8000 + 51811004
4   vStores.iOS             … 0x1006b8000 + 50528860
5   vStores.iOS             … 0x1006b8000 + 50090964
6   vStores.iOS             … 0x1006b8000 + 50085288
7   vStores.iOS             … 0x1006b8000 + 50043684
8   vStores.iOS             … 0x1006b8000 + 5809788
9   vStores.iOS             … 0x1006b8000 + 1806356
10  vStores.iOS             … 0x1006b8000 + 5549216
11  vStores.iOS             … 0x1006b8000 + 50163996
12  vStores.iOS             … 0x1006b8000 + 50924792
13  vStores.iOS             … 0x1006b8000 + 50950060
14  vStores.iOS             … 0x1006b8000 + 50025772
15  vStores.iOS             … 0x1006b8000 + 51845936
16  vStores.iOS             … 0x1006b8000 + 1806180
17  dyld                    … start + 444

As you can see, frame 3 is your code and it’s directly called abort. It’s hard to make further progress because your frames are not symbolicated. You need to fix that, per Adding Identifiable Symbol Names to a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment

Sorry for the late reply, here is the symbolicated crash report

vStores.iOS 1-31-22, 12-43 PM.crash
Posted by
jcookVF
Post not yet marked as solved Up vote reply of jcookVF Down vote reply of jcookVF
Add a Comment

here is the symbolicated crash report

Thanks.

Looking at the crashed thread I see this:

Thread 0 name:  tid_103 Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libsystem_kernel.dylib  … __pthread_kill + 8
1   libsystem_pthread.dylib … pthread_kill + 208
2   libsystem_c.dylib       … abort + 120
3   vStores.iOS             … xamarin_unhandled_exception_handler + 60
4   vStores.iOS             … mono_invoke_unhandled_exception_hook + 132
5   vStores.iOS             … mono_handle_exception_internal + 5664
6   vStores.iOS             … mono_handle_exception + 56
7   vStores.iOS             … mono_arm_throw_exception + 360
8   vStores.iOS             … throw_exception + 172
9   vStores.iOS             … vStores_iOS_Application_Main_string__ + 52
10  vStores.iOS             … wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 272
11  vStores.iOS             … mono_jit_runtime_invoke + 1136
12  vStores.iOS             … mono_runtime_invoke_checked + 148
13  vStores.iOS             … mono_runtime_exec_main_checked + 128
14  vStores.iOS             … mono_jit_exec + 376
15  vStores.iOS             … xamarin_main + 1052
16  vStores.iOS             … main + 76
17  dyld                    … start + 444

Based on the symbol names in the backtrace it seems that your C# code has thrown an unhandled language exception which has caused its runtime to call abort. I don’t know enough about this third-party runtime to offer further advice here. I recommend you escalate this via their support channel.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Post marked as solved

  • Thank you, I will try that

    —
    jcookVF
Add a Comment

Hi @jcookVF ,

Wondering if you are able to find the reason behind this crash. I am facing similar crash but on iOS 16.5.1 while developing app using MAUI.

Thanks in advance.

Posted by
mudit.jain@renishaw
Post not yet marked as solved Up vote reply of mudit.jain@renishaw Down vote reply of mudit.jain@renishaw

  • Hi @mudit.jain@renishaw @jcookVF @eskimo,

    I'm also experiencing a similar issue with a .Net Maui app (.Net 8). Running on Android, Windows and iOS is fine in debug and even in release mode while deploying from Visual Studio 2022 or VS Code, but when deployed for testing via App Center the iOS app crashes immediately and doesn't offer much information about what went wrong.

    I've tried the suggestion from here, but it's hasn't made a difference.

    Did anyone figure out the problem?

    Thanks,

    —
    BenEastpoint
Add a Comment