Hi there, Hope you are all well. I would like to know on how I am able to develop/build for both current software, like iOS 26 and iOS 27 at the same time. If it is possible, please let me know how. This is also my first WWDC as a developer, so I may have many questions. Sorry in advance lol. Thanks, Jason

Since updating to MacOS 26.5.1, about 50% of Simulator launches from Xcode 26.3 produce this error: Mach error -308- (pic/mig server died) which is some trouble but I can get past it sometimes. I considered updating to Xcode 26.5 for a possible fix BUT there is a SERIOUS Swift 6.3.2 compiler bug that can violate MainActor isolation and the app I am close to finishing uses MainActor extensively. Also according to Dev Community, there's "also an active bug where SKTestSession cannot use the selected StoreKit configuration during unit tests, causing test actions to fail — relevant if you work on subscription-based apps." Frankly, IMO, Xcode 26.5 seems like a poor point upgrade that needs patching and soon. Is there any news when Apple might patch Xcode to fix both these issues (both reported using Feedback Assist that shows No Similar Reports).

I'm using Dynamic Font throughout my entire app yet the audits in Accessibility Inspector will give me a ton of "Dynamic Type font sizes are unsupported: User will not be able to change the font size of this SwiftUI.AccessibilityNode" warnings. This is incorrect because users are able to change the font size. I can even move to the inspector panel and adjust the font and see it all change right within the Accessibility Inspector. I assume this is a bug since I can change the font but I was also wondering if there's some special thing I'm missing that could prevent these warnings from appearing especially when management runs audits to look for deficiencies.

I am interested to be informed what is relation between storage capacity and Xcode usage; because my storage level goes up when I develop apps on Xcode.

With Xcode 26.5, I've switched from using SwiftLint in a "Run Script" phase to using the SwiftLintPlugins package and running it as a build plugin. This works fine on one Mac, in a small project, where the warnings from the build plugin show up in the issue navigator as expected. But on another Mac, in a large project, I can see the SwiftLint build plugin warnings in the build log but they don't appear in the Xcode issue navigator. Is there some Xcode setting that could influence this, or what else can I check?

Has anybody had encountered these build fail issues in xcode: Type ‘Constants’ has no member ‘AdmobinterstitialID’’; type ‘Constants’ has no member ‘admobadstriggerurls’;type ‘Constants’ has no member ‘fbadstriggerurls’, cannot find ‘cancelbutton’ in; cannot find ‘autoInjectVariable in scope; cannot find ‘enableBioAuth’ in scope;cannot find ‘statusBarBackgroundColor’ in scope;cannot find ‘deletecacheonexit’ in scope; cannot find ‘loadingIndicatorColor’ in scope; cannot find ‘status ‘statusBarTextColor’ in scope;cannot find ‘bottombar’ in scope; And they are all tied to AppConfig. swift And if so, how did you resolve it?

M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread "Keychain issues after installing backup on new Mac" which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p codesigning always returns 0 valid identities. Cryptographic Evidence The internal application labels confirm the keys are cryptographically unrelated to their certificates: Key internal application label: 53C26EB056997276B5E938258D00665ACABD1F0F Certificate public key hash: 57cd1af4a9162f26b1a6d750e05a63a2166b75ff These do not match ❌ Confirmed Eliminated As Causes Keychain search list corruption — found and fixed Partition list — set correctly Access control — set to allow all applications Full Disk Access — granted to Xcode Xcode caches and preferences — completely cleared Login keychain — completely reset Orphaned certificates and keys — all removed SIP enabled, system fully up to date Valid P12 Import Also Fails A p12 exported from the working MacBook Air and cryptographically verified as a matched pair also fails on the Mac Mini: security import returns MAC verification failed Keychain Access import returns OSStatus -2 Importing certificate and key separately as PEM files succeeds but they are not recognized as a valid identity pair despite matching application labels A3F3F193B7896DA9055353F59AB450778CB09AE7 Question Is there a known issue with M4 Mac Mini keychain infrastructure where private keys are generated with incorrect internal application labels? Is there a lower level diagnostic or fix beyond what the security command provides? The problem is specific to my Mac Mini M4 and persisted thru more than a year of Mac OS and xCode updates.

For a couple of months now I haven't been able to see new crash reports for my App Store apps in Xcode. I see the list of crash reports in the Organizer, but selecting any of the new ones always shows the same error message: Error Downloading Crash Log Information: An error occurred preventing Xcode from downloading crash log information. "my.email at domain.com" failed with error: There was a failure decoding response: (HTTP 500, 20364 bytes) The data couldn't be read because it isn't in the correct format.. Pushing the Reload button makes the view load for a bit, but then the same error appears again. Since I want to keep fixing crashes in my apps as fast as possible, is Apple aware of the issue and working on a fix? I don't know if this is a Xcode or App Store Connect issue. I would have expected this issue to be fixed with the newest Xcode version 26.5, but it's still happening. I opened FB22589345 on April 23, but got no response so far.

