Hi everyone, I’m unable to enable Xcode Cloud for any app on my account. At the final step of the Xcode workflow setup (“Confirm App on App Store Connect”), pressing Complete always returns: “ could not be added to Xcode Cloud. Authentication credentials are invalid.” This affects both existing apps and completely new test apps with fresh bundle IDs. What I’ve verified • I am Account Holder and Admin. • All agreements are accepted. • App creation, bundle ID registration, and certificate management work normally. • I’ve removed/re-added my Apple ID in Xcode and cleared all Xcode-* tokens from Keychain. • Test apps in clean Git repos reproduce the same error. Support I have already opened Case ID 102769512657 with Apple Developer Support, but I’m posting here in case others have seen this issue or know of additional steps to confirm the provisioning state.

Hi everyone, After updating my Mac and Xcode to 26, I’m running into a consistent crash whenever I try to launch an app from Xcode. Environment: Mac: Apple Silicon M3 macOS: 26.0 (25A354) Xcode: 26.0.1 (17A400) Issue: When I press Run on any project (including new, empty projects), Xcode immediately crashes. This started only after updating to the latest macOS and Xcode. Crash details: The crash log shows: Application Specific Signatures: ___localError Thread 0 crashed inside -[IDEScheme _executionOperationForSchemeOperationParameters:...] from IDEFoundation/IDEKit. I also noticed background threads calling DVTPortal (developer portal requests) right before the crash. What I’ve tried so far: Cleared DerivedData, ModuleCache.noindex, and Xcode caches. Signed out/in of my Apple ID in Xcode. Recreated project schemes. Verified provisioning profiles. Reinstalled Xcode 26. Unfortunately, the crash still happens. Question: Is this a known issue with Xcode 26 on Apple Silicon (M3)? Has anyone seen a workaround? Any guidance would be greatly appreciated — I can’t currently launch apps in Xcode at all. Thanks!

Trying to submit a build to TF from Xcode 26 via Xcode Cloud (both for iOS and macOS). The operation fails with this message: Missing app icon. Include a large app icon as a 1024 by 1024 pixel PNG for the 'Any Appearance' image well in the asset catalog of apps built for iOS or iPadOS. Without this icon, apps can't be submitted for review. For details, visit: https://aninterestingwebsite.com/documentation/xcode/configuring-your-app-icon. If you’ve added an icon made with Icon Composer, visit https://aninterestingwebsite.com/app-store-connect/release-notes/ for details about known issues. I thought it's because Icon Composer icons may not be supported yet, but then that last sentence is confusing me. Does this mean that TF just won't support Xcode 26 uploads yet, or does it accept them and I need to provide legacy icons for my build?

‌Using Xcode 26, the built package encounters device compatibility issues — while it installs successfully on supported iPhone devices, but it crashes immediately upon launch and cannot run normally.‌‌In previous versions of Xcode, the same "minimum deployment" setting in the project did not cause such compatibility issues.‌ The app built with Xcode 26 shows the following behavior when installed and tested on various devices:‌ iPhone6p iOS12.5.8 fails to run 2.iPhone6 iOS11 fails to run 3.Iphone6 iOS12.5.7 fails to run 4.iPhone7 iOS12.1.3 ok 5.iPhoneX iOS 12.2 ok 6.iphone6s plus iOS10.3.1 ok 7.iphoneXS. iOS 12.1.4 ok 8.iPhone11 iOS 13.6.1 ok 9.iPhone7. iOS 13.7 ok We have tested and found that an iPhone 6s Plus running iOS 10.3.1 can normally run the app. We would like to know whether apps built with Xcode 26 are inherently incompatible with iPhone 6 and older devices. Has Xcode 26’s underlying build environment removed full support for the A8 chip, resulting in binary files containing instructions or memory models that older devices cannot parse? ‌Looking forward to your reply‌.

What is the recommended approach for distributing an XCFramework that uses common third-party dependencies (like Google Maps) when client apps may also use the same dependencies, resulting in duplicate symbol conflicts? I'm developing a closed-source SDK distributed as an XCFramework. My SDK internally uses Google Maps for mapping functionality. However, when clients integrate my XCFramework into their apps that also use Google Maps, we encounter duplicate symbol errors. What I've Tried: Static vs Dynamic Linking: Both approaches result in conflicts Static linking: Google Maps symbols compiled into my binary Dynamic linking: GoogleMaps.framework bundled with my XCFramework Build Configuration: Set "Build Libraries for Distribution" = YES Tried various linking strategies Architecture Changes: Used @implementation_only import Wrapped code with #if canImport(GoogleMaps) However, the dependencies still get linked at build time

