Search results for

“xcode github”

95,396 results found

Post

Replies

Boosts

Views

Activity

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:
1w
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
141
1w
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
122
1w
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.
1w
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:
1w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
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
1w
Reply to Data Disappeared
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.
1w
Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This
0
0
102
1w
Xcode 26.3 Claude Agent — 401 Invalid Bearer Token on Intel Mac (FB22141224)
I've been investigating a persistent 401 Invalid Bearer Token error with Claude Agent in Xcode 26.3 on an Intel Core i9 Mac and wanted to share my findings here in case others are affected. ENVIRONMENT Hardware: Intel Core i9 (x86_64) Xcode: 26.3 (17C529) macOS: 26.3 (25D125) THE ISSUE Claude Agent fails with Failed to authenticate. API Error: 401 - Invalid bearer token on every prompt, despite the account showing as Signed In under Settings → Intelligence. The error persists after signing out and back in, and the token is confirmed valid and unexpired in Keychain. WHAT WORKS Claude Code in Terminal works perfectly on the same machine with the same credentials The basic Claude Sonnet 4.5 coding assistant in Xcode works fine Only Claude Agent is affected ROOT CAUSE HYPOTHESIS Xcode appears to be installing an ARM64 Claude binary on Intel Macs silently, with no warning or fallback. This binary likely fails to execute on x86_64 hardware and that failure is being misreported up
0
0
54
1w
Reply to User crash report contains ??? instead of my app's symbols and no binary image base address
Thanks. I wasn't sure what I should use as the load address for the atos command. I used the start address of the __TEXT segment, but I just got the crash address back: % atos -arch x86_64 -o ~/Library/Developer/Xcode/Archives/2026-02-03/MyApp 03.02.2026, 13.48.xcarchive/dSYMs/MyApp.app.dSYM/Contents/Resources/DWARF/MyApp -l 0x10462e000 0x10844eb40 0x10844eb40 Although notice that the range of __TEXT 10462e000-1048c8000 doesn't even contain the crash address 0x10844eb40. Unless I'm doing something wrong, it looks to me like the crash is out of my control and I can't really do anything about it, which like you said is kind of confirmed by the weird crash report.
1w
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
1w
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
141
Activity
1w
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
122
Activity
1w
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
1w
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
1w
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
1w
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
1w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
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
Replies
Boosts
Views
Activity
1w
Reply to Cannot create new CloudKit container after deleting all containers - need help
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.
Replies
Boosts
Views
Activity
1w
Reply to Data Disappeared
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.
Replies
Boosts
Views
Activity
1w
Reply to Ad Hoc .ipa for iOS 12.5.8
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
Topic: Business & Education SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Xcode 26 fails to load SPM packages
Enabling IDEPackageSupportUseBuiltinSCM worked perfectly! Even better than with old Xcode versions.
Replies
Boosts
Views
Activity
1w
Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This
Replies
0
Boosts
0
Views
102
Activity
1w
Xcode 26.3 Claude Agent — 401 Invalid Bearer Token on Intel Mac (FB22141224)
I've been investigating a persistent 401 Invalid Bearer Token error with Claude Agent in Xcode 26.3 on an Intel Core i9 Mac and wanted to share my findings here in case others are affected. ENVIRONMENT Hardware: Intel Core i9 (x86_64) Xcode: 26.3 (17C529) macOS: 26.3 (25D125) THE ISSUE Claude Agent fails with Failed to authenticate. API Error: 401 - Invalid bearer token on every prompt, despite the account showing as Signed In under Settings → Intelligence. The error persists after signing out and back in, and the token is confirmed valid and unexpired in Keychain. WHAT WORKS Claude Code in Terminal works perfectly on the same machine with the same credentials The basic Claude Sonnet 4.5 coding assistant in Xcode works fine Only Claude Agent is affected ROOT CAUSE HYPOTHESIS Xcode appears to be installing an ARM64 Claude binary on Intel Macs silently, with no warning or fallback. This binary likely fails to execute on x86_64 hardware and that failure is being misreported up
Replies
0
Boosts
0
Views
54
Activity
1w
Reply to User crash report contains ??? instead of my app's symbols and no binary image base address
Thanks. I wasn't sure what I should use as the load address for the atos command. I used the start address of the __TEXT segment, but I just got the crash address back: % atos -arch x86_64 -o ~/Library/Developer/Xcode/Archives/2026-02-03/MyApp 03.02.2026, 13.48.xcarchive/dSYMs/MyApp.app.dSYM/Contents/Resources/DWARF/MyApp -l 0x10462e000 0x10844eb40 0x10844eb40 Although notice that the range of __TEXT 10462e000-1048c8000 doesn't even contain the crash address 0x10844eb40. Unless I'm doing something wrong, it looks to me like the crash is out of my control and I can't really do anything about it, which like you said is kind of confirmed by the weird crash report.
Replies
Boosts
Views
Activity
1w