Hey, I am running Xcode 26.5 and I am not able to option + click anymore on a variable or a type that is not native (String, Bool etc works). The developer documentation preview is also broken.

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 suggests Xcode may be waiting on a Source Control authentication or host fingerprint UI flow that never resolves. SSH connectivity itself is functioning correctly: ssh -T git@bitbucket.org and ssh -T git@github.com both authenticate successfully. git ls-remote, git fetch, git pull, and git push all work correctly from Terminal. No Source Control accounts are configured in Xcode Preferences. Authentication relies entirely on SSH keys. Steps to Reproduce Configure an SSH key for Git access (e.g., Bitbucket or GitHub) and confirm it works via Terminal. Clone or open an existing Git repository that uses SSH (git@host:repo.git). Open the project/workspace in Xcode. In Xcode, attempt a Source Control operation such as: Source Control → Pull Source Control → Push Observe that Xcode displays a spinning progress indicator and does not complete the operation. Logs available on this Feedback Assist ID: FB22146913

Hello, everyone! I've discovered a bug similar to libstdc++/115939 in GCC. This bug exists for a while. Did someone face it too? I'd be glad to accept any advise. Thank you in advance!

ENVIRONMENT Device : MacBook Pro 16,1 CPU : 6-Core Intel Core i7, 2.6 GHz RAM : 16 GB DDR4 GPU : AMD Radeon Pro 5300M + Intel UHD 630 macOS : 26.5 (Build: 25F71) Xcode : 26 (also tried Xcode 16 — same issue) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ISSUE SUMMARY Xcode crashes immediately on launch after updating to macOS 26.5. The issue started right after the macOS update — Xcode was working perfectly before. Both Xcode 26 and Xcode 16 are affected. Fresh reinstall does not help. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ERROR — xcodebuild -version output dyld: Library not loaded: @rpath/DVTSystemPrerequisites.framework/ Versions/A/DVTSystemPrerequisites Reason: code signature in DVTSystemPrerequisites.framework not valid for use in process — mapping process is a platform binary, but mapped file is not. zsh: abort xcodebuild -version ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ CRASH REPORT DETAILS Incident ID : 370D1162-4CA5-4FFE-9193-45EBD350BF85 Exception : EXC_BAD_ACCESS (SIGKILL — Code Signature Invalid) Termination : CODESIGNING, Code 2, Invalid Page Crash Date : 2026-05-14 Failing Frameworks: DVTSystemPrerequisites.framework MobileDevice.framework (/Library/Apple/System/Library/ PrivateFrameworks/MobileDevice.framework) Crashed Thread 7 Stack: dyld3::MachOFile::trieWalk dyld4::Loader::hasExportedSymbol dyld4::JustInTimeLoader::applyFixups _CFBundleLoadExecutableAndReturnError -[NSBundle loadAndReturnError:] __watchForSims_block_invoke -[OSActivityStream setDeviceDelegate:] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT I HAVE ALREADY TRIED sudo xattr -cr /Applications/Xcode.app sudo codesign --force --deep --sign - /Applications/Xcode.app sudo codesign --force --deep --preserve-metadata=identifier,entitlements --sign - /Applications/Xcode.app Re-signed DVTSystemPrerequisites.framework individually Deleted DerivedData, Xcode caches, preferences Fresh reinstall of Xcode (multiple times) Tried installing Xcode 16 — same crash Raised Apple Support Ticket: 102889658162 — no resolution received Nothing has worked. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ROOT CAUSE ANALYSIS macOS 26.5 introduced stricter platform binary validation in dyld. On Intel Mac (x86_64), this validation is rejecting Xcode's own frameworks at runtime — even after re-signing. This does not appear to be a user-fixable issue. This seems to be a macOS 26.5 regression specifically affecting Intel Mac users. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ REQUEST Is anyone else experiencing this on Intel Mac? Has anyone found a working workaround? Can Apple Engineering please investigate this as a macOS 26.5 regression for Intel Macs? My entire development workflow is blocked. Any help is greatly appreciated. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Hi, Overview I would like to add a Swift Package to my Xcode project. Problem In Xcode when I select Project > Package Dependencies and Press + button to add a dependency it keeps spinning and doesn't end Points to note: Xcode 26.5 (17F42) macOS 26.5 (25F71) This is a private GitHub repository I am able to clone the Swift Package URL on the command line. Xcode has the GitHub account I am able to push and pull code on that GitHub account using Xcode My failed attempt rm -rf ~/Library/Developer/Xcode/DerivedData rm -rf ~/Library/Caches/org.swift.swiftpm plutil -remove IDESwiftPackageAdditionAssistantRecentlyUsedPackages ~/Library/Preferences/com.apple.dt.Xcode.plist I have removed GitHub account in Xcode and added it again I am confused if I am missing something very obvious, any help on this is much appreciated. Questions Is there any workaround or way to fix this issue? Why does this take such a long time when I have a specific URL, either it needs to add it or return that the package is not found. Why is it searching?