An internal error occurs when executing the xcodebuild -list command targeting a Swift Package. This behavior is new in Xcode 16.3 and was not present in the previous version, Xcode 16.2. cd ~/Developer mkdir Playground cd Playground swift package init xcodebuild -list Command line invocation: /Applications/Xcode-16.3.0.app/Contents/Developer/usr/bin/xcodebuild -list Resolve Package Graph ** INTERNAL ERROR: Unable to load workspace '/Users/treastrain/Developer/Playground' ** Uncaught Exception: -[Swift.__SwiftDeferredNSArray intersectsSet:]: unrecognized selector sent to instance 0x600001aab5e0 Stack: 0 __exceptionPreprocess (in CoreFoundation) 1 objc_exception_throw (in libobjc.A.dylib) 2 -[NSObject(NSObject) __retain_OA] (in CoreFoundation) 3 ___forwarding___ (in CoreFoundation) 4 _CF_forwarding_prep_0 (in CoreFoundation) 5 -[DVTCoreDevice(DVTCoreDeviceIDE) deviceSupportsBuildable:buildParameters:error:] (in IDEFoundation) 6 -[DVTCoreDevice(DVTCoreDeviceIDE) supportedArchitecturesForBuildableContext:buildParameters:error:] (in IDEFoundation) 7 _IDERunDestinationsForBuildableUsingDeviceWithBuildParameters (in IDEFoundation) 8 -[IDERunDestinationManager runDestinationsForScheme:schemeCommands:executionEnvironment:eligibleOnly:genericOnly:architectureVisibility:] (in IDEFoundation) 9 IDESchemeDetermineAvailableRunDestinations (in IDEFoundation) 10 -[IDEScheme _actuallyInvalidateAvailableRunDestinations] (in IDEFoundation) 11 addSchemeAndMakeActiveIfNecessary #1 (result:error:) in IDESwiftPackage.generateScheme(with:buildable:additionalBuildables:unsetRunnable:makeActive:orderHint:) (in IDESwiftPackageCore) 12 IDESwiftPackage.generateScheme(with:buildable:additionalBuildables:unsetRunnable:makeActive:orderHint:) (in IDESwiftPackageCore) 13 IDESwiftPackage.generateSchemes(_:isRootPackage:) (in IDESwiftPackageCore) 14 IDESwiftPackage.update(from:graphHasErrors:delegate:) (in IDESwiftPackageCore) 15 specialized IDESPMWorkspaceDelegate.rootPackagesDidUpdate(packages:graphHasErrors:modelGraphSynchronizerToken:) (in IDESwiftPackageCore) 16 closure #1 in IDESPMWorkspaceDelegate.packageGraphDidFinishAction(_:duration:result:) (in IDESwiftPackageCore) 17 partial apply for closure #1 in IDESPMWorkspaceDelegate.disableWorkspaceContentSynchronization(during:) (in IDESwiftPackageCore) 18 <deduplicated_symbol> (in DVTFoundation) 19 <deduplicated_symbol> (in DVTFoundation) 20 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation) 21 __58-[DVTModelObjectGraph performBlockCoalescingModelChanges:]_block_invoke (in DVTFoundation) 22 -[DVTModelGraphTransactionScope performTransaction:] (in DVTFoundation) 23 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation) 24 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation) 25 IDESPMWorkspaceDelegate.disableWorkspaceContentSynchronization(during:) (in IDESwiftPackageCore) 26 IDESPMWorkspaceDelegate.packageGraphDidFinishAction(_:duration:result:) (in IDESwiftPackageCore) 27 <deduplicated_symbol> (in IDESwiftPackageCore) 28 SPMWorkspace.packageGraphActionFinished(_:) (in SwiftPM) 29 closure #2 in closure #3 in SPMWorkspace.processPackageGraphActionsInBackgroundIfNeeded(canProcessPackageGraphActions:) (in SwiftPM) 30 <deduplicated_symbol> (in SwiftPM) 31 <deduplicated_symbol> (in SwiftPM) 32 <deduplicated_symbol> (in SwiftPM) 33 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) (in libswift_Concurrency.dylib) zsh: abort xcodebuild -list Environments: % xcodebuild -version Xcode 16.3 Build version 16E140 % swift --version swift-driver version: 1.120.5 Apple Swift version 6.1 (swiftlang-6.1.0.110.21 clang-1700.0.13.3) Target: arm64-apple-macosx15.0

