I have a MacMini M2 machine running Sequoia 15.1 OS. On this machine, I am running a Virtual Machine, utilizing the Virtualization.Framework, with the same OS version, 15.1.
Logging into my account in the System Settings is successful. Next, I need to add my account in Xcode 16.1. While the initial login is successful, Xcode immediately displays the following error:
Decoding Error.
There was a failure decoding response: (HTTP 401, 60 bytes) The data couldn’t be read because it isn’t in the correct format.
As a result, I cannot see any account information, teams, etc.
A very similar bug has been reported at this issue - https://developer.apple.com/forums/thread/759877, but there has been no progress or updates there.
Is there any chance to fix this and get it working?
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
ChatGPT in Xcode 26.1 is super slow for me. What used to complete in a batter f seconds is now taking tens of minutes.
Context: M2 Pro MBP, Xcode 26.1, macOS 26.1. CPU stays under 50% while ChatGPT returns. Using the minimal setting. Tried restarting, have verified I have nothing running Electron, no other apps are running.
ChatGPT returns fast for the displayed content but the preview window where it renders code per line takes a few seconds per line.
Hey,
I've updated to both Xcode 26 Beta 4 and MacOS 26 Beta 4. Both run super stable so far.
However, every time I use Xcode Previews for a few minutes, the entire system freezes for a few seconds and then crashes and reboots.
I'm trying to generate a system diagnosis (which it offers me after the reboot), but it seems to be stuck generating.
It's hard to say what exactly causes the crash, unfortunately. But it happened multiple times after starting to use Xcode Previews.
Anyone else has that problem?
I've also filed a feedback for this: FB19013059
Cheers
Dennis
WKWebView based apps crash in today's Xcode 16.4 iOS 18.5 simulator with messages including:
"Library not loaded: /usr/lib/swift/libswiftWebKit.dylib"
and of the form
"/Users/yyy/Library/Developer/Xcode/DerivedData/zzz/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file)"
I'm trying to write performance tests with Xcode 15, but it's not working: even though setting a baseline seems to work (baseline data files are created), Xcode seems to ignore that baseline altogether whenever the test is run. As a result, performance tests never fail, no matter how bad performance gets.
The source editor persistently displays a “No baseline average for Time” message.
Has anyone else encountered this? Figured out how to sidestep the issue?
Of note, the issue is easily reproduced: create a new (macOS in my case) app project with tests, add a dummy performance test; run the test once and save its baseline, and despite this subsequent tests will always succeed, even if you significantly slow the dummy test down.
(I've filed this as FB13330139)
Hi,
I just migrated from Xcode 15 to Xcode 16.3 RC. When I run my app on any simulator, iOS 17 or iOS 18, I seeing strange behavior the second time I launch the app. The app uses a few frameworks, such as Firebase Crashlytics, and the network calls all work fine on the initial launch. however, subsequent launches consistently get the following error:
Task <17ACD3D4-FB31-4091-A797-D573F31909C2>.<2> finished with error [-1001] Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x600000c46910 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <17ACD3D4-FB31-4091-A797-D573F31909C2>.<2>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask <17ACD3D4-FB31-4091-A797-D573F31909C2>.<2>"
), NSLocalizedDescription=The request timed out.,
The only way to run again on that simulator is to Erase All Content and Settings. I did not see this issue in Xcode 16, and my app has been in production for over a year without networking issues.
Pushing to my phone works fine.
Running on MacBook Pro apple silicon - Sequoia 15.3.2
Any help would be greatly appreciated!
Thanks,
Mike
I've recently set up new M4 Mac Minis with macOS Sequoia and Xcode 16. After logging into my Apple account in Xcode, everything works fine initially. However, the next day—or sometimes just a few hours later—my builds fail, and when I check the Accounts tab in Xcode's Settings, my account is missing. I have to re-add and re-authenticate my account, only for the same issue to recur later.
To investigate further, I upgraded an older Mac Mini from macOS Sonoma and Xcode 15.1.0 to macOS Sequoia and Xcode 16.2. Unfortunately, this machine now exhibits the same behavior, suggesting the issue is related to either macOS Sequoia or Xcode 16.
Has there been a change in Xcode or macOS that causes this automatic removal of accounts? Is there a solution or workaround to prevent Xcode from removing my Apple account?
Any insights or suggestions would be greatly appreciated!
Hello, do the String Catalogs (new in Xcode 15) support Swift Packages?
I've tried adding a new Localizable.xcstrings (string catalog) file to my package's resources folder.
Great! I then see this screen:
All good so far.
I then try to go and build my Swift Package... and nothing changes. The string catalog is never populated and I'm left with the same screen as above.
So, do string catalogs not support packages at this time or am I doing something wrong?
I was really hoping String Catalogs would work and save the day since Export Localizations also does not work for Swift packages that don't support macOS. 😔
Hello. In the Xcode 15 we were using this command in the terminal to run our tests on the Rosetta Simulator:
xcodebuild -workspace CoreLibraries.xcworkspace -scheme CoreLibraries -destination 'platform=iOS Simulator,name=iPhone 15,arch=x86_64' test`
In the Xcode 16 the same command doesn't work anymore. It produces the error:
xcodebuild: error: Unable to find a device matching the provided destination specifier:
{ platform:iOS Simulator, arch:x86_64, OS:latest, name:iPhone 16 }
Unsupported device specifier option.
The device “iPhone 16” does not support the following options: arch
Please supply only supported device specifier options.
Running test directly from the Xcode UI using iPhone 16 (Rosetta) still works fine.
Does anyone know how to modify the xcodebuild command to make it work again?
Hello,
we are struggling for hours with the following issue: I have an individual developer account and since yesterday I'm member of developer team with an own organization account.
I have access to an app in the team account as an "App-Manager", also the option "Access to Certificates, Identifiers & Profiles" is activated and I can see that it is activated for my account in AppstoreConnect.
In "Apple Developer" I can also see the team and can switch to. But then I do not see the "Certificates, Identifiers & Profiles" menu entry. Also the team is not showing up in XCode.
What am I missing?
Thanks and regards
Philipp
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode
Signing Certificates
Developer Program
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
Xcode 16.2 runs well, but encountered the problem in Xcode 16.3.
Topic:
Developer Tools & Services
SubTopic:
Xcode
I recently switched to Mac OS 12 and XCode 13. I did some work on my application and rebuilt it. Now there is no Help Book. I didn't change the property lists and everything looks right. When I open the Help Book the application either opens a window with a message that the content is currently unavailable or it opens a Help Book window with no content. When this second thing happens the log window shows "entering AHRegistered help Book" but it doesn't appear. Does anyone have any suggestions?
Hello everyone!
When I run UI Tests on Xcode Cloud, I often encounter unexpected failures. Checking the screen recording, I found that the iOS Simulator could go into a black screen with a white Apple logo and a progress bar for a period after the test starts. This behavior of the Simulator causes my app's UI Tests to fail randomly, which greatly affects the practical use of UI Tests.
I suspect this phenomenon is unrelated to my app and test cases, so I'm asking if anyone else has encountered a similar issue. 🤔
I just submitted a feedback for this (FB9662125) but in the spirit of “share and enjoy”…
The cool new Generate Info.plist File feature in Xcode 13 crashes if you try to put an NSLocationTemporaryUsageDescriptionDictionary in your Info.plist file. Here’s a simple repro scenario:
Create a minimal iOS app (no Core Data, no tests)
Go to target settings → Info tab → Custom iOS Target Properties
Click the (+) button on any row to begin inserting a new row
Select Privacy - Location Temporary Usage Description Dictionary
Click somewhere else or press Return to commit the selection
Xcode crashes immediately
More generally, it seems that Xcode crashes any time it tries to regenerate your Info.plist file if it contains an NSLocationTemporaryUsageDescriptionDictionary, even if (for example) you manually pasted that dictionary into the file earlier. In that case, merely tapping the (+) button in step 3 above is enough to crash it.
I am unable to download the iOS 26.1 Simulator Runtime through Xcode 26.1 on macOS 26.1 (Build 25B78).
Issue Details:
When attempting to download via Xcode Settings → Platforms, the download fails with error code 41 (DVTDownloadableErrorDomain) and error code 60 (MADownloadCannotConnectToHost)
The error message states: "Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({RequestedBuild = 23B80;})"
I receive HTTP 403 Forbidden when accessing mesu.apple.com/assets/
Steps Attempted:
Downloaded via Xcode Settings → Component → iOS 26.1 Simulator
Tried command line: xcodebuild -downloadPlatform iOS
Searched https://developer.apple.com/download/all/ - iOS 26.1 Simulator Runtime not listed
Tested with different networks (home WiFi, VPN, mobile hotspot)
Disabled proxy settings
Flushed DNS cache
All attempts result in the same error.
Important Notes:
Xcode 26.1 shows iOS Simulator SDK 26.1 (Build 23B77) is available
However, Xcode attempts to download Build 23B80, which appears unavailable
I experienced a similar issue previously with Xcode 16.4 requesting iOS 18.4 Simulator Runtime, which was also unavailable for download
Impact:
Without the iOS 26.1 Simulator Runtime, I cannot develop or test iOS applications. macOS 26.1 requires Xcode 26.1, which in turn requires iOS 26.1 runtime, leaving me unable to perform any iOS development work.
Questions:
Is iOS 26.1 Simulator Runtime (Build 23B80) officially released?
Is there a direct download link available?
Should Xcode 26.1 be requesting Build 23B77 instead of 23B80?
Is there any account restriction preventing me from downloading newer simulator runtimes?
System Information:
macOS: 26.1 (Build 25B78)
Xcode: 26.1 (Build 17B55)
Error description:
Download failed.
Domain: DVTDownloadableErrorDomain
Code: 41
User Info: {
DVTErrorCreationDateKey = "2025-11-10 15:38:07 +0000";
}
Download failed.
Domain: DVTDownloadableErrorDomain
Code: 41
Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({
RequestedBuild = 23B80;
})
Domain: DVTDownloadsUtilitiesErrorDomain
Code: -1
Download failed due to not being able to connect to the host. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime)
Domain: com.apple.MobileAssetError.Download
Code: 60
User Info: {
checkNetwork = 1;
}
Topic:
Developer Tools & Services
SubTopic:
Xcode
My MBP M1 Pro gets really hot. iOS 26.1 Simulator in Xcode 26.1 makes ReportCrash process run at 60-160% of CPU shows Activity Monitor.
MacOS 26.1. I've reported this via Feedback Assistant: FB20918609.
Is there a way to quit this process permanently? When I Force Quit this it opens again immediately. Only way to stop it is to quit Simulator. But then again, I need to use the Simulator.
It seems like, by default, the preview pane tries to align to 50% of the editor pane's width.
I prefer to shrink the preview pane to around ~30% of the screen so I have more space for code. This used to work fine—at least until I restarted Xcode. I never understood why the setting wouldn’t persist across sessions, but fine, that was a tradeoff I was willing to live with.
However, with Xcode 16.3, it seems like Xcode forgets the manually adjusted preview pane width as soon as I switch to a different file. This has definitely impacted my productivity, as I now find myself readjusting the pane size dozens of times in a single session.
Am I holding it wrong? Is anyone else experiencing this?
And while we’re at it—why not make this a persistent setting so everyone can tweak the width to their liking?
Opened a FB already (FB20928652) but wanted to check here if anybody has seen similar or has better workarounds.
xcresulttool merge appears to crash immediately after launch in Xcode 26.1 (and in 26.2b1).
It does so regardless of any inputs passed in; the crash appears to be during argument parsing before any other logic is run, so it's not contingent on inputs.
Working example from 26.0.1 (passing in arbitrary strings for a minimum-reproducible-case, so we expect to see an error message) :
% /Applications/Xcode-26.0.1.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c
Error: File or directory doesn't exist at path: b.
Usage: xcresulttool <subcommand>
See 'xcresulttool --help' for more information.
The same example crashes in 26.1:
/Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c
zsh: trace trap /Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge
Again, this does crash in real use cases as well, the arbitrary strings are just for quick reproduction.
The stack trace appears to be during argument parsing (which from a quick look, did indeed change between 26.0.1 and 26.1). On 26.1+, garbage data seemingly gets passed to AbsolutePath.init.
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x00000001002c6748 xcresulttool-26.1`normalize(absolute:)
frame #1: 0x00000001002c6438 xcresulttool-26.1`AbsolutePath.init(_:) + 28
frame #2: 0x000000010005a2c0 xcresulttool-26.1`Merge.run() + 372
frame #3: 0x000000010005b180 xcresulttool-26.1`protocol witness for ParsableCommand.run() in conformance Merge + 12
frame #4: 0x000000010011d3e4 xcresulttool-26.1`dispatch thunk of ReadableStream.close() + 16
frame #5: 0x000000010000148c xcresulttool-26.1`main + 156
frame #6: 0x00000001804d5d54 dyld`start + 7184
The only workaround we've found is to keep using 26.0.1's copy of xcresulttool, though that's obviously not ideal.
I installed a custom font (Font awesome) into my app. I triple checked that I did everything right: the font files are included in the bundle (they appear in the "Copy Bundle Resources" build phase) and the names of the fonts appear in the Info.plist file under "Fonts provided by application".
In Interface builder, I select a Label, set the font to "Custom", then I click the Family list to select the font I want.
Once or twice, I was actually able to see the Font Awesome fonts in this list and select one. However, they no longer appear there when I create new labels in new views. I do not understand why. I've been limping along by copying a label from one of the views where it worked and pasting it into the new view, but this is tiresome.
I know the fonts are installed correctly because I can see them when I run the app.
Why are the fonts not showing up on the font list in interface builder?