We would like to use Xcode's new agentic coding feature (probably with Claude Agent). I had a look at the privacy statement, and under "Third-Party Agentic Coding Tools" it says the following: Capabilities include but are not limited to code searching, retrieving build logs, building source code, and arbitrary code execution. This is all expected, except for the bit about "arbitrary code execution". What does this mean, exactly? This sounds like a backdoor to my machine, surely that's not it? Does "code" refer to the code in my project, or any code the agent may provide? I know that other agentic coding tools may execute terminal commands, which you have to (or can select to) confirm first. Is that what is meant by arbitrary code execution? How arbitrary are we talking? And can I configure Xcode to always ask my permission first before any code is executed?

I was having some trouble installing app to test on my Apple Watch (Series 9) so I removed it and thought to re-add it. However, after removing it, it no longer shows under my iPhone for me to add it as a possible run destination. I have tried numerous actions: Restart all devices Repair my watch Use hotspot so everything is on the same network Delete and reinstall Xcode None of these actions seem to be working. Does anyone have a way to get my watch to show up?

There are many situations where debug breaking points are not the right tool. What I often need is a log that shows what gets called, with how much frequency, and in which order. There are so many times where I have to add print statements, re compile, re run, see that I didn't include all the print statements I needed, and repeat a couple of times. My proposal (with zero knowledge of technical feasibility), is that much like we have break points, add "print break points" for logging without modifying code. It would be nice too, if I could also, add a "timer break point", where I can tag a function definition, and every time it gets called, it's are timed. Again, no idea if this is possible, but it would be extremely helpful for me, and I'm guessing to many other devs as well. Thoughts?

Hey everyone, this is a difficult topic to pin down on a certain component but I don't want to assign blame anyway. I want it to go away. Looks like people started to see this somewhere at Xcode 15 but it keeps happening. Xcode 26.5 as of this writing. For Apple people reading this, I posted a bug/feedback FB20206100 including a ready-to-compile (or rather fail-to-compile) example project. The gist is: If you open a Package.swift file with Xcode and that package contain a sub-package, Xcode will insert -suppress-warnings into the build of said sub-package. This means if you add "swiftSettings: [.unsafeFlags(["-warnings-as-errors"])]" into that sub-packages Package.swift file, it wont compile. Why? Because: error: Conflicting options '-warnings-as-errors' and '-suppress-warnings' When you look into the fairly recently accepted swift evolution propsal 0443 they basically say "That's fine. Nothing to see here." or as the proposal put it: Interaction with -suppress-warnings This proposal deliberately excludes -suppress-warnings and its group-based counterpart from the new unified model. We retain the behavior of the existing -suppress-warnings flag but forbid its usage with the new options. The following rules will be applied: It is forbidden to combine -suppress-warnings with -Wwarning or -Werror. The compiler will produce an error if these options are present in the command line together. It is allowed to be combined with -no-warnings-as-errors. The current compiler behavior permits the usage of -no-warnings-as-errors or -warnings-as-errors -no-warnings-as-errors with -suppress-warnings. We will maintain this behavior. I don't care who is right or wrong here but the bottom line is that if you use sub-packages you are effectively being errored out of using "-warnings-as-errors" for (IMHO) no good reason. Could Please someone look at this and say "Yeah, that doesn't look right, let's fix this". Please Thank You Roddi P.S.: Yes, I know there have been posts before that are lamenting this. But I thought, Let's try a fresh start here.

Hello Apple Developer Community, I’ve got a problem with the Xcode Build feature. Because when I would like to build / run my app, my iPhone won’t show up. I’ve already enabled Developer Mode and have set it up in Xcode and did the setup again. I don’t know what I can do next. Are there any possible solutions to this? Thanks for the help 😁. additional Information: Xcode Version: 26.5 Mac: MacBook Air M3 · macOS 26.5 iPhone: iPhone 16 · iOS 26.5