Dear Apple,I'm an iOS developer and provided feedback in the good old online bug tracker for many years.Decent conversations with Apple egnineers often resulted in bug fixes or updated documentation.The fact that my contributions helped to improve the products was rewarding.So I kept adding reports in the new Feedback Assistant app in macOS Catalina.But ever since (September 2019) I never ever got any response on any ticket.1 month ago I even added a report if Apple even read my reports. Again, no response ever since.So my question on this forum: Is Apple actually reading reports in the new Feedback Assistant?This can either be answered by Apple, or by other Developers that hopefully did response feedback from Apple. Or did not.Best regards,Martijn

I am using SwiftData for my model. Until Xcode 15 beta 4 I did not have issues. Since beta 5 I am receiving the following red warning multiple times: 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release This seems to be a CoreData warning. However, I am not using CoreData directly. I have no way to change the config of CoreData as used by SwiftData. My model just uses UUID, Int, String, Double, some of them as optionals or Arrays. I only use one attribute (.unique).

Hi everyone, (you can answer in french) I’m french-rookie in xcode, and I have a problem: I’m trying to choice my custom font to add it in my Main.storyboard button, but it not works. I have my « Font provided by application » line in my Info.plist, with the name of my font in [0] (See images below) When I’m on storyboard button, I chose « custom » in font selector, then display font list but my custom font doesn’t appear. I already tried to install the font in my mac, but still stucked, nothing change 😭 Could you help me please? Thanks a lot (I specify that I scrupulously followed the way of doing explained on the Apple official page: Adding a Custom Font to Your App )

I downloaded the latest version of Xcode 26 (beta). I'm running Max OS 15.5. How can I use Claude 4 Opus? I can't wait to try this out. Thanks in advance!

Hi! In neither Xcode 16.2 beta 3 nor Xcode 16.2 I am able to get App Shortcuts Preview to recognise my Shortcuts. In either supported language I always get "No Matching Intent" as the result. Flexible matching is enabled, minimum deployment target is iOS 18. The Shortcut phrases do work in the simulator and on device. Is this a known issue or am I missing something?

I am building a bundle target for macOS 12 and later using Xcode. The bundle is not a standalone app, but a plug-in that is loaded by a host app. The code is written in Swift and uses the new Span API which is available in the OS-provided standard library in macOS 26 and backdeploys to macOS 10.14.4+. Xcode should instruct the linker to include libswiftCompatibilitySpan.dylib in the compiled bundle to provide this backdeployment, but that does not happen. SwiftPM does this additional linking by adding an rpath. When trying to load the bundle using the NSBundle.loadAndReturnError() API, I get the following error on macOS 15 (and no error on macOS 26): Error Domain=NSCocoaErrorDomain Code=3588 "dlopen(.../MyBundle.someBundle/Contents/MacOS/MyBundle, 0x0109): Library not loaded: @rpath/libswiftCompatibilitySpan.dylib Referenced from: <CE92806C-94B7-367E-895D-EF6DF66C7FC2> .../MyBundle.someBundle/Contents/MacOS/MyBundle Reason: tried: '/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file, not in dyld cache), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file), '/private/Frameworks/libswiftCompatibilitySpan.dylib' (no such file), '.../MyBundle.someBundle/Contents/MacOS/../Frameworks/libswiftCompatibilitySpan.dylib' (no such file), '/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file, not in dyld cache), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file), '/private/Frameworks/libswiftCompatibilitySpan.dylib' (no such file), '.../MyBundle.someBundle/Contents/MacOS/../Frameworks/libswiftCompatibilitySpan.dylib' (no such file)" UserInfo={NSLocalizedFailureReason=The bundle couldn’t be loaded., NSLocalizedRecoverySuggestion=Try reinstalling the bundle., NSFilePath=.../MyBundle.someBundle/Contents/MacOS/MyBundle, NSDebugDescription=dlopen(.../MyBundle.someBundle/Contents/MacOS/MyBundle, 0x0109): Library not loaded: @rpath/libswiftCompatibilitySpan.dylib Referenced from: <CE92806C-94B7-367E-895D-EF6DF66C7FC2> .../MyBundle.someBundle/Contents/MacOS/MyBundle Reason: tried: '/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file, not in dyld cache), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file), '/private/Frameworks/libswiftCompatibilitySpan.dylib' (no such file), '.../MyBundle.someBundle/Contents/MacOS/../Frameworks/libswiftCompatibilitySpan.dylib' (no such file), '/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file, not in dyld cache), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file), '/private/Frameworks/libswiftCompatibilitySpan.dylib' (no such file), '.../MyBundle.someBundle/Contents/MacOS/../Frameworks/libswiftCompatibilitySpan.dylib' (no such file), NSBundlePath=.../MyBundle.someBundle, NSLocalizedDescription=The bundle “MyBundle” couldn’t be loaded.} My setup: Xcode 26.2 macOS 26.2 (25C57) SDK (Built-in)

