“Xcode”

[quote='879687022, DTS Engineer, /thread/818501?answerId=879687022#879687022'] If that doesn't help, try to remove the iCloud capability [/quote] Yeah, that’s what I recommend you do first. As Ziqiao says, it’s all disabled, so removing it doesn’t cost you anything. And I think it’ll get your app building again. Once you’re back in that stable state, you can add it back in and let Xcode’s automatic code siging do its thing. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for your reply. I have already filed a report through Feedback Assistant. Case-ID: 18609190 (Apple DTS incident) Feedback ID: 22081725 The issue was submitted on Feb 28, 2026, but so far there has been no update in Feedback Assistant. The problem is still reproducible in Xcode 26.3 with Release (-O) builds when targeting iOS 16/17/18. Could you please help check whether this Feedback has been routed to the appropriate Swift/Xcode engineering team, and whether there is any information about which future Xcode version might include a fix? Thank you very much for your help.

Right -- think I've had a breakthrough: the entitlements file for the appex shows its app ID as follows: [Key] com.apple.application-identifier [Value] [String] $(AppIdentifierPrefix)$(PRODUCT_BUNDLE_IDENTIFIER) while the main app shows a proper value: [Key] com.apple.application-identifier [Value] [String] XXXXXXXXXX.com.mydomain.MyApp For some reason, the Xcode variables weren't being substituted in the FileProvider! The surprise here is simply that the app worked for so long without the entitlements being validated... Anyway. I've confirmed that the app now presents the entitlements validated flag correctly on our older machines; once I hear back from the employee running this on Sequoia that it works now, I'll accept the answer here. Thanks!

@Engineer Thank you for your previous response. We re-verified the behavior, and it appears that the device token that was active before the app was uninstalled is still valid. As a result, two push notifications were delivered to the same device. If you can share the apns-id of two such notifications sent and received (within the last couple of days), we can double check, but what you are describing should not be possible. As requested, I am sharing the details below. Notification sent to the latest token (obtained after reinstalling the app) Request curl -v --http2 --cert cert.p12: --cert-type P12 -H apns-topic: {{bundle_id}} -H apns-push-type: alert -d '{aps:{alert:test1}}' https://api.sandbox.push.apple.com/3/device/{{latest_token}} (timestamp: 2026-03-13T04:37:20Z) APNs response apns-id: 9963707F-7469-1CB3-231A-66B9EC9CFEB3 Xcode log when the notification was received in the foreground (real device) - - - Push Payload Start - - - Push received timestamp: 2026-03-13T04:37:24Z [AnyHashable(a

After trying with several workarounds with the focusable() modifier (snippet for context) Stepper(value: $configuration.time, in: 1...8) { // Stepper Label } .focusable(false) .focusEffectDisabled() I found a different error: onChange(of: ButtonInteractionPhase) action tried to update multiple times per frame. These were the steps to reproduce: Interact with the Picker Try to modify the Stepper You will see the said error in the Xcode console printed after a couple seconds.

I'm glad to hear that was the info you needed. I agree with how the terminology of SDKs, components, platforms, and simulators sprinkled throughout documentation, command line tools, and the Xcode IDE can accidentally mislead in figuring out exactly what you need here. — Ed Ford,  DTS Engineer

We need much more information about the errors you're seeing, the version of Xcode, and so on, in order to assist you. For tips on creating Apple Developer Forums posts that include the necessary info, see tips on writing forums posts.

A few brief clarifications and comments: I am seeking clarification on whether the various driverkit entitlement families (com.apple.developer.driverkit.family.*) are available for development on my local Mac without requesting entitlements from Apple. Making the more explicit, they Development Only entitlement variants do two things: They match against a VERY broad hardware configuration, basically letting you match any hardware. Their ONLY available to Development signed builds. Note that the second criteria heavily restricts distribution, as development builds will ONLY run on machines which were registered with your developer account at the point the signing profile was generated. This is largely invisible when using automatic signing (Xcode will just generate a new profile), but can be easy to overlook with manual signing. At WWDC2022 Apple stated that In MacOS... In fact, all DriverKit family entitlements are now available to use for development. On these very forums, Eskimo himself also sugges

Hi, We need some more diagnostics to be able to help you resolve the issue. Could you please file a feedback request for this and post the feedback number here? You can file Xcode Cloud specific feedback using these steps. Thanks

Quinn is helping this, which is great. I am just curious if the com.apple.developer.icloud- is really com.apple.developer.icloud-container-identifiers. I am guessing that the provisioning profile on your machine, either your notebook or Mac Mini, is not up to date, which leads to the different behaviors. Maybe you can try the following: Be sure your developer account is correctly set up in Xcode Settings > Apple Accounts, and your Mac has the access Apple's developer portal. Uncheck the Automatically manage signing box, and check it back. This tells Xcode to refresh the provisioning profile. If that doesn't help, try to remove the iCloud capability – You are not using any iCloud feature, and so don't really need the capability just yet. If you do need the iCloud capability, check one of the services, and pick an iCloud container if the service you checked is iCloud Documents or CloudKit. This is how folks use the capability. If everything goes well, the .entitlements file in your project

Just to add that the steps to bring back a hidden container are detailed in this post, and that you can add a new container from Xcode as well, as detailed in Enabling CloudKit in Your App. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thanks for taking the time to share your question here. After reading your question, I’m finding myself with more questions than answers right now. Could you tell me what database you’re using (SwiftData)? Also, please specify the programming languages, frameworks, or tools you’re working with. The more details you can share, including code snippets and the versions of the tools you’re using (like Xcode, macOS, iOS, etc.), the better. Lastly, could you let me know which platform you’re aiming for? I'm sure someone in the community will be able to help once you have a chance to update your post. Albert Pascual
  Worldwide Developer Relations.

Same issue, add hoc build compiled with Xcode 26 cannot be run on iOS 12. No crash report only logs. Launch screen is shown for a second and in a moment app is closed