Search results for

“translate scheme”

6,670 results found

Post

Replies

Boosts

Views

Activity

Xcode 26 Crashes on Launching App After macOS + Xcode Update (M3 Mac)
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 workaro
Topic: Developer Tools & Services SubTopic: Xcode
9
0
793
Nov ’25
Can’t Debug background.js in Safari App Extension (Manifest V3)
I’m developing a Safari App Extension and I want to debug the background.js script. However, I can’t find any tool or option to do this. When I run the extension from Xcode using the ProjectName Extension (macOS) scheme, I expect to see a “ProjectName” item under the Develop → Web Extension Background Content menu. But there’s nothing there. Has anyone encountered the same issue? How did you fix it? Environment: Manifest Version: V3 Safari: 26.0.1 (21622.1.22.11.15) Xcode: 26.0.1 (17A400)
Topic: Safari & Web SubTopic: General Tags:
1
0
715
Nov ’25
CompileAssetCatalogVariant failed with nonzero exit code.
I'm running in a very very very weird error. I have a large asset catalog, consisting of about 2700 assets for 1.19GB of size. I can successfully build and run my project with both release and debug scheme, when a real device or simulator is selected. However, whenever I select Any iOS device (arm64), about 80ish seconds in the build process, the building fails with the following output: CoreUI: Error: unable to add asset to store *** Terminating app due to uncaught exception 'IBPlatformToolFailureException', reason: 'The tool closed the connection (AssetCatalogSimulatorAgent) What I tried and failed: Cleaning DerivedData and restarting PC Building the same project on three different devices, each with a different version of XCode. All failed. running sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService Scanning for duplicate image files, found none. Scanning for duplicate .imageset folders in different folders, found none. Scanning for images that declared a different format than theirs, eg
Topic: Developer Tools & Services SubTopic: Xcode Tags:
6
0
401
Nov ’25
iOS 26.1 is not installed in Xcode Cloud using Xcode 26.1 and iOS 26.1 testing scheme
When running an Xcode Cloud workflow pinned to Xcode 26.1, macOS 26.1 and using a Test Destination for iPhone 15 Pro and iOS 26.1, the following error appears in the xcodebuild-build-for-testing.log: 2025-11-13T19:08:31.855137440Z xcodebuild: error: Unable to find a destination matching the provided destination specifier: 2025-11-13T19:08:31.855318998Z { platform:iOS Simulator, id:704F84C8-025F-4F70-B2D9-FF19B7DC098F } 2025-11-13T19:08:31.855362640Z 2025-11-13T19:08:31.855370957Z Ineligible destinations for the Inbound scheme: 2025-11-13T19:08:31.855381964Z { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device, error:iOS 26.1 is not installed. Please download and install the platform from Xcode > Settings > Components. } This can be fixed if ci_pre_xcodebuild.sh is updated with the following: # Get Xcode major version # `xcodebuild -version` returns something like: # Xcode 26.0.1 # Build version 17A400 XCODE_VERSION=$(xcodebuild -version | head -n 1 | awk '
Topic: Developer Tools & Services SubTopic: Xcode Cloud
1
0
322
Nov ’25
New Xcode lost support of old iOS versions
I cannot install ios device support using Xcode-Settings-> Components. I lost my support for my ios devices. My system ran low on disk space. All of a sudden my Schemes only show Get IOS support for my iPad and iPhone. Both devices run older ios versions : 18, 16. Any ways the Xcode-Settings-> Components just tries to force me to update ios. I don't want ios 26 yet as my app I developing does not play well with it. I may try the remove XCode, restart Mac and fresh install xcode 26 to see if this fixes it. Unpairing/Repairing devices to mac does not start the autodownload of the support files.
Topic: Developer Tools & Services SubTopic: Xcode
1
0
123
Nov ’25
Reply to Private Access Tokens - Documentation?
[quote='806866021, SD2000, /thread/806866, /profile/SD2000'] Is there any further documentation on implementing … ? [/quote] No. Note The original WWDC session that discusses this stuff, WWDC 2025 Session 10077 Replace CAPTCHAs with Private Access Tokens, is no longer available from Apple, but I’ve found that rummaging around on the Internet with the original URL (https://developer.apple.com/videos/play/wwdc2025/10077/) to be a fruitful exercise (-: [quote='806866021, SD2000, /thread/806866, /profile/SD2000'] or has the capability been deprecated? [/quote] That doesn’t follow. PATs are an industry standard thing. We don’t have Apple-specific documentation for that technology in the same way that we don’t have Apple-specific documentation for TCP. However, the history here is a bit tricky: There were originally two Internet drafts: Private Access Tokens and Privacy Pass: The Protocol. Those got merged into Privacy Pass Issuance Protocol. Which was standardised as RFC 9578 Privacy Pass Issuance Protocols. I als
Topic: Privacy & Security SubTopic: General
Nov ’25
URLSession Token Authentication: What's the 'correct' way to do it?
I'm working on an API client for a REST service that uses a custom token-based authentiation scheme. The app hits a specificed authentication endpoint with a username and password, said endpoint returns a token that's good for X amount of time, and the app passes that token along with every subsequent request. When that token expires, we start over.Most literature out there tells me to manually set the Authorization header on my request, but official Apple documentation discourages this, as that header is meant to be 'owned' by the built-in HTTP loading system. That said, official documentation on the 'correct' way to do this is shockingly lacking, and the standard didReceiveChallenge callbacks seem better suited for non-custom Basic/Digest/etc authentication schemes. One thought I had was registering my own URLProtocol subclass to handle our custom flow. However, while I haven't had a chance to sit down and take a crack at that yet, my understanding from skimming these forums is that it's s
Topic: App & System Services SubTopic: General Tags:
5
0
1.0.0k
Nov ’25
Reply to Changing watchOS Deployment Target - What happens to users on old versions
I see, thank you. That's what I suspected but hoped there would be a better solution. Yes, they will. Are you saying that your watch app is the valuable bit, and the iOS app doesn't do anything without the watch app? Well, it's a fitness/workout app, and most users use the Watch to actually work out. The phone app is just for setup and checking your data. (workout is also possible but users prefer to use the watch) You didn't say whether the watchOS app is independent or not. Yes, my app is not independent. Not that I can think of, aside from communicating that watchOS 11 will be required with the next version of the app. Communicating the requirement of watchOS 11 (regardless of the channel) won't be noticed by all users running watchOS 10. Hence, many auto-updated iOS apps will render the app useless to most of these users. To conclude: The only proper workaround is to make the watch app independent, so users on older hardware can keep the older version. Correct? (I'm aware that making the app independent w
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Nov ’25
As soon as I run the app in debug the breakpoints are disabled
After updating my system to macOS Tahoe 26.1 and Xcode 26.1, all breakpoints in my project fail to work. When I run the application in Debug mode, any enabled breakpoint (blue) immediately becomes disabled (grayed out) the moment the app launches. The application runs, but the debugger never stops. This issue occurs in any location, including in the application's init() method, which should always be hit. This behavior suggests that the LLDB debugger is failing to attach to the process at launch or is being instructed not to enable breakpoints. System Configuration: Mac Model: MacBook Pro 14 (2021), Apple M1 Pro macOS Version: Tahoe 26.1 Xcode Version: 26.1 Project Type: SwiftUI App for macOS Troubleshooting Steps Performed (All Unsuccessful): We have performed an extensive series of troubleshooting steps to resolve the issue, none of which have worked. These steps include: Basic Project Cleaning: Cleaned the build folder (Product > Clean Build Folder). Deleted the entire DerivedData directory. Deleted the
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
287
Nov ’25
Reply to Xcode 26.x Frequently Freezes During Breakpoint Debugging with Simulator
[quote='806580021, tczhu, /thread/806580, /profile/tczhu'] our app can only run on the Rosetta simulator [/quote] I want to make a couple of things clear: This isn’t a supported configuration. Honestly, I’ve always been surprised that this works at all. Apple has announce a timeline for the removal of general support for Rosetta. For the details, see the Important box at the top of About the Rosetta translation environment. I encourage you to work with your third-party SDK vendor to resolve this roadblock sooner rather than later. As to your immediate issue, if you create a small test project and run it natively in simulator, does it have the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Nov ’25
Reply to Problem with DriverKitUserClientSample
That sample doesn't quite work out of the box. Here is how you can get it to work on macOS 26 with Xcode 26 (and earlier versions of both, but that's what I'm using). Download the sample from https://developer.apple.com/documentation/driverkit/communicating-between-a-driverkit-extension-and-a-client-app?. Follow only some of the directions under Configure the sample code project: (turn off SIP) - skip this, it is no longer necessary Set Automatically manage signing for both the driver and the app targets Select a development team. Xcode will tell you that you cannot select an individual for this type of signing. ignore the advice about Sign to run locally and AD_HOC_CODE_SIGNING_ALLOWED. ignore all the other stuff. You don't need to make profiles, add capabilities, manually download profiles or add them to Xcode. Now go the Build Settings for the driver and app target, and change the Product Bundle Identifier. The download project uses a disambiguation string that doesn't work, and you end up with very long b
Topic: App & System Services SubTopic: Drivers Tags:
Nov ’25
Xcode 26 Crashes on Launching App After macOS + Xcode Update (M3 Mac)
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 workaro
Topic: Developer Tools & Services SubTopic: Xcode
Replies
9
Boosts
0
Views
793
Activity
Nov ’25
Can’t Debug background.js in Safari App Extension (Manifest V3)
I’m developing a Safari App Extension and I want to debug the background.js script. However, I can’t find any tool or option to do this. When I run the extension from Xcode using the ProjectName Extension (macOS) scheme, I expect to see a “ProjectName” item under the Develop → Web Extension Background Content menu. But there’s nothing there. Has anyone encountered the same issue? How did you fix it? Environment: Manifest Version: V3 Safari: 26.0.1 (21622.1.22.11.15) Xcode: 26.0.1 (17A400)
Topic: Safari & Web SubTopic: General Tags:
Replies
1
Boosts
0
Views
715
Activity
Nov ’25
Reply to Swift Playground preview issues
If my machine translation of the error in that screenshot is correct, you are hitting the issue being discussed in Reoccurring data access prompt issue with Swift Playgrounds 4.6.4 on macOS 26.1. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: Swift Playground Tags:
Replies
Boosts
Views
Activity
Nov ’25
CompileAssetCatalogVariant failed with nonzero exit code.
I'm running in a very very very weird error. I have a large asset catalog, consisting of about 2700 assets for 1.19GB of size. I can successfully build and run my project with both release and debug scheme, when a real device or simulator is selected. However, whenever I select Any iOS device (arm64), about 80ish seconds in the build process, the building fails with the following output: CoreUI: Error: unable to add asset to store *** Terminating app due to uncaught exception 'IBPlatformToolFailureException', reason: 'The tool closed the connection (AssetCatalogSimulatorAgent) What I tried and failed: Cleaning DerivedData and restarting PC Building the same project on three different devices, each with a different version of XCode. All failed. running sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService Scanning for duplicate image files, found none. Scanning for duplicate .imageset folders in different folders, found none. Scanning for images that declared a different format than theirs, eg
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
6
Boosts
0
Views
401
Activity
Nov ’25
iOS 26.1 is not installed in Xcode Cloud using Xcode 26.1 and iOS 26.1 testing scheme
When running an Xcode Cloud workflow pinned to Xcode 26.1, macOS 26.1 and using a Test Destination for iPhone 15 Pro and iOS 26.1, the following error appears in the xcodebuild-build-for-testing.log: 2025-11-13T19:08:31.855137440Z xcodebuild: error: Unable to find a destination matching the provided destination specifier: 2025-11-13T19:08:31.855318998Z { platform:iOS Simulator, id:704F84C8-025F-4F70-B2D9-FF19B7DC098F } 2025-11-13T19:08:31.855362640Z 2025-11-13T19:08:31.855370957Z Ineligible destinations for the Inbound scheme: 2025-11-13T19:08:31.855381964Z { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device, error:iOS 26.1 is not installed. Please download and install the platform from Xcode > Settings > Components. } This can be fixed if ci_pre_xcodebuild.sh is updated with the following: # Get Xcode major version # `xcodebuild -version` returns something like: # Xcode 26.0.1 # Build version 17A400 XCODE_VERSION=$(xcodebuild -version | head -n 1 | awk '
Topic: Developer Tools & Services SubTopic: Xcode Cloud
Replies
1
Boosts
0
Views
322
Activity
Nov ’25
Reply to New Xcode lost support of old iOS versions
Well, The Scheme chooser had only one option to install Xcode 26 support. I downloaded the 8GB installer for it. Afterwards I have gotten back all my old choices of supported Devices/IOSVersions . So this is fixed.
Topic: Developer Tools & Services SubTopic: Xcode
Replies
Boosts
Views
Activity
Nov ’25
New Xcode lost support of old iOS versions
I cannot install ios device support using Xcode-Settings-> Components. I lost my support for my ios devices. My system ran low on disk space. All of a sudden my Schemes only show Get IOS support for my iPad and iPhone. Both devices run older ios versions : 18, 16. Any ways the Xcode-Settings-> Components just tries to force me to update ios. I don't want ios 26 yet as my app I developing does not play well with it. I may try the remove XCode, restart Mac and fresh install xcode 26 to see if this fixes it. Unpairing/Repairing devices to mac does not start the autodownload of the support files.
Topic: Developer Tools & Services SubTopic: Xcode
Replies
1
Boosts
0
Views
123
Activity
Nov ’25
Reply to Private Access Tokens - Documentation?
[quote='806866021, SD2000, /thread/806866, /profile/SD2000'] Is there any further documentation on implementing … ? [/quote] No. Note The original WWDC session that discusses this stuff, WWDC 2025 Session 10077 Replace CAPTCHAs with Private Access Tokens, is no longer available from Apple, but I’ve found that rummaging around on the Internet with the original URL (https://developer.apple.com/videos/play/wwdc2025/10077/) to be a fruitful exercise (-: [quote='806866021, SD2000, /thread/806866, /profile/SD2000'] or has the capability been deprecated? [/quote] That doesn’t follow. PATs are an industry standard thing. We don’t have Apple-specific documentation for that technology in the same way that we don’t have Apple-specific documentation for TCP. However, the history here is a bit tricky: There were originally two Internet drafts: Private Access Tokens and Privacy Pass: The Protocol. Those got merged into Privacy Pass Issuance Protocol. Which was standardised as RFC 9578 Privacy Pass Issuance Protocols. I als
Topic: Privacy & Security SubTopic: General
Replies
Boosts
Views
Activity
Nov ’25
URLSession Token Authentication: What's the 'correct' way to do it?
I'm working on an API client for a REST service that uses a custom token-based authentiation scheme. The app hits a specificed authentication endpoint with a username and password, said endpoint returns a token that's good for X amount of time, and the app passes that token along with every subsequent request. When that token expires, we start over.Most literature out there tells me to manually set the Authorization header on my request, but official Apple documentation discourages this, as that header is meant to be 'owned' by the built-in HTTP loading system. That said, official documentation on the 'correct' way to do this is shockingly lacking, and the standard didReceiveChallenge callbacks seem better suited for non-custom Basic/Digest/etc authentication schemes. One thought I had was registering my own URLProtocol subclass to handle our custom flow. However, while I haven't had a chance to sit down and take a crack at that yet, my understanding from skimming these forums is that it's s
Topic: App & System Services SubTopic: General Tags:
Replies
5
Boosts
0
Views
1.0.0k
Activity
Nov ’25
Reply to Changing watchOS Deployment Target - What happens to users on old versions
I see, thank you. That's what I suspected but hoped there would be a better solution. Yes, they will. Are you saying that your watch app is the valuable bit, and the iOS app doesn't do anything without the watch app? Well, it's a fitness/workout app, and most users use the Watch to actually work out. The phone app is just for setup and checking your data. (workout is also possible but users prefer to use the watch) You didn't say whether the watchOS app is independent or not. Yes, my app is not independent. Not that I can think of, aside from communicating that watchOS 11 will be required with the next version of the app. Communicating the requirement of watchOS 11 (regardless of the channel) won't be noticed by all users running watchOS 10. Hence, many auto-updated iOS apps will render the app useless to most of these users. To conclude: The only proper workaround is to make the watch app independent, so users on older hardware can keep the older version. Correct? (I'm aware that making the app independent w
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Nov ’25
As soon as I run the app in debug the breakpoints are disabled
After updating my system to macOS Tahoe 26.1 and Xcode 26.1, all breakpoints in my project fail to work. When I run the application in Debug mode, any enabled breakpoint (blue) immediately becomes disabled (grayed out) the moment the app launches. The application runs, but the debugger never stops. This issue occurs in any location, including in the application's init() method, which should always be hit. This behavior suggests that the LLDB debugger is failing to attach to the process at launch or is being instructed not to enable breakpoints. System Configuration: Mac Model: MacBook Pro 14 (2021), Apple M1 Pro macOS Version: Tahoe 26.1 Xcode Version: 26.1 Project Type: SwiftUI App for macOS Troubleshooting Steps Performed (All Unsuccessful): We have performed an extensive series of troubleshooting steps to resolve the issue, none of which have worked. These steps include: Basic Project Cleaning: Cleaned the build folder (Product > Clean Build Folder). Deleted the entire DerivedData directory. Deleted the
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
287
Activity
Nov ’25
Reply to Xcode 26.x Frequently Freezes During Breakpoint Debugging with Simulator
[quote='806580021, tczhu, /thread/806580, /profile/tczhu'] our app can only run on the Rosetta simulator [/quote] I want to make a couple of things clear: This isn’t a supported configuration. Honestly, I’ve always been surprised that this works at all. Apple has announce a timeline for the removal of general support for Rosetta. For the details, see the Important box at the top of About the Rosetta translation environment. I encourage you to work with your third-party SDK vendor to resolve this roadblock sooner rather than later. As to your immediate issue, if you create a small test project and run it natively in simulator, does it have the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Nov ’25
Help Setting Up Project for Swift Student Challenge
I was wondering wether you have to create your full app as an Xcode app and then translate it into playgrounds? Because some of the submissions I have seen on YouTube are running on Xcode iPad emulators.
Topic: Community SubTopic: Swift Student Challenge Tags:
Replies
2
Boosts
0
Views
479
Activity
Nov ’25
Reply to URLRequest(url:cachePolicy:timeoutInterval:) started to crash in iOS 26
@DTS Engineer it seems like .crash-files gets translated into text-file... so I can no longer attach it. I will try to upload it and share a link instead...
Topic: App & System Services SubTopic: Networking Tags:
Replies
Boosts
Views
Activity
Nov ’25
Reply to Problem with DriverKitUserClientSample
That sample doesn't quite work out of the box. Here is how you can get it to work on macOS 26 with Xcode 26 (and earlier versions of both, but that's what I'm using). Download the sample from https://developer.apple.com/documentation/driverkit/communicating-between-a-driverkit-extension-and-a-client-app?. Follow only some of the directions under Configure the sample code project: (turn off SIP) - skip this, it is no longer necessary Set Automatically manage signing for both the driver and the app targets Select a development team. Xcode will tell you that you cannot select an individual for this type of signing. ignore the advice about Sign to run locally and AD_HOC_CODE_SIGNING_ALLOWED. ignore all the other stuff. You don't need to make profiles, add capabilities, manually download profiles or add them to Xcode. Now go the Build Settings for the driver and app target, and change the Product Bundle Identifier. The download project uses a disambiguation string that doesn't work, and you end up with very long b
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Nov ’25