“eskimo”

I want to highlight a couple of points in the releases notes for the software that we seeded yesterday: Xcode 26.4 Beta Release Notes documents new entitlements that allow your app to deploy back to pre-xyzOS 26 systems (search for 168185600 to find the info). iOS & iPadOS 26.4 Beta Release Notes document that hard mode is now an option (search for 160719439). I haven’t had a chance to play with this yet, but I encourage you to take it for a spin and lemme know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to highlight a couple of points in the releases notes for stuff that we seeded yesterday: Xcode 26.4 Beta Release Notes documents new entitlements that allow your app to deploy back to pre-xyzOS 26 systems (search for 168185600 to find the info). iOS & iPadOS 26.4 Beta Release Notes document that hard mode is now an option (search for 160719439). I haven’t had a chance to play with this stuff yet, but I encourage you to take it for a spin and lemme know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

A good place to start here is Enabling enhanced security for your app. The only one of these settings that actively reduces security is Enable Soft Mode for Memory Tagging. However, that currently has no effect because our shipping systems run all third-party apps is soft mode regardless of that setting. See this thread for more about that. Be aware that certain settings can cause problems with deploying to systems prior to xyzOS 26.0. We’ve fixed this in Xcode 26.4 beta. See the Xcode 26.4 Beta Release Notes for more (search for 168185600). But, generally, my general advice is that you enable all the extra stuff and then only disable something if it causes problems that you can’t otherwise resolve. Finally, there are a couple of upcoming Meet with Apple sessions focused on security, and those are a great opportunity to learn more about this. See here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Historically there was no supported way to transfer an app group ID between teams, so my advice has always been to simply create a new app group ID in the new team and have the new app and its appex use that app group. However, there’s been a recent development in this space. I’m currently researching that, and I’ve made a note to come back here once I learn more. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815753021, AkshayKalucha, /thread/815753, /profile/AkshayKalucha'] We are currently observing NEVPNConfigurationChangeNotification [/quote] That is the canonical way to do this. [quote='815753021, AkshayKalucha, /thread/815753, /profile/AkshayKalucha'] it appears to have inconsistent behavior when … VPN configurations are installed programmatically via MDM systems [/quote] What do you mean by “inconsistent”? Your steps to reproduce indicate that this fails every time, which seems pretty consistent to me (-: Are you saying that this is inconsistent with the documented behaviour? Or are you seeing the problem intermittently? Either way, this sounds like a bug to me and I encourage you to file it as such. Make sure to include a sysdiagnose log taken shortly after reproducing the problem and, for bonus points, enable additional logging per the VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page. Please post your bug number, just for the record. On the workaround front: Do

This isn’t an answer to the question you asked but… [quote='815452021, Philipss, /thread/815452, /profile/Philipss'] When launching an app in a Rosetta simulator [/quote] See my response on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='876059022, jzilske, /thread/815493?answerId=876059022#876059022, /profile/jzilske'] the exception reason tripped me up at first: [/quote] Yeah, I’ve been mislead by that in the past. Fortunately, this time I remembered the mantra that we here in DTS chant steadily throughout the day: Always start with a crash report. Always start with a crash report. Almost start with a crash report. … (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I didn’t reply earlier because I didn’t see your comments )-: See tip 5 in Quinn’s Top Ten DevForums Tips. Regarding FB20753534, I’ve got no info to share on that front. I can’t talk about Apple’s internal processes and I can’t offer predictions about The Future™. Having said that, iOS 26 has been shipping for a while now, so even if this behaviour changed today you’d still have to decide what to do about all the existing iOS 26 installs. And once you make that decision, which admittedly might involve some tough choices )-:, there’s less pressure on you getting a resolution from Apple. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='876243022, disinghal, /thread/811887?answerId=876243022#876243022, /profile/disinghal'] It's MacOS [/quote] D’oh! Yes, sorry, I had my iOS coloured glasses on )-: [quote='876243022, disinghal, /thread/811887?answerId=876243022#876243022, /profile/disinghal'] We are calling some custom extension using Apple's enterprise single sign-on feature. [/quote] So your packet tunnel provider is using URLSession to issue a request that’s triggering enterprise SSO which then ends up calling an SSO app extension? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Yeah, this isn’t super surprising. errOSAInternalTableOverflow isn’t something I have a lot of experience with but it seems like it’s primarily associated with AppleScript’s garbage collector. At least one of the places that raise this error logs relevant info to the system log, so you should have a rummage around in there to see if anything interesting pops out. See Your Friend the System Log for my advice on how to wrangle the system log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='876196022, omeriadon, /thread/812607?answerId=876196022#876196022, /profile/omeriadon'] Are we not allowed to add a package normally and the judging computer download the package? [/quote] In the fine print we specifically state that your playground is expected to work without a network connection. For other hints and tips on this topic, see my reply on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad to hear you got this sorted out. I recommend that you read the following, which might explain some of the pathologies you encountered: Creating distribution-signed code for macOS (specifically, the bit about not using sudo) The Care and Feeding of Developer ID Resolving errSecInternalComponent errors during code signing Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The documentation for our low-level APIs is quite scattered, something I going into detail in in Availability of Low-Level APIs. In this specific case a good start is the header itself, which has this key titbits: Note that the validity of the addresses returned correspond to the validity reader You’re passing in NULL, which gives you the in-memory reader, which returns everything directly, and thus doesn’t need to be deallocated. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad to hear that you got this sorted. [quote='876168022, kjw1978, /thread/815604?answerId=876168022#876168022, /profile/kjw1978'] Do NOT add the entitlement to app.json. [/quote] Correct. [quote='876168022, kjw1978, /thread/815604?answerId=876168022#876168022, /profile/kjw1978'] Apple now treats MusicKit as a Runtime Service [/quote] The word “now” is misleading, in that it suggests that this changed at some point. That’s not the case. MusicKit has never used entitlements. Indeed, trying to use an entitlement for this is one of the common mistakes I call out in Determining if an entitlement is real. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If you search the ’net for “Unsupported Swift Architecture”, you’ll find a bunch of helpful advice on this front. My additions to that are: If you’re using third-party tooling or libraries, seek help from the support channel for the relevant vendor. TN3117 Resolving architecture build errors on Apple silicon describes best practices for your build architecture settings. Check your settings to make sure you’re following them. If you get stuck, try to isolate the problem into a small test project and then share that here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com