Search results for

“Xcode”

93,861 results found

Post

Replies

Boosts

Views

Activity

Reply to Unable to install Metal toolchain through Xcode Cloud
removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer
2w
Reply to New project with new AppIntent throws build error
To see what happened here, I used Xcode 26.4 beta 3 to create a new multi-platform app. I added a new file, added an import statement for App Intents, and then copied in the snippet of getting started code from the documentation. Indeed, this fails to compile. That new project's default build setting configuration is: Swift Langage Version: Swift 5 Approachable Concurrency: Yes Default Actor Isolation: MainActor To allow this to compile, I change the Default Actor Isolation build setting to nonisolated instead. This is worth a bug report — please use Feedback Assistant to report it, and post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer
2w
isEligibleForAgeFeatures: wrong minimum OS version
Dear Apple, while implementing Declared Age Range API in my app, I've noticed a mistake in documentation: the isEligibleForAgeFeatures property is marked 26.0+ in documentation, but 26.2+ in Xcode, which ultimately leads to inability to use it with OS below 26.2. Moreover, I'm thoroughly confused by this quote from documentation: This flag returns true on iOS and iPadOS based on a person’s eligibility and always returns false on macOS. It leads me to two questions: Is it possible to use Declared Age Range API for macOS apps? Will it be possible to use it in future? Will there be any changes regarding this matter in a meantime (especially after Jan 1st)? If yes - when should we expect these changes? If no - why this API declares macOS 26+ support alongside iOS/iPadOS, if it simply doesn't work for macOS now? As of now, my iOS app works flawlessly with given API (on iOS 26.2) while macOS app returns isEligibleForAgeFeatures = false and requestAgeRange request always throws AgeRangeService.Error.notAvai
1
0
286
2w
Reply to Grant Access - Register GitLab Application - 504 Client Timeout
@zoltanbognar Please see Use a remote source control repository for an update to the IP list: If you use an IP allow list either on a self-hosted or cloud SCM provider — such as Bitbucket Server or GitHub Enterprise — make sure Xcode Cloud has access to your Git server. Check your firewall’s inbound HTTPS allow list and grant Xcode Cloud access to your Git server by adding the IP address ranges: 57.103.0.0/22 57.103.64.0/18 2a01:b747:3000:200::/56 2a01:b747:3001:200::/56 2a01:b747:3002:200::/56 2a01:b747:3003:200::/56 2a01:b747:3005:200::/56 2a01:b747:3006:200::/56 2a01:b747:3004:200::/56
2w
Reply to Orphaned XCode simulator disk images
I am unable to unmount them, either from the command line or Disk Utility. How do I go about this? Don't use Disk Utility to mange these installations or mount points. Instead, you can remove simulators with the xcrun simctl runtime delete command. Use xcrun simctl runtime list to get a list of identifiers. You can also do this inside of Xcode's Settings UI. Go to the Components tab, and you'll see a list of what is installed, and the Info button will lead you to an option to remove specific simulators. — Ed Ford,  DTS Engineer
2w
Orphaned XCode simulator disk images
Recently I noticed that although my drive showed ~800Gb of usage, the folders within totally to around ~600Gb (and yes I was including hidden 'dot' files/folders. After some inspection I found that there are a whole set of Disk Media Images, that appear to be related to XCode simulators. Here's an extract from the command line diskutil list command: /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk5 Physical Store disk4s1 1: APFS Volume iOS 26.2 Simulator 17.1 GB disk5s1 /dev/disk6 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.2 GB disk6 1: Apple_APFS Container disk7 14.2 GB disk6s1 /dev/disk7 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.2 GB disk7 Physical Store disk6s1 1: APFS Volume XROS 26.2 Simulator 13.8 GB disk7s1 /dev/disk8 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.2 GB disk8 1: Apple_APFS Container disk9 17.2 GB disk8s1 /dev/disk9 (synthesized): #: TYPE NAME SIZ
1
0
75
2w
Lost connection to my iphone
I was developing on Xcode and downloading and testing just fine. Today when I connect (via cable), clean, build and run the system When I look in the iPhone ->settings -> General ->VPN & Device Management it does not list my developers tag. How do I get the two talking again. I have restarted the MAC (Xcode) and the iPhone multiple times.
1
0
50
2w
DeviceActivityReportExtension: NSExtensionPrincipalClass required by App Store but rejected at runtime
I'm experiencing a contradictory validation issue with DeviceActivityReportExtension that creates an impossible situation: The Problem: Without NSExtensionPrincipalClass in Info.plist → App Store Connect rejects upload with: Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found With NSExtensionPrincipalClass → Local install fails with: defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.deviceactivityui.report-extension Setup: Extension point: com.apple.deviceactivityui.report-extension Using SwiftUI with @main attribute and DeviceActivityReportExtension protocol Xcode 16.2, iOS 17.6 deployment target Code structure: @main struct SpoolReport: DeviceActivityReportExtension { var body: some DeviceActivityReportScene { // Report scenes here } } The extension builds and runs perfectly without NSExtensionPrincipalClass, but cannot be uploaded to App Store Connect. Adding the key
10
0
643
2w
Instruments Crash using swiftui instrument
Instruments is crashing when the swiftui instrument is stopped (the session is finished) and the transfer begins from device to device: Crashed Thread: 11 Dispatch queue: com.apple.swiftuitracingsupport.reading Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [1633] I've tried removing derived data, reinstalling xcode, updating xcode (I originally thought this might be the issue -- I needed to update to 26.2 from the 26 RC -- the update didn't fix crash or change the crash report), and restarting both devices. I'm running Instruments/Xcode 26.2 on a MacBook Pro 15 (2018) running Mac OS 15.7.2 (24G325) with an iPhone 16 Pro Max running 26.2. Hoping someone else might have seen this or could help me troubleshoot. I find the swiftui instrument be helpful and like to use it :) I can post a complete crash report as well.
5
0
217
2w
Reply to ppq.apple.com returning 502 Bad Gateway - Unable to verify developer apps on device
Well, that was exciting |-: [quote='879472022, simonsruggi, /thread/818403?answerId=879472022#879472022, /profile/simonsruggi'] It looks like Apple fixed the issue. [/quote] Yep. I can’t really go into details here, other than to say that: ppq.apple.com is a service on the critical path for the trusted execution of code in some situations [1]. It was having problems. Those are now fixed. I don’t have time to read through all 10 pages of posts on this thread. So, if there’s something you want to draw my attention to here, I recommend that you start a new thread with the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There might be more info about it on the enterprise support side of things, but the only developer-focused reference I could find for it was in an old Xcode help page: Manually trust a developer on iOS.
3w
Xcode Cloud: Unable to Notarize macOS App (Stuck in Infinite Waiting)
Hi everyone, I’m encountering an issue with Xcode Cloud when trying to notarize my macOS app. As shown in the screenshot, there are no errors in the logs, but the process gets stuck indefinitely. The message says: The post-action could not be completed because the build was canceled. No artifacts are generated at all. This problem started recently. Notarization works perfectly when I submit from my local Xcode, so it seems to be specific to Xcode Cloud. Has anyone else experienced this?
5
0
384
2w
Reply to Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
I have same problem with Xcode 26.3 Bun on Xcode 16.4 - Download Container worked User Info: { DVTErrorCreationDateKey = 2026-03-11 14:49:00 +0000; NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The request from the client is missing one or more required fields: A valid filename cannot end in a path separator character Domain: com.apple.dt.remoteservices.error Code: 11015 -- System Information macOS Version 15.7.4 (Build 24G517) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-11T17:49:00+03:00
3w
Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
After updating my Xcode to the latest, I am unable to download an installed app container from the Xcode Devices screen. This currently works with older versions of Xcode with the same app on the same iPad. This worked with older versions of Xcode on the same MacBook as well (including the Xcode 26 beta before updating to the official release yesterday) The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { DVTErrorCreationDateKey = 2025-09-18 20:31:01 +0000; NSURL = file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/; } The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/; } Failed to perform I/O operations. Domain: com.apple.dt.remoteservices.error Code: 11001 Failure Reason: Cannot o
4
0
400
3w
Dumb noob question,,
How can i get a simple figma layout with minimal art into xcode
Replies
1
Boosts
0
Views
65
Activity
2w
Reply to Unable to install Metal toolchain through Xcode Cloud
removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer
Replies
Boosts
Views
Activity
2w
Reply to New project with new AppIntent throws build error
To see what happened here, I used Xcode 26.4 beta 3 to create a new multi-platform app. I added a new file, added an import statement for App Intents, and then copied in the snippet of getting started code from the documentation. Indeed, this fails to compile. That new project's default build setting configuration is: Swift Langage Version: Swift 5 Approachable Concurrency: Yes Default Actor Isolation: MainActor To allow this to compile, I change the Default Actor Isolation build setting to nonisolated instead. This is worth a bug report — please use Feedback Assistant to report it, and post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer
Replies
Boosts
Views
Activity
2w
isEligibleForAgeFeatures: wrong minimum OS version
Dear Apple, while implementing Declared Age Range API in my app, I've noticed a mistake in documentation: the isEligibleForAgeFeatures property is marked 26.0+ in documentation, but 26.2+ in Xcode, which ultimately leads to inability to use it with OS below 26.2. Moreover, I'm thoroughly confused by this quote from documentation: This flag returns true on iOS and iPadOS based on a person’s eligibility and always returns false on macOS. It leads me to two questions: Is it possible to use Declared Age Range API for macOS apps? Will it be possible to use it in future? Will there be any changes regarding this matter in a meantime (especially after Jan 1st)? If yes - when should we expect these changes? If no - why this API declares macOS 26+ support alongside iOS/iPadOS, if it simply doesn't work for macOS now? As of now, my iOS app works flawlessly with given API (on iOS 26.2) while macOS app returns isEligibleForAgeFeatures = false and requestAgeRange request always throws AgeRangeService.Error.notAvai
Replies
1
Boosts
0
Views
286
Activity
2w
Reply to Grant Access - Register GitLab Application - 504 Client Timeout
@zoltanbognar Please see Use a remote source control repository for an update to the IP list: If you use an IP allow list either on a self-hosted or cloud SCM provider — such as Bitbucket Server or GitHub Enterprise — make sure Xcode Cloud has access to your Git server. Check your firewall’s inbound HTTPS allow list and grant Xcode Cloud access to your Git server by adding the IP address ranges: 57.103.0.0/22 57.103.64.0/18 2a01:b747:3000:200::/56 2a01:b747:3001:200::/56 2a01:b747:3002:200::/56 2a01:b747:3003:200::/56 2a01:b747:3005:200::/56 2a01:b747:3006:200::/56 2a01:b747:3004:200::/56
Replies
Boosts
Views
Activity
2w
Reply to Orphaned XCode simulator disk images
I am unable to unmount them, either from the command line or Disk Utility. How do I go about this? Don't use Disk Utility to mange these installations or mount points. Instead, you can remove simulators with the xcrun simctl runtime delete command. Use xcrun simctl runtime list to get a list of identifiers. You can also do this inside of Xcode's Settings UI. Go to the Components tab, and you'll see a list of what is installed, and the Info button will lead you to an option to remove specific simulators. — Ed Ford,  DTS Engineer
Replies
Boosts
Views
Activity
2w
Orphaned XCode simulator disk images
Recently I noticed that although my drive showed ~800Gb of usage, the folders within totally to around ~600Gb (and yes I was including hidden 'dot' files/folders. After some inspection I found that there are a whole set of Disk Media Images, that appear to be related to XCode simulators. Here's an extract from the command line diskutil list command: /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk5 Physical Store disk4s1 1: APFS Volume iOS 26.2 Simulator 17.1 GB disk5s1 /dev/disk6 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.2 GB disk6 1: Apple_APFS Container disk7 14.2 GB disk6s1 /dev/disk7 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.2 GB disk7 Physical Store disk6s1 1: APFS Volume XROS 26.2 Simulator 13.8 GB disk7s1 /dev/disk8 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.2 GB disk8 1: Apple_APFS Container disk9 17.2 GB disk8s1 /dev/disk9 (synthesized): #: TYPE NAME SIZ
Replies
1
Boosts
0
Views
75
Activity
2w
Reply to iOS 26.2 Simulator is not available for download
What Xcode version are you using? I took a look with Xcode 26.4 beta, and the iOS 26.2 simulator is available as a choice when looking at the same UI of available versions to install that you shared a screenshot of. — Ed Ford,  DTS Engineer
Replies
Boosts
Views
Activity
2w
Lost connection to my iphone
I was developing on Xcode and downloading and testing just fine. Today when I connect (via cable), clean, build and run the system When I look in the iPhone ->settings -> General ->VPN & Device Management it does not list my developers tag. How do I get the two talking again. I have restarted the MAC (Xcode) and the iPhone multiple times.
Replies
1
Boosts
0
Views
50
Activity
2w
DeviceActivityReportExtension: NSExtensionPrincipalClass required by App Store but rejected at runtime
I'm experiencing a contradictory validation issue with DeviceActivityReportExtension that creates an impossible situation: The Problem: Without NSExtensionPrincipalClass in Info.plist → App Store Connect rejects upload with: Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found With NSExtensionPrincipalClass → Local install fails with: defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.deviceactivityui.report-extension Setup: Extension point: com.apple.deviceactivityui.report-extension Using SwiftUI with @main attribute and DeviceActivityReportExtension protocol Xcode 16.2, iOS 17.6 deployment target Code structure: @main struct SpoolReport: DeviceActivityReportExtension { var body: some DeviceActivityReportScene { // Report scenes here } } The extension builds and runs perfectly without NSExtensionPrincipalClass, but cannot be uploaded to App Store Connect. Adding the key
Replies
10
Boosts
0
Views
643
Activity
2w
Instruments Crash using swiftui instrument
Instruments is crashing when the swiftui instrument is stopped (the session is finished) and the transfer begins from device to device: Crashed Thread: 11 Dispatch queue: com.apple.swiftuitracingsupport.reading Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [1633] I've tried removing derived data, reinstalling xcode, updating xcode (I originally thought this might be the issue -- I needed to update to 26.2 from the 26 RC -- the update didn't fix crash or change the crash report), and restarting both devices. I'm running Instruments/Xcode 26.2 on a MacBook Pro 15 (2018) running Mac OS 15.7.2 (24G325) with an iPhone 16 Pro Max running 26.2. Hoping someone else might have seen this or could help me troubleshoot. I find the swiftui instrument be helpful and like to use it :) I can post a complete crash report as well.
Replies
5
Boosts
0
Views
217
Activity
2w
Reply to ppq.apple.com returning 502 Bad Gateway - Unable to verify developer apps on device
Well, that was exciting |-: [quote='879472022, simonsruggi, /thread/818403?answerId=879472022#879472022, /profile/simonsruggi'] It looks like Apple fixed the issue. [/quote] Yep. I can’t really go into details here, other than to say that: ppq.apple.com is a service on the critical path for the trusted execution of code in some situations [1]. It was having problems. Those are now fixed. I don’t have time to read through all 10 pages of posts on this thread. So, if there’s something you want to draw my attention to here, I recommend that you start a new thread with the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There might be more info about it on the enterprise support side of things, but the only developer-focused reference I could find for it was in an old Xcode help page: Manually trust a developer on iOS.
Replies
Boosts
Views
Activity
3w
Xcode Cloud: Unable to Notarize macOS App (Stuck in Infinite Waiting)
Hi everyone, I’m encountering an issue with Xcode Cloud when trying to notarize my macOS app. As shown in the screenshot, there are no errors in the logs, but the process gets stuck indefinitely. The message says: The post-action could not be completed because the build was canceled. No artifacts are generated at all. This problem started recently. Notarization works perfectly when I submit from my local Xcode, so it seems to be specific to Xcode Cloud. Has anyone else experienced this?
Replies
5
Boosts
0
Views
384
Activity
2w
Reply to Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
I have same problem with Xcode 26.3 Bun on Xcode 16.4 - Download Container worked User Info: { DVTErrorCreationDateKey = 2026-03-11 14:49:00 +0000; NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The request from the client is missing one or more required fields: A valid filename cannot end in a path separator character Domain: com.apple.dt.remoteservices.error Code: 11015 -- System Information macOS Version 15.7.4 (Build 24G517) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-11T17:49:00+03:00
Replies
Boosts
Views
Activity
3w
Xcode Devices "Download Container" no longer works on latest Xcode 26.0 (24228) (Build 17A324)
After updating my Xcode to the latest, I am unable to download an installed app container from the Xcode Devices screen. This currently works with older versions of Xcode with the same app on the same iPad. This worked with older versions of Xcode on the same MacBook as well (including the Xcode 26 beta before updating to the official release yesterday) The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { DVTErrorCreationDateKey = 2025-09-18 20:31:01 +0000; NSURL = file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/; } The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/; } Failed to perform I/O operations. Domain: com.apple.dt.remoteservices.error Code: 11001 Failure Reason: Cannot o
Replies
4
Boosts
0
Views
400
Activity
3w