Search results for

“Xcode”

93,898 results found

Post

Replies

Boosts

Views

Activity

Is it a bug in UIActivityViewController to Airdrop ?
Context: Xcode 26.3, iOS 18.7.6 on iPhone Xs In this iOS app, I call UIActivityViewController to let user Airdrop files from the app. When trying to send a URL whose file name contains some characters like accentuated (-, é, '), the transfer fails. Removing those characters makes it work without problem. The same app running on Mac (in iPad mode) works with both cases. I also noticed that even when airdrop fails, there is no error reported by activityVC.completionWithItemsHandler = { activity, success, items, error in } Are those known issues ?
Topic: UI Frameworks SubTopic: UIKit Tags:
4
0
262
2w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
Thank you for your replies. Unfortunately, this didn't help either. I developed an app with SwiftDate in a GroupContainer. The data model is stable, and all relationships are optional. The next step should be to switch to an iCloudContainer. Both computers are on the same network and have internet access and access to the developer account. I disabled and re-enabled automatic signing. No change. A comparison of the project.pbxproj files showed two new lines in the non-functional project: 913a913 CODE_SIGN_IDENTITY = Apple Development; 948a949 PROVISIONING_PROFILE_SPECIFIER = ; I manually deleted these two lines and restarted Xcode. There was no change in behavior; the same error occurred. I also manually downloaded the profile from the developer website and tried to sign it manually. But this deployment profile has the same error again: Entitlements: 8 included, 1 Missing What surprises me is that the working version on the MacBook lists 12 entitlements. The entitlements are identical on both systems
2w
Xcode 26.3 incompatible with FireBase and WeTest?
Popular automated testing systems like FireBase [1] and WeTest [2] expect the uploaded test to include the Debug-iphoneos directory generated by Xcode. However, in all of our builds on Xcode 26.3, this folder is created but remains empty. There are some other folders with the same name in subdirectories, but these only contain intermediate build files. Now we're looking for configuration or settings in Xcode to restore the original behavior, where the top-level Debug-iphoneos directory gets populated with a complete image of the test target, include the binary and resource files. Any suggestions would be much appreciated! [1] https://firebase.google.com/docs/test-lab/ios/run-xctest [2] https://www.wetest.net/documents/detail/automation/d8yaA7yz
0
0
36
2w
Swift Data Recovery
Hi Writing an app in Swift on Xcode for my iPhone, all software is the latest version. If after making a minor change and re-building all the application data has disappeared, is there a way to see if it is still in the .modelContainer and just not showing up?
2
0
643
2w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
[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
2w
Reply to Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
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.
2w
Reply to App group broken on Sequoia
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!
Topic: Code Signing SubTopic: Entitlements Tags:
2w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
@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
2w
Reply to Crown Sequencer warning on Scroll
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.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2w
Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
When building a SwiftUI project in Xcode 26.3, Swift compilation fails in the Release configuration with Optimization Level set to -O, when the iOS deployment target is lower than iOS 26 (e.g. iOS 16, 17, or 18). The failure occurs when using a generic class conforming to ObservableObject that contains a @Published property. The same code: Compiles successfully in Xcode 16.3 (Release, -O) with iOS 16/17/18 Compiles successfully in Xcode 26.x when the deployment target is set to iOS 26 Compiles successfully in Xcode 26.x Debug configuration (-Onone) Compiles successfully in Xcode 26.x Release when optimization is disabled (-Onone) However, in Xcode 26.3, the build consistently fails in Release (-O) when targeting iOS 16, 17, or 18. This appears to be a Swift compiler optimization issue related to generics, ObservableObject, @Published, and back-deployment to iOS versions prior to iOS 26. STEPS TO REPRODUCE Create a new Sw
3
0
150
2w
XCode 26 - xcodebuild command hangs on XCFail
On XCode 26.x, calling XCFail with continueAfterFailure set to false causes xcodebuild command to hang indefinitely if the XCUIApplication object is stored outside the test method. Create a new template iOS App project with UI tests Add XCFail(...) to a UI test test-case Set the XCUIApplication in self.app (avoiding this fixes the hang) Run tests with xcodebuild test The terminal hangs forever Reproduction example import XCTest final class TestAppUITests: XCTestCase { var app: XCUIApplication? = nil override func setUpWithError() throws { continueAfterFailure = false } override func tearDownWithError() throws { app?.terminate() } @MainActor func testExample() throws { let app = XCUIApplication() self.app = app // <- HERE this causes the problem app.launch() XCTFail() } } Reproduction environment macOS Sequoia 15.7.3 Tested XCode 26.3 and XCode 26.2 have the hang Tested XCode 16.4 does work as expected XCode 16.4 The issue does not happen on XCode 16.4,
3
0
130
3w
Reply to Xcode help
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.
3w
Reply to DriverKit entitlement policy clarification for development purposes
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
Topic: Code Signing SubTopic: Entitlements Tags:
3w
Is it a bug in UIActivityViewController to Airdrop ?
Context: Xcode 26.3, iOS 18.7.6 on iPhone Xs In this iOS app, I call UIActivityViewController to let user Airdrop files from the app. When trying to send a URL whose file name contains some characters like accentuated (-, é, '), the transfer fails. Removing those characters makes it work without problem. The same app running on Mac (in iPad mode) works with both cases. I also noticed that even when airdrop fails, there is no error reported by activityVC.completionWithItemsHandler = { activity, success, items, error in } Are those known issues ?
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
4
Boosts
0
Views
262
Activity
2w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
Thank you for your replies. Unfortunately, this didn't help either. I developed an app with SwiftDate in a GroupContainer. The data model is stable, and all relationships are optional. The next step should be to switch to an iCloudContainer. Both computers are on the same network and have internet access and access to the developer account. I disabled and re-enabled automatic signing. No change. A comparison of the project.pbxproj files showed two new lines in the non-functional project: 913a913 CODE_SIGN_IDENTITY = Apple Development; 948a949 PROVISIONING_PROFILE_SPECIFIER = ; I manually deleted these two lines and restarted Xcode. There was no change in behavior; the same error occurred. I also manually downloaded the profile from the developer website and tried to sign it manually. But this deployment profile has the same error again: Entitlements: 8 included, 1 Missing What surprises me is that the working version on the MacBook lists 12 entitlements. The entitlements are identical on both systems
Replies
Boosts
Views
Activity
2w
Xcode 26.3 incompatible with FireBase and WeTest?
Popular automated testing systems like FireBase [1] and WeTest [2] expect the uploaded test to include the Debug-iphoneos directory generated by Xcode. However, in all of our builds on Xcode 26.3, this folder is created but remains empty. There are some other folders with the same name in subdirectories, but these only contain intermediate build files. Now we're looking for configuration or settings in Xcode to restore the original behavior, where the top-level Debug-iphoneos directory gets populated with a complete image of the test target, include the binary and resource files. Any suggestions would be much appreciated! [1] https://firebase.google.com/docs/test-lab/ios/run-xctest [2] https://www.wetest.net/documents/detail/automation/d8yaA7yz
Replies
0
Boosts
0
Views
36
Activity
2w
Swift Data Recovery
Hi Writing an app in Swift on Xcode for my iPhone, all software is the latest version. If after making a minor change and re-building all the application data has disappeared, is there a way to see if it is still in the .modelContainer and just not showing up?
Replies
2
Boosts
0
Views
643
Activity
2w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
[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
Replies
Boosts
Views
Activity
2w
Reply to Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
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.
Replies
Boosts
Views
Activity
2w
Reply to App group broken on Sequoia
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!
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
2w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
@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
Replies
Boosts
Views
Activity
2w
Reply to Crown Sequencer warning on Scroll
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.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
2w
Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
When building a SwiftUI project in Xcode 26.3, Swift compilation fails in the Release configuration with Optimization Level set to -O, when the iOS deployment target is lower than iOS 26 (e.g. iOS 16, 17, or 18). The failure occurs when using a generic class conforming to ObservableObject that contains a @Published property. The same code: Compiles successfully in Xcode 16.3 (Release, -O) with iOS 16/17/18 Compiles successfully in Xcode 26.x when the deployment target is set to iOS 26 Compiles successfully in Xcode 26.x Debug configuration (-Onone) Compiles successfully in Xcode 26.x Release when optimization is disabled (-Onone) However, in Xcode 26.3, the build consistently fails in Release (-O) when targeting iOS 16, 17, or 18. This appears to be a Swift compiler optimization issue related to generics, ObservableObject, @Published, and back-deployment to iOS versions prior to iOS 26. STEPS TO REPRODUCE Create a new Sw
Replies
3
Boosts
0
Views
150
Activity
2w
XCode 26 - xcodebuild command hangs on XCFail
On XCode 26.x, calling XCFail with continueAfterFailure set to false causes xcodebuild command to hang indefinitely if the XCUIApplication object is stored outside the test method. Create a new template iOS App project with UI tests Add XCFail(...) to a UI test test-case Set the XCUIApplication in self.app (avoiding this fixes the hang) Run tests with xcodebuild test The terminal hangs forever Reproduction example import XCTest final class TestAppUITests: XCTestCase { var app: XCUIApplication? = nil override func setUpWithError() throws { continueAfterFailure = false } override func tearDownWithError() throws { app?.terminate() } @MainActor func testExample() throws { let app = XCUIApplication() self.app = app // <- HERE this causes the problem app.launch() XCTFail() } } Reproduction environment macOS Sequoia 15.7.3 Tested XCode 26.3 and XCode 26.2 have the hang Tested XCode 16.4 does work as expected XCode 16.4 The issue does not happen on XCode 16.4,
Replies
3
Boosts
0
Views
130
Activity
3w
Reply to Is it possible to download or copy the iOS SDK for Xcode 26.1 using command-line tools? If so, how?
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
Replies
Boosts
Views
Activity
3w
Reply to Xcode help
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.
Replies
Boosts
Views
Activity
3w
Reply to DriverKit entitlement policy clarification for development purposes
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
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
3w
Reply to Xcode Cloud: CI.SCM.Error.RepositoryNotFound with GitHub Organization (401 Unauthorized)
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
Replies
Boosts
Views
Activity
3w