Thanks, I created https://developer.apple.com/forums/thread/776304

I just wanted to give a quick update on my earlier statement: [quote='796483022, Nickkk, /thread/760029?answerId=796483022#796483022, /profile/Nickkk'] Regarding the first crash, I noticed something strange. The crash report seems to imply that a particular method called another one, which is impossible. [/quote] I was just having a look at some completely different crash reports downloaded by Xcode, and I noticed the same wrong pattern: the crash reports indicate that method A calls method B, which is impossible. In one particular case, method A that is triggered by the press of a button (and nothing else) seems to be called by method B that can be triggered by a context menu (or keyboard shortcut). The rest of the stack trace confirm that it's indeed the button that was pressed. This seems to me like a quite serious bug in how macOS creates crash reports. Should I open a new forum post and bug report to discuss this, or would you like to go on here?

How do I enable Game Center debug logging?

What I find strange is that the Mac logs starting match with local player A:_5b773e1b128bcf2b710fda6ca683bc43 and remote players ["A:_23dc24e3273fb327ce3a17c34a6c390a"] while the iPhone logs starting match with local player A:_23dc24e3273fb327ce3a17c34a6c390a and remote players ["174148222230085984"] Note how the player id for the iPhone matches on both devices, while the player id for the Mac is different. Not sure if this is expected. At first I thought this might be related to not being able to determine the hosting player, but this also happens in the rare case when the hosting player can be determined successfully.

Thanks for your insights. Unfortunately I don't have any more information about the crash: the crash report downloaded by Xcode is all I have. I think this is the first time I've seen this kind of crash. Whenever I see a crash report that gives me no clue about what the issue is, I have no choice but to assume that it's something unrelated to my own code, but if that's really the case, then in my opinion I shouldn't even get the crash report at all, since I cannot do anything about it. Looking into these reports only to realize that there's nothing I can do about it still takes quite some time when summing them all up. I thought I might still ask if there's anything I can do.

Xcode just downloaded a similar crash report, only with Exception Type: EXC_CRASH (SIGABRT) and OS Version: macOS 15.3.1 (24D70). crash.crash

Well, without a GKMatch it's not possible to exchange data with the other players.

Thank you for your insight!

That guide is only useful if you can actually reproduce the issue, but like I said, I cannot reproduce it and the crash was downloaded by Xcode (it happened on another user's Mac).

Unfortunately, like mentioned previously, this is a crash report downloaded by Xcode, and I have no idea how I could reproduce it.

I often have the same issue with crash reports from other users downloaded by Xcode. Right now I had this issue with a crash report transferred from a different partition on my Mac where I tested my app on an older macOS version (macOS 12). Usually I use the atos Terminal command, but surprisingly this time that command never returns or prints anything, even after waiting for 10 minutes. When dragging the crash log to Xcode, the console prints out error: unable to locate main executable (arm64) "~/Downloads/myApp.app/Contents/MacOS/myApp" error: unable to locate main executable (arm64e) "/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit" error: unable to locate main executable (arm64e) "/usr/lib/system/libdispatch.dylib" error: unable to locate main executable (arm64e) "/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation" error: unable to locate main executable (arm64e) "/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox" error: unable to locate main executable (arm64e) "/usr/lib/dyld" error: unable to locate main executable (arm64e) "/usr/lib/system/libsystem_pthread.dylib" error: unable to locate main executable (arm64e) "/usr/lib/system/libsystem_kernel.dylib" crashlog.create_target()...2 crashlog.create_target()...3 crashlog.create_target()...4 error: Unable to locate any executables from the crash log. Try loading the executable into lldb before running crashlog and/or make sure the .dSYM bundles can be found by Spotlight. error: invalid target error: invalid target error: invalid target error: invalid target error: invalid target error: invalid target which seems strange, as it isn't even able to locate the system libraries. Then I opened the crash report in TextEdit and replaced all references to the app path (previously in /Downloads) with the location of the Xcode archive (\/Users\/username\/Library\/Developer\/Xcode\/Archives\/2025-02-12\/myApp macOS 12.02.2025, 08.45.xcarchive\/Products\/Applications\/*\/myApp.app\/Contents\/MacOS\/myApp) and then Xcode symbolication seemed to work ("seemed" because the crash still doesn't make sense to me: apparently it crashed on the line window.toolbar = toolbar which works fine on macOS 15).

Thanks for the detailed explanation. I filed FB16470722. I ran the sample app again but after unmounting the volume and resolving the bookmark with an error, the Files app doesn't show the volume.

Thanks for the detailed explanation. I filed FB16481526.

Thanks for checking. I opened FB16457804. What do XX_NECESSARY_INFO_1 and XX_NECESSARY_INFO_2 mean?

[quote='824169022, DTS Engineer, /thread/770421?answerId=824169022#824169022'] There's a lot of inter-process communication that happens with system features that are hidden away from what you need to worry about at the API level. [/quote] Of course that's very pleasant for us in the end and how it should be. It's just unexpectedly easy for someone used to various XPC mechanisms and distributed notifications to communicate between processes.