Hello! When launching/debugging on my iPad and iPhone I keep getting the following error: “Previous preparation error: Failed to find a DDI … Run ‘devicectl list preferredDDI’ …” I believe this was caused by a previously interrupted Xcode update around June due to low disk space, which may have left DeviceSupport/DDI/CoreDevice files incomplete. Even after finishing the update later, the error persists. I now use a new Mac with 4 TB of storage, but the issue still occurs. Since then I have unfortunately been blocked from testing or presenting my app on devices. It seems that only a new, fully completed Xcode update might resolve the problem. Tried so far: – Cleared caches (CoreDevice/Devices) – Reset trust on device and re-paired – Checked devicectl list preferredDDI I would really appreciate guidance, as at the moment I cannot present my app due to this blocking issue. Thank you very much for your support!

At the Platform State of the Union, Apple demoed clicking a ✨ button in the Xcode toolbar to use Apple Intelligence in Xcode. I don't see that button in Xcode Version 26.0 beta (17A5241e). Am I missing it? It's supposed to be in the upper-left corner, right? Do I need to turn it on or something? I'm on macOS 15.5 Sequoia, on a 16-inch, 2021 MacBook Pro

Hi there, We’re encountering this error in all of our builds when using the latest Xcode and macOS: The Metal Toolchain was not installed and could not compile the Metal source files. Download the Metal Toolchain from Xcode > Settings > Components and try again. In short, all builds are failing. I’ve tried fixing this by installing Metal and applying other solutions, but none of them worked reliably. Is there a way to ensure that the Metal Toolchain is installed on the CI machine?

I am preparing for Swift Student Challenge, but it seems like the iPad Playground app still not support the latest SDK. I can't use frameworks like FoundationModel, etc., directly in playground app My playground for this year would require iPad environment since it uses PencilKit, ARKit, etc., and I also want to use the latest tech + the liquid glass UI Right now, I develop the project as a normal Xcode project, and I am wondering how do I post it? As Xcode playground, it must run on macOS As Swift Playground project, the iPad version of Playground does not support latest APIs and it can't compile

Hi, our builds with a Test action in Xcode Cloud are failing because of an internal Xcode Cloud crash. We see the "red cloud with an X" icon, that indicates that it's an Xcode Cloud issue, and the message says "The Test - iOS action could not complete due to an error. The error may not occur on rebuild." but this has been happening for a while now, and for repeated builds. In the artifacts there is a crash log apparently related to the "ibtoold" process, has anybody had this issue before? Thanks

Xcode Cloud seems to be queueing up builds but not processing them. Currently the earliest queued build on my end is about 3 hours ago. System status pages don't show any issues. I just want to check if this is something other people are seeing or just something going weird on our account.

Hi, We are trying to integrate Metric Kit into our MacOS Application. Our application is a background process. We are interested in getting CPU and Memory metrics for our process. MXMetricPayload is the one we are looking at. We tried to integrate metric Kit and left the background app for 24 hours, we did not get any callback. So, does metric kit work for background app in MacOS? Also does it for Network Extension?

When I try to get a new API Key I get the following error. "API Keys cannot be created due to an invalid Program License Agreement. Please update this agreement and try your request again." I have been to the agreement section, and it says: "Issued October 8, 2025. Accepted November 19, 2025." Any idea why I still get this error?? Not sure if that makes a difference. I had a paid account, but I didn't renew it because I don't need it anymore, and I was told that I can still use this account for free for app testing.