DTiPhoneSimulatorErrorDomain Code 2

I've encountered this exact same problem. I follow this guide to a tee: https://developer.apple.com/documentation/xcode/configuring-your-app-to-use-alternate-app-icons And yet I am consistently hit with: Failed: Error Domain=NSPOSIXErrorDomain Code=35 Resource temporarily unavailable UserInfo={_LSFile=LSIconAlertManager.m, _LSLine=113, _LSFunction=-[LSIconAlertManager iconChangeAlertTokenForIdentity:error:]} My app targets iPads and iPhones, has a minimum version for iOS of 18, and I am not using a simulator, I am running on my own device (iPhone 17 on iOS 26.2). This has been driving me insane. The example project Apple provides works, so I cannot see what possibly could be different.

The sandbox-relaxed mode works up to 26.1 and stopped working in 26.2. So, with a bit more digging, I was able to figure out what's going on here. Basically, as part of a security fix (r.157744252) in macOS 26.2, CUPS was changed to use a fixed configuration, by its config file (/etc/cups/cups-files.conf). That's actually what explains this: As an alternative to the relaxed mode, we also tried Sandboxing off, but that doesn't help either (from CUPS scheduler/conf.h). ...as CUPS was actually always running at CUPSD_SANDBOXING_STRICT, regardless of how you configured it. Is there anything we can configure or modify in the system to achieve the old behaviour of sandbox-relaxed mode? If for some reason, we can’t get back to the previous sandbox-relaxed behaviour, is there a way for us to switch off the sandbox? No, I don't think so. The core problem here is that the sandbox configuration itself hasn't actually changed; cupsd is just ignoring any configuration file. I think you can see this directly if you try pas

Why not just have a way to allow the user to buy the IAP without having to play for 5 minutes? If there's some sort of menu screen just add a way of buying the IAP from there. Some users might play your game for two minutes ten times and never see the screen that appears after five minutes, but they might like it enough to buy it. One of my apps lets you add three things in the free version, and unlimited things once you've bought the IAP, but you don't have to add exactly three things before the buy button appears; it's always there.

@MegaWatt Feel free to reply with focused sample code that runs without any external dependencies, unless absolutely necessary for the issue to be replicated, and I can take a look if something fishy is going on 🎣🔍💭. Please note which iOS and Xcode version is used, thank you.  Travis Trotto - DTS Engineer

I see the navigationTitle as expected without being provided the same myItems, .surfacePrimary and .surfaceSecondary that you used (I used an EmptyView and two generic color options). If the issue persists when you remove these dependencies, please file a bug report that mentions what exact version(s) of iOS and Xcode is affected. Share the FB number and updated sample code below and I can investigate accordingly. Thank you,  Travis Trotto - DTS Engineer

Same here. Tried to enroll on December 30th, their two business days to review the enrollment are surprisingly long. I know that with Christmas and New Year, many people are off, but still… I couldn’t find a phone number, I don’t get replies to mails. Did anyone get approved during the past week or so?

A character encoding reflects the way the coded character set is mapped to bytes in memory. When using Terminal on macOS, you interact with the system via inputting characters, and the system needs to know how the characters are laid out in memory, which is the character encoding. Terminal by default uses UTF-8, which is described in the LANG environment, as you have noticed. In a Cocoa app, you handle text, which is a series of characters, via the Cocoa framework. Typically, you create a piece of text using String in Swift, or NSString in Objective C, and pass it to the system for text rendering. When creating a string type, you need to specify the encoding of your content – You can see that the init methods of Swift.String and NSString typically have an encoding parameter. If you don't, you are assumed to use the default encoding, which is UTF-8 for Swift.String and UTF-16 for NSString. Other than that, you most likely don't need to care the character encoding. Having said that, I am curious why yo