Search results for

Xcode

92,297 results found

Post

Replies

Boosts

Views

Activity

Reply to Xcode Cloud fails while exporting archive
Seeing this as well. I don't see those exact errors in the log. In our case it repeatedly mentions: 2025-12-14T23:42:24.246116551Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246119266Z 2025-12-14T23:42:24.246121303Z error: exportArchive No signing certificate iOS Development found 2025-12-14T23:42:24.246124727Z 2025-12-14T23:42:24.246126906Z error: exportArchive There is a problem with the request entity 2025-12-14T23:42:24.246129486Z 2025-12-14T23:42:24.246131437Z error: exportArchive No signing certificate iOS Development found Which is odd as we use cloud managed signing. I do see a Development certificate created by Xcode cloud. The app id that references is setup for iOS. I don't see an Xcode cloud generated Provisioning profile in the development portal, but I can't recall if they show up there. FB21343022
4d
Xcode Simulator causes Mac audio crackling and distortion
[Submitted as FB20950954] Xcode Simulator causes crackling and distortion in audio playback across all apps (Apple Podcasts, Music, third-party). REPRO STEPS Open any audio app and start playback Note the audio quality Launch Xcode Simulator After a few seconds, note audio quality again Quit Xcode Simulator Audio returns to normal CURRENT Audio has crackling and distortion while Simulator is running. EXPECTED Clean audio playback regardless of whether Simulator is running. SYSTEM INFO macOS 26.1 (25B78) Xcode 26.1 (17B55) Simulator 26.0 (1058)
2
0
142
4d
Reply to DeclaredAgeRange framework new cases and properties cause runtime crash with missing symbol
@DTS Engineer Tested with Xcode 26.2 downloaded from the App Store, against iPhone 17 Pro running 26.1 (23B85) Xcode Version 26.2 (17C52) So this property wasn't tested. I haven't touched PermissionKit yet so I wasn't actively testing this, however my wrapper library code still fails for this property too and causes a runtime crash due to symbol not found. AgeRangeService.ParentalControls.significantAppChangeApprovalRequired 55C0A89C-7970-4C69-B5D3-1E6873C6EF2B-diagnostic.json Here is some offending code, assumes iOS 26 minimum target: extension ParentalControls { public init(activeParentalControls: AgeRangeService.ParentalControls) { var value: Int = 0 if activeParentalControls.contains(.communicationLimits) { value |= ParentalControls.communicationLimits.rawValue } if activeParentalControls.contains(.significantAppChangeApprovalRequired) { value |= ParentalControls.significantAppChangeApprovalRequired.rawValue } self.rawValue = value } }
4d
Reply to SDK for Swift Student Challenge 2026 submissions
👋Hi @DTS Engineer I remember that the form submitted last year needed to be filled in with Xcode or Playground test, and it seems that it was also mentioned: • If you use Xcode, the judges may use Simulator to run. • If you use Playground, it's a real machine. But my work this time will encounter two limitations: It will use the framework/API only available in iOS 26 (so if it is a Playground environment, it may not run) It will also use some content that must be real to run (such as ARKit), which means that Xcode Simulator is not good. So I would like to ask: Does this year's review allow you to compile and connect the iPad to the real machine? Or did I misremember last year's regulations? If the judge's environment is fixed (for example, only Playground or only Simulator), how should I adjust the submission method or implement the scheme? Looking forward to your reply, thank you. ~ Jiaxu Li
5d
Importing files to Files.app in iOS 26 Simulator
In previous versions of the simulator, it was possible to import files into the Files app by dragging them from the Finder into the Simulator. It appears that in the iOS 26 Simulator, this opens the file in Safari. I've only tried it with .json files so far. The documentation at https://developer.apple.com/documentation/xcode/sharing-data-with-simulator says that the original behaviour should happen: To add files to Simulator, select one or more files in Finder on your Mac, then click the Share button. Select Simulator from the share destination list. Choose the simulated device from the drop-down list. Simulator opens the Files app, and lets you select where to save the files. I'd love to learn if this is intentional behaviour, and if so, what workarounds there might be. I use this pattern quite a lot, as I have a HealthKit app, and I've built a system that allows me to export workouts as JSON files from a real device, that I can then import into a simulator for testing. Edit: I found a workaround.
7
0
332
5d
Tapping on ShareLink crashes the app
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
1
0
88
5d
Code Coverage Not Generated in Xcode 26.1 Despite Successful Test Runs
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.
1
0
120
5d
Reply to Code Coverage Not Generated in Xcode 26.1 Despite Successful Test Runs
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.
5d
WeatherKit request fail
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
7
0
677
6d
Metal toolchain compilation error after migration to MacOS 26 and XCode 26.1
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
2
0
95
6d
Reply to Metal toolchain compilation error after migration to MacOS 26 and XCode 26.1
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
6d