We were unable to review your app as it crashed on launch

App Store Distribution & Marketing App Review
FEIB
FEIB OP
Created Mar ’24
Replies 7
Boosts 0
Views 1.3k
Participants 7

Hello,

The following issues I am facing, and I have already referenced solutions from https://forums.developer.apple.com/forums/thread/747895.

However, Apple still rejected and respond same issue "crashed on launch". There has two weird points:

  1. It's iPhone App. Why Apple review it via iPad Air?
  2. I have downloaded the test through TestFlight, and there have no crash happened either iPhone or iPad.

================================================================

Guideline 2.1 - Performance - App Completeness

We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue.

Review device details:

  • Device type: iPad Air (5th generation)
  • OS version: iOS 17.3.1

Next Steps

To address the crash in your app, follow these steps:

  1. Fully symbolicate the crash report. See Adding Identifiable Symbol Names to a Crash Report for an explanation of the symbolication process.
  2. Match the crash report to a common pattern. Based on the pattern, take specific actions to further investigate the crash. See Identifying the Cause of Common Crashes.
  3. Test your app on a device to ensure that it now runs as expected.
  4. Once you’ve addressed the crash, create and submit a new build to the App Store for review.

Resources

For additional information on crash reports, see Diagnosing Issues Using Crash Reports and Device Logs.

Support

  • Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module.
  • Consult with fellow developers and Apple engineers on the Apple Developer Forums.
  • Help improve the review process or identify a need for clarity in our policies by suggesting guideline changes.
Replies  7
Boosts  0
Views  1.3k
Participants  7
Brayden-hoo
Brayden-hoo OP
Mar ’24

Same here. Even though I passed the same code last week, they rejected it due to the crash on launch. I think the test code that the Apple development team uses has some issues.

0
againNagain
againNagain OP
Mar ’24

I have the same problem. That's my symbolicate crash report. I got the same rejection on two games with the same crashed thread. I tried many things it didn't work.

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6

Triggered by Thread: 2

Thread 2 name: Dispatch queue: com.apple.root.default-qos Thread 2 Crashed: 0 libsystem_kernel.dylib 0x1e3bfe974 __pthread_kill + 8 1 libsystem_pthread.dylib 0x1f763d0ec pthread_kill + 268 2 libsystem_c.dylib 0x1a36b7b80 abort + 180 3 libc++abi.dylib 0x1f755cccc abort_message + 132 4 libc++abi.dylib 0x1f754ce84 demangling_terminate_handler() + 348 5 libobjc.A.dylib 0x1936be0bc _objc_terminate() + 144 6 libc++abi.dylib 0x1f755c090 std::__terminate(void (*)()) + 16 7 libc++abi.dylib 0x1f755c034 std::terminate() + 108 8 libdispatch.dylib 0x1a35fede8 _dispatch_client_callout + 40 9 libdispatch.dylib 0x1a3601f6c _dispatch_queue_override_invoke + 928 10 libdispatch.dylib 0x1a3610894 _dispatch_root_queue_drain + 392 11 libdispatch.dylib 0x1a361109c _dispatch_worker_thread2 + 156 12 libsystem_pthread.dylib 0x1f7638ee4 _pthread_wqthread + 228 13 libsystem_pthread.dylib 0x1f7638fc0 start_wqthread + 8

Thread 2 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x00000001f75612c3 x5: 0x000000016d6bede0 x6: 0x000000000000006e x7: 0x0000000000002600 x8: 0x6d61676ad664dda5 x9: 0x6d61676bbb0f2da5 x10: 0x0000000000000200 x11: 0x000000016d6be910 x12: 0x0000000000000000 x13: 0x00000000001ff800 x14: 0x0000000000000010 x15: 0x0000000000000000 x16: 0x0000000000000148 x17: 0x000000016d6bf000 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000001803 x21: 0x000000016d6bf0e0 x22: 0x0000000000000114 x23: 0x0000000000000000 x24: 0x000000016d6bf0e0 x25: 0x00000001fcbe5200 x26: 0x00000000000005ff x27: 0x00000001fde0f044 x28: 0x0000000000000000 fp: 0x000000016d6bed50 lr: 0x00000001f763d0ec sp: 0x000000016d6bed30 pc: 0x00000001e3bfe974 cpsr: 0x40001000 far: 0x0000000000000000 esr: 0x56000080 Address size fault

0
againNagain
againNagain OP
Mar ’24

I have the same problem. That's my symbolicate crash report in the pictures. I got the same rejection on two games with the same crashed thread. I tried many things it didn't work.

0
Weslei_rs
Weslei_rs OP
Apr ’24

@FEIB @againNagain Were you able to identify the error?

0
Muslamica
Muslamica OP
Jul ’24

i have this issue with eas built app. any suggestions ?

0
Selectorshub
Selectorshub OP
Jan ’25

I also got into this trap and now they are rejecting every build with this issue. Surprisingly ipad air 5th gen is not there in their xcode so how can we even test?

0
farhansajid
farhansajid OP
Jun ’25

Looks like I"m having the same issue, I'm genuinely not sure what's going on with that Ipad air (fifth generation)

0
We were unable to review your app as it crashed on launch
First post date Last post date
 
 
Q