Native Crash - Unknown Function (/usr/lib/system/libsystem_kernel.dylib) Unknown Function (/usr/lib/system/libsystem_kernel.dylib)

Question

EternalForge OP

Created 2w

Replies 4

Boosts 0

Participants 2

Hi,

I encountered the following error while trying to launch a video game developed with Unity and running on an iPhone 12 and iPhone 16 Pro.

Native StackTrace:

Thread 2 (crashed) 0 libsystem_kernel.dylib 0x00000001d40102ec <symbols missing for uuid: 21ee5290d1193c31b948431865a67738> 1 libsystem_c.dylib 0x000000019330fba0 <symbols missing for uuid: 7135c2c8ba5836368b46a9e6226ead45> 2 UnityFramework 0x000000010e7bc744 <symbols missing for uuid: 4c1540b0ca733555aa69fc3e514204a3> 3 UnityFramework 0x000000010dc1c22c <symbols missing for uuid: 4c1540b0ca733555aa69fc3e514204a3> 4 UnityFramework 0x000000010cc26da4 <symbols missing for uuid: 4c1540b0ca733555aa69fc3e514204a3> 5 CoreFoundation 0x000000018b4af984 <symbols missing for uuid: 76a3b1983c09323e83590d4978e156f5> 6 libobjc.A.dylib 0x0000000183277140 <symbols missing for uuid: afdf5874bc3b388e864cdc9f4cdbf4f0> 7 libc++abi.dylib 0x00000001e7d20068 <symbols missing for uuid: b613e600b39c3bbf8e098a1466610355> 8 libc++abi.dylib 0x00000001e7d2000c <symbols missing for uuid: b613e600b39c3bbf8e098a1466610355> 9 libdispatch.dylib 0x0000000193256de8 <symbols missing for uuid: 5f66cdb608a936158c6a4e3b47005495> 10 libdispatch.dylib 0x000000019325e400 <symbols missing for uuid: 5f66cdb608a936158c6a4e3b47005495> 11 libdispatch.dylib 0x000000019325ef30 <symbols missing for uuid: 5f66cdb608a936158c6a4e3b47005495> 12 libdispatch.dylib 0x0000000193269cb4 <symbols missing for uuid: 5f66cdb608a936158c6a4e3b47005495> 13 libdispatch.dylib 0x0000000193269528 <symbols missing for uuid: 5f66cdb608a936158c6a4e3b47005495> 14 libsystem_pthread.dylib 0x00000001e7e00934 <symbols missing for uuid: e4a9d6dbf93b3c88bdd185671ec22e2b> 15 libsystem_pthread.dylib 0x00000001e7dfd0cc <symbols missing for uuid: e4a9d6dbf93b3c88bdd185671ec22e2b>

Answered by DTS Engineer in 856271022

Yes!

If you Quick Look that in the Finder, you’ll get a human readable version of it. My comments below are based on that.

The presence of the Last Exception Backtrace section indicates that your app crashed due to an unhandled language exception. Looking at the associated backtrace I see this:

Last Exception Backtrace:
0   CoreFoundation    … __exceptionPreprocess + 164
1   libobjc.A.dylib   … objc_exception_throw + 88
2   CoreFoundation    … +[NSObject(NSObject) _copyDescription] + 0
3   CoreFoundation    … ___forwarding___ + 1492
4   CoreFoundation    … _CF_forwarding_prep_0 + 96
5   UnityFramework    … 0x10b164000 + 26948776
6   UnityFramework    … 0x10b164000 + 26953748
7   UnityFramework    … 0x10b164000 + 26918904
8   UnityFramework    … 0x10b164000 + 26917296
9   UnityFramework    … 0x10b164000 + 26902496
10  UnityFramework    … 0x10b164000 + 27452572
11  libdispatch.dylib … _dispatch_call_block_and_release + 32

Frame 11 is Dispatch calling a block on a queue. Frames 10 through 5 are your third-party runtime. Frames 4 through 0 are a telltale pattern you see when you call an Objective-C method on an object that doesn’t support that method. There are two common causes:

You really are mixing up object types, for example, calling string methods on data objects.
You have an over-release bug, meaning that the original object was deallocated and some other object of a different type happened to use the same memory.

There are standard memory debugging tools that can help you with this.

Another thing to do here is to symbolicate frames 10 through 5. That might give you a clue as to what part of your code is triggering this issue. For info on how to do that, see Adding identifiable symbol names to a crash report.

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

Boost

Answer 1

DTS Engineer OP

Apple

2w

Please post a full Apple crash report. See Posting a Crash Report for advice on how to do that.

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

0

Answer 2

DTS Engineer OP

Apple

1w

[It seems that the mods didn’t like your previous post. Normally I might try to fix that but there’s no point in this case, as will become clear.]

is this?

No. The xcode://… URL you posted is useful if you want to share a crash with another member of your team, but I’m looking for a .crash or, better yet, a .ips file. Posting a Crash Report explains how to get these.

IMPORTANT From the context it’s clear that you’re looking at a crash report in the Xcode organiser. I’ve just updated Posting a Crash Report to explain how to get a .crash file from there. See the new Getting a Crash Report from the Xcode Organiser section.

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

0

Answer 3

EternalForge OP

1w

NavalConquest-2025-08-29-171558.ips

This one?

0

Answer 4

DTS Engineer OP

Apple

5d

Recommended

Yes!

If you Quick Look that in the Finder, you’ll get a human readable version of it. My comments below are based on that.

The presence of the Last Exception Backtrace section indicates that your app crashed due to an unhandled language exception. Looking at the associated backtrace I see this:

Last Exception Backtrace:
0   CoreFoundation    … __exceptionPreprocess + 164
1   libobjc.A.dylib   … objc_exception_throw + 88
2   CoreFoundation    … +[NSObject(NSObject) _copyDescription] + 0
3   CoreFoundation    … ___forwarding___ + 1492
4   CoreFoundation    … _CF_forwarding_prep_0 + 96
5   UnityFramework    … 0x10b164000 + 26948776
6   UnityFramework    … 0x10b164000 + 26953748
7   UnityFramework    … 0x10b164000 + 26918904
8   UnityFramework    … 0x10b164000 + 26917296
9   UnityFramework    … 0x10b164000 + 26902496
10  UnityFramework    … 0x10b164000 + 27452572
11  libdispatch.dylib … _dispatch_call_block_and_release + 32

Frame 11 is Dispatch calling a block on a queue. Frames 10 through 5 are your third-party runtime. Frames 4 through 0 are a telltale pattern you see when you call an Objective-C method on an object that doesn’t support that method. There are two common causes:

You really are mixing up object types, for example, calling string methods on data objects.
You have an over-release bug, meaning that the original object was deallocated and some other object of a different type happened to use the same memory.

There are standard memory debugging tools that can help you with this.

Another thing to do here is to symbolicate frames 10 through 5. That might give you a clue as to what part of your code is triggering this issue. For info on how to do that, see Adding identifiable symbol names to a crash report.

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

0