Hullo, I wanted to turn a class in a struct and move intelligence in a protocol extension, but when I try to call inits in the extension I get 'self' used before 'self.init' call or assignment to 'self' How do I call self.init or assign to self before updating the values? Of course init does no accept mutating.

Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified) On Intel Macs, Xcode 26.5 (build 17F42) downloads the darwin-arm64 build of the Claude Agent rather than the darwin-x64 build that the vendor publishes at the same version. The arm64 binary fails to exec on Intel with NSPOSIXErrorDomain Code=86 ("Bad CPU type in executable") and Xcode's Intelligence subsystem then surfaces this in the UI as a code-signing / sandboxing failure. Replacing the downloaded binary with the parallel darwin-x64 build, and updating the agent's Info.plist checksum and URL to match, results in a fully functional Claude Agent in Xcode 26.5 on the same Intel Mac. This was verified end to end on the affected hardware. The agent downloader in Xcode should select the URL matching the host CPU architecture (e.g. by inspecting the result of uname -m or the equivalent in Foundation). This appears to be an isolated fix to whichever component constructs the agent's download URL in Xcode's Intelligence subsystem. Secondary suggestion: the user-facing error message "the code signing identity for the agent did not match expectations, or the agent violated sandboxing rules" should be revised when the underlying cause is an exec failure (EBADARCH or otherwise). The current wording is misleading and has produced considerable misdirected investigation in the developer community. USER-SIDE WORKAROUND (VERIFIED) The following restores Claude Agent functionality on this Intel Mac running Xcode 26.5. It may need re-applying after Xcode updates the agent, since the buggy download logic will run again. Quit Xcode. Download the parallel darwin-x64 binary from the vendor's release bucket (the same URL as in the Info.plist, with "darwin-arm64" replaced by "darwin-x64"). Make the destination writable, copy in the new binary, restore read-only mode. Recompute SHA-512 and update Info.plist's checksum and url fields with plutil. Relaunch Xcode. Workaround for Intel Mac users (verified) This restores a working Claude Agent in Xcode 26.5 on Intel until Xcode'sdownloader is fixed. Quit Xcode fully first. 1. Quit Xcode osascript -e 'tell application "Xcode" to quit' sleep 3 2. Download the correct-arch binary directly from Anthropic's release bucket curl -fL -o /tmp/claude-x64\ttps://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude chmod +x /tmp/claude-x64 3. Verify it's the right arch and properly signed file /tmp/claude-x64 # → Mach-O 64-bit executable x86_64 codesign --verify --verbose /tmp/claude-x64 4. Replace the arm64 binary Xcode downloaded (destination is read-only by default) AGENT_DIR=~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/17F42/claude chmod u+w "$AGENT_DIR/claude" cp -p /tmp/claude-x64 "$AGENT_DIR/claude" chmod a-w "$AGENT_DIR/claude" 5. Update Info.plist so its checksum and URL match the swapped binary NEW_CHECKSUM=$(shasum -a 512 "$AGENT_DIR/claude" | awk '{print $1}') plutil -replace checksum -string "$NEW_CHECKSUM" "$AGENT_DIR/Info.plist" plutil -replace url -string "https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude" "$AGENT_DIR/Info.plist" 6. Relaunch Xcode; the Claude Agent now works on Intel. Caveats Adjust 17F42 and 2.1.118 to whatever your Xcode build and agent version actually are. Check with ls ~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/ and the version key in the Info.plist. The workaround may not survive an Xcode update. If Xcode refreshes the agent (new Claude Code version, new Xcode point release), the buggy download logic will run again and overwrite the x86_64 binary. The same procedure restores working state. Worth saving the commands above as a small shell script so you don't have to re-derive them next time. ENVIRONMENT Hardware: MacBook Pro 2019, Intel Core i9 (x86_64) macOS: 26.5 Xcode: 26.5 (build 17F42) Agent: Claude Code 2.1.118 Account: Claude Pro (claude.ai OAuth) I have tried unsuccessfully to request via 'Apple Feedback Assistant' that the above problem be looked into. This was their response: "Thank you for your feedback, it is noted. Engineering has determined that there are currently no plans to address this issue. This feature relies on the dedicated Neural Engine found on Macs with Apple silicon (M1 or newer) to provide the necessary performance and capabilities. As a result, systems that do not include this hardware are not supported for this specific workflow. You can close this feedback by selecting "Close Feedback" via the Actions button found above. This Feedback will no longer be monitored, and incoming messages will not be reviewed. " Clearly no one from the senior engineering team has looked at this or given it any consideration and they are not interested in making a trivial fix within Xcode so that it selects the correct Claude binary for download. It is frustrating that Apple's response cites the requirement for a 'neural engine found in M-series Macs' , when this is very clear to any developer that Claude does not make use of this feature and it self-evidently works on x86 hardware without it . If anyone has any ideas how to get a response from a helpful senior Xcode developer, I would be most interested. I can understand Apple are reluctant to put any effort into old hardware, however they still provide an up to date Xcode for the x86 platform and I don't think it is asking too much to fix a simple bug which would make life easier.