Overview Tapping on ShareLink crashes the app when ShareLink is added in the toolbar with the placement of secondaryAction Feedback FB21337385 Note: Apple engineers please priorities this is a blocker and affects production apps and prevents us from going live. Environment Xcode: 26.2 (17C52) iOS: 26.2 iPadOS: 26.2 Reproduce Able to reproduce 100% both on Simulator and Device Isolation of the crash The crash happens only when the ShareLink is used with the placement .secondaryAction The crash doesn't 'happen when the ShareLink is used with the placement .primaryAction Code import SwiftUI struct ContentView: View { var body: some View { NavigationStack { Text(Hello, world!) .toolbar { ToolbarItem(placement: .primaryAction) { Button(Dummy) { print(dummy) } } // Tapping on share button will cause it to crash // Crash only happens when the ShareLink is used with placement .secondaryAction // It doesn't crash when placement is primaryAction ToolbarItem(placement: .secondaryAction) { ShareLink(item: Some s
Search results for
xcode github
93,999 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
This is happening to me on a fresh install of Xcode 26.2 > 13 mini (iOS 26.2). No betas here, all shipping versions.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Just checked new Xcode 26.2 with iOS 26.2 and the debug builds startup time indeed improved significantly. We still have ~7 seconds of initial sluggishness (difference between debug executable on/off), but it's way better than it was before! 👍
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
We’re facing an issue with Xcode 26.1 where code coverage is not being generated. All our test cases run and pass successfully, but the .xccovreport / .xccovarchive files are never produced. Code coverage is enabled in the scheme, and this setup used to work correctly in earlier Xcode versions. We are trying to determine whether this is a configuration issue on our end or a possible Xcode 26.1 bug. Is anyone else experiencing the same problem with code coverage in Xcode 26.1? Any insights or workarounds would be appreciated.
I investigated this further and confirmed the issue is due to a toolchain mismatch inside Xcode 26.1. Although test execution successfully generates multiple .profraw files, the coverage merge step fails. Running the merge manually using the Xcode-bundled tool results in the following error: raw profile version mismatch: Profile uses raw profile format version = 8 expected version = 10 error: no profile can be merged. The same project and test configuration generates coverage correctly on earlier Xcode versions, which strongly suggests a issue in Xcode 26.1’s coverage toolchain.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hello, I have an app on the App Store built around WeatherKit and it was working fine, up until this morning when I started seeing errors when using the app. When debugging using Xcode I see the familiar error Failed to generate jwt token for: com.apple.weatherkit.authservice with error: Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 (null) which, according to what I've read on the forums looks like an authentication error. Attaching a network debugger to the Simulator, I saw this error: This I have tried: Verify that WeatherKit is enabled on both Capabilities and App Services tabs on the Dev Portal. Toggle on/off this value and regenerate Provisioning Profiles Uninstall/reinstall Checking that I have API available calls. Nothing. If I create a new Bundle ID and sign with that, it works correctly. But this is not an option since that will force all my customers to download everything from scratch. I am getting emails from customers demanding money back and I can't figure
Hello. I migrated yesterday two machines from OS15 to OS26 (same Ram; M1Max chip). On the first one, a MBP, everything is allright, and my old Metal projects can compile and run, even with MacOS12 as a destination. On the second computer (MacStudio) I got a compile error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain. I spent hours on many forums and tried all proposed solutions and still get the same error. Any idea? Thanks
Thanks. Couldn't succeed after many tries of downloading and install (errors about permissions to read or execute...). I succeeded following the protocol described here: https://medium.com/@sergey-pekar/how-to-fix-annoying-xcode-26-not-building-swiftui-previews-error-cannot-execute-tool-metal-due-49564e20357c What I dont understand is that on my M1Max MBP, Metal was already OK without any setting, and I could compile my project once XCode 26 was downloaded and installed
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I have been using Xcode Version 26.1.1 on macOS Tahoe Version 26.1. In VIM mode, whenever I quickly tap d twice, to delete the complete line, most of the time Xcode crashes. Is anyone else facing this issue? Should I move to any older version of Xcode or any other solve for this?
The latest version of Xcode available on: https://developer.apple.com/download/applications/ is Xcode 26.2 build 17C52. It was released today, December 12, 2025. However, uploads are failing with error: Validation failed. This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode. I have verified my Xcode is not beta: I think that at least the non-release candidate, latest version of Xcode should be allowed to submit apps.
The link that Albert posted has updated to include this latest entry: December 12, 2025 App Store Connect update You can now upload apps built with Xcode 26.2 using the SDK for iOS 26.2, iPadOS 26.2, macOS 26.2, tvOS 26.2, visionOS 26. 2, and watchOS 26.2 for the App Store, and for internal and external testing through TestFlight. We were able to upload and submit our app. Conclusions: This is probably a rare situation. However, it demonstrates that Xcode RC builds might not reach the point of having their archived app builds accepted for App Store submissions. If anyone from Apple is reading this, our feedback: We respect your processes and accept that it is often in Apple's and the developers' interests to not convey information that is subject to change. That said, when a pattern is established like almost always accepting Xcode RC built submissions, then expectations will become established amongst the developers. If you multiply the time spent and frustration caused across all
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
The tooling for Metal became an optional download with Xcode 26, as only some developers need those capabilities. If you look to Xcode > Settings > Components, and try to download and install it, what happens? The text of the error you shared there is also a command you can run in Terminal to do the same thing. If there are error messages when installing the toolchain from Xcode settings or in Terminal, please include a screenshot or the full error message text. — Ed Ford, DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Thanks for the post. Upon uploading your app to TestFlight and installing it from there, all audio on your app appears to be disabled? Are you utilizing Flutter? Have you reached out to the support channel for Flutter, the third-party resource you are using? I do not believe this issue is related to TestFlight, as other apps have audio. However, if you can reproduce the issue using Xcode by creating a focused sample and uploading it to TestFlight to verify the presence of audio, that would be helpful. A focused Xcode project that builds and demonstrates the issue. Ideally this will be a new Xcode project created specifically to demonstrate this issue, and which includes only the minimal code and API necessary to reproduce the issue. This focuses on the important code paths and may require you to perform additional debugging to extract the relevant code. Please do not include any 3rd-party code or frameworks unless they are absolutely required for this targeted sample project to run.
Topic:
Media Technologies
SubTopic:
Audio
Environment MacOC 26 Xcode Version 26.0 beta 7 (17A5305k) simulator: iPhone 16 pro iOS: iOS 26 Problem NLContextualEmbedding.load() fails with the following error In simulator Failed to load embedding from MIL representation: filesystem error: in create_directories: Permission denied [/var/db/com.apple.naturallanguaged/com.apple.e5rt.e5bundlecache] filesystem error: in create_directories: Permission denied [/var/db/com.apple.naturallanguaged/com.apple.e5rt.e5bundlecache] Failed to load embedding model 'mul_Latn' - '5C45D94E-BAB4-4927-94B6-8B5745C46289' assetRequestFailed(Optional(Error Domain=NLNaturalLanguageErrorDomain Code=7 Embedding model requires compilation UserInfo={NSLocalizedDescription=Embedding model requires compilation})) in #Playground I'm new to this embedding model. Not sure if it's caused by my code or environment. Code snippet import Foundation import NaturalLanguage import Playgrounds #Playground { // Prefer initializing by script for broader coverage; returns NLContextualEmbeddin
Uploads to App Store from Xcode 26.2 build 17C52 are working now! I was also seeing the same error 2 hours ago.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags: