LLDB crash

Yes, we see a lot of crashes like this in our apps, too. But we can't reproduce it. OS Version: iPhone OS 18.6 (22G86) Release Type: User Baseband Version: 2.70.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Reason: *** -[__NSSingleObjectArrayI objectAtIndex:]: index 2 beyond bounds [0 .. 0] Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: OurAppName [72412] Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x1950500c0 __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x1924e9abc objc_exception_throw + 88 (objc-exception.mm:356) 2 CoreFoundation 0x1950418c8 -[__NSSingleObjectArrayI objectAtIndex:] + 308 (NSSingleObjectArray.m:18) 3 PrintKitUI 0x1f34d4518 -[UIPrintPaperSizeOption listItemSelected:] + 88 (UIPrintMoreOptions.m:896) 4 PrintKitUI 0x1f34a0a0c -[UIPrintOptionListViewController tableView:didSelectRowAtIndexPath:] + 116 (UIPrintOptionCells.m:103) 5 UIKitCore 0x198b902fc

I am experiencing a similar issue using an Xcode 16.4 with a simulator running IOS 18.6 I receive a series of this message when trying to load products from the StoreKit configuration file: Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) If I enable Zombie Objects in the debugger, I also get these messages: Class _NSZombie_SKProductInternal is implemented in both ?? (0x1347517a0) and ?? (0x1347517d0). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. I've tested the file on a handful of older simulators and everything works fine; neither error is reported on an IOS 18.0 simulator. I've also verified that things are working as expected with TestFlight so I'm less concerned about going to Production. Still, it would be nice be have a much higher level of confidence that there is not a serious bug somewhere before I roll out my next Production release.

Hi @PraneethK, You wrote: I am fallowing the steps mention here https://developer.apple.com/wallet/get-started-with-verify-with-wallet/ and https://developer.apple.com/documentation/passkit/requesting-identity-data-from-a-wallet-pass to run a POC in simulator but I am getting a crash [...] To use Verify with Wallet, you need to submit an entitlement request. Please review the Request the entitlement section of the following page to learn if you app is eligible for this entitlement: Get started with Verify with Wallet API https://developer.apple.com/wallet/get-started-with-verify-with-wallet/ Note: Building an app with this entitlement requires macOS 13 or later. Once you have been approved for the entitlement, review the following documentation as a guide to your implementation: Requesting identity data from a Wallet pass https://developer.apple.com/documentation/passkit/requesting-identity-data-from-a-wallet-pass Lastly, read the section titled Test the implementation for the expected behavior on a

FB19957253 (Crash on Hierarchical List children access from SwiftData inherited model) Again, thank you so much! I hope I gave enough informations, feel free to ask if I can do anything.

Thank you for responding, and so quickly. You are correct on the first point, I don't have multicast entitlements in my app (got a nasty crash when I tried), but I am mostly attempting to send multicast udp packets, and kept hitting a roadblock with these permissions. The issue is with the Local Network Privacy permissions. The reason I think it is this, and not incorrect API usage, is I had the app installed on a brand new Mac Mini, and could not send UDP multicast packets from the app. I then ran the app from the Terminal, and it worked just fine. I realized I was missing these network permissions, and re-built and reinstalled it with these permissions enabled. The app worked temporarily after re-installing, but then restarting the machine, the app would again stop working and still not allow me to send these packets. It would work from the terminal (which says that the API's are used correctly. BSD sockets being what they are...) I then created a new user on that machine, and had no issues with th

We haven't been able to find any causes yet. We've fixed all of the main thread violations we've run into, and I've tried running the app with NSZombies enabled and all of the other memory error aids, but to no avail. It would be nice to gain insight into what might cause this crash.

Thanks a lot for helping Ziqiao, i've made a small iOS App that shows the issue which is available here: https://github.com/fgirardey/SwiftDataInheritance The step to reproduce are: Create a collection named Work Create another collection name Tech that has Work as a parent Kill the app, relaunch and see the crash happening when List is accessing to children through .childrenOrNil.