Search results for

“file uri scheme”

81,720 results found

Post

Replies

Boosts

Views

Activity

Reply to Help with visionOS pushWindow issues requested
Hey @drewolbrich, Thank you for filing all of these reports! Having each issue tracked separately is really helpful for our investigations. In terms of workarounds, your suggestions sound reasonable, but I don't have specific workarounds to recommend at this time. If you find anything else that helps you avoid the issue, please share it with the community here. For others encountering similar issues: Even though we're aware of this issue, we still encourage you to open a bug report, and post the FB number here once you do. The specific info you include in your bug report might help our investigation, and filing the bug report allows you to get notified when it is resolved. Bug Reporting: How and Why? Thanks, Michael
Topic: Spatial Computing SubTopic: General Tags:
1w
Reply to RealityView attachment draw order
Hey @drewolbrich, Thanks for filing this feedback. I wasn't able to replicate your experience, but I'm curious if you get the same result by replacing opacity(_:) with OpacityComponent? Additionally, have you considered applying a subtle breakthrough effect on your views? This might mitigate the issue and could improve things if you expect your views to collide your content. Are you able to replicate this behavior in a sample project that we could take a look at? Feel free to link it publicly here, or you can privately share any project with us in your Feedback Request. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Thanks, Michael
Topic: Spatial Computing SubTopic: General Tags:
1w
Reply to App Store Connect API returning 403 from perfPowerMetrics using Admin / Dev role keys
Since adopting a newer AppStoreConnect API OpenAPI spec, the trailing '/' in the server was added back; this was something I manually patched last summer. Without the patch to remove the trailing '/', when used with the Swift OpenAPI Generator, a URL with two slashes is produced which was invalid against the SCOPE of the token evidently. Notice .com//v1 and the double slash. https://api.appstoreconnect.apple.com//v1/apps/1672441148/perfPowerMetrics There is nothing wrong with the App Store Connect API itself other than perhaps the scope should honor two slashes since the spec declares it? I submitted a feedback for this last summer to have the Apple minted OpenAPI spec remove the trailing slash in the server url. FB18389250 - AppStoreConnect API: OpenAPI spec file has a server trailing '/' which results in Swift OpenAPI Generator code to have paths with two slashes unexpectedly
Topic: App Store Distribution & Marketing SubTopic: App Store Connect API Tags:
1w
The Xcode 26.3 project build failed
0 0x1001bd52c __assert_rtn + 252 1 0x100132054 void std::__1::__introsort(ld::Atom const**, ld::Atom const**, ld::AliasAddressOrderer&, std::__1::iterator_traits::difference_type, bool) + 0 2 0x1001319a4 ld::LayoutLinkedImage::assignAtomOffsetsInSection(ld::SectionLayout&, unsigned int, bool) + 680 3 0x100136724 void dispatchForEach(std::__1::span, unsigned long, ld::LayoutLinkedImage::sortAtomsWithinSections()::$_0)::'lambda'(unsigned long)::operator()(unsigned long) const + 7852 4 0x19dca8aec _dispatch_client_callout2 + 16 5 0x19dca37f8 _dispatch_apply_invoke3 + 336 6 0x19dca8ad4 _dispatch_client_callout + 16 7 0x19dc91a60 _dispatch_once_callout + 32 8 0x19dca2938 _dispatch_apply_invoke + 252 9 0x19dca8ad4 _dispatch_client_callout + 16 10 0x19dcc59dc _dispatch_channel_invoke.cold.5 + 32 11 0x19dca113c _dispatch_root_queue_drain + 736 12 0x19dca1784 _dispatch_worker_thread2 + 180 13 0x19de47e10 _pthread_wqthread + 232 ld snapshot written at /tmp/****app.debug.dylib-2026-03-24-092748.ld-snapshot ld: A
Topic: Developer Tools & Services SubTopic: Xcode
0
0
82
1w
"Invalid Certificate Signing Request" error when generating MDM Push Certificate
Hello, I am currently developing an MDM solution, including both the sever-side(.NET) and the client app. I have recently been granted the MDM CSR signing permission in the Certificates, Identifier & Profiles of my developer account. I am following the official Apple documentation, Setting up Push Notifications for your MDM Customers, to generate the required MDM Push Certificate. However, I keep encountering the Invalid Certificate Signing Request error when uploading the encoded .plist file to the Apple Push Certificates Portal(identity.apple.com/pushcert). The steps I have taken so far: Generated .csr file via Keychain Access Used the MDM SCR certificate to sign the request. Created a .plist file for th final upload containing : Customer CSR: Base64 encoded Signature : Signed using the SHA256withRSA algorithm and Base64 encoded. Certificate Chain : Including my MDM Vendor Signing Certificate, the Apple WWDR intermediate certificate, and the Apple Root CA. Issues/Questions: Is
Topic: App & System Services SubTopic: Notifications Tags:
0
0
44
1w
macOS 26.4 regression with Mac Catalyst apps using PhotoKit: Photos do not appear when using limited access - Failed to get sandbox extension for url - Image request failed with error PHPhotosErrorDomain Code 3303
I just submitted FB22318443. In Mac Catalyst apps running on macOS 26.4, if you choose to limit the app's access to specific photos (as opposed to granting full access), the photos do not appear in the app. 💀 This issue does not occur on iPadOS. It is a macOS 26.4 regression. It occurs even with apps built using a previous version of the SDK such as 26.2. A sample of the console logs: [RM]: 4-1-1 failed to decode for asset: 9290CC20-B85D-47B5-BDBE-D330FE61773D, error code: 3303, description: Error Domain=PHPhotosErrorDomain Code=3303 (null) Failed to get sandbox extension for url: file:///Users/Jordan/Pictures/Photos%20Library.photoslibrary/resources/derivatives/masters/9/9290CC20-B85D-47B5-BDBE-D330FE61773D_4_5005_c.jpeg, error: Error Domain=com.apple.photos.error Code=44001 sandbox extension not in the cache after requesting them for path: /Users/Jordan/Pictures/Photos Library.photoslibrary/resources/derivatives/masters/9/9290CC20-B85D-47B5-BDBE-D330FE61773D_4_5005_c.jpeg UserInfo={NSDebugDescript
Topic: Media Technologies SubTopic: Photos & Camera Tags:
0
0
249
1w
Reply to symbolicate crashlog using .symbols files instead of dSYMs
In a threaded comment, @kambala said: right now CI (GH Actions) produces iOS builds as well as the .symbols files (which are generated from dSYM using symbols command), but I upload builds manually from my Mac (this will be changed in the future to upload from CI directly). I can of course also store dSYM as a build artifact, but wondered if it's possible to avoid that and store the minimal amount of artifacts on CI. As I said above, you should be keeping the entire Xcode archive, which includes the original dSYM file for any build that you ship to your customers. There's a few things that underpin this advice, including the ability to symbolicate any crash report coming from the field on any version of your app in active use, but also the ability to export your app for different types of distribution, which can enable some further testing and debugging workflows. I can't speak to the storage details of your particular CI system, but for Xcode Cloud, you are provided with the ability to down
Topic: Developer Tools & Services SubTopic: General Tags:
1w
Reply to System-wide deadlock in removexattr from revisiond / APFS
I opened one last week. Case-ID: 18860388 I don't think that’s a valid bug number. Details on the bug filing process are here, and the numbers are prefixed FB. Again, please upload the full spintrace to that bug and then post the bug number back here. It definitely revised (well, APFS), that's holding the lock. Sure, but the question is why, not who. Causes this kind of hang are the interactions between multiple locks and multiple processes. It's hard to pick up unless you're looking at the full log and know what you're looking for, but the basic form is that there are two locks: The outer lock, which the blocking thread (in this case, thread 0xc0616d) is inside and holding. The inner lock, which the blocking thread (thread 0xc0616d) is stuck waiting on. You can actually see this dynamic in the traces you sent. This lock is an APFS-owned lock: *940 apfs_vnop_getattr + 312 (apfs + 604336) [0xfffffe000beacff0] *940 IORWLockRead + 144 (kernel.release.t6000 + 496568) [0xfffffe00088e53b8] And, unsurprisin
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Static library links on device but fails on iOS Simulator
There is potentially one detail I jumped over that is relevant — are you expecting clients of your library to build from source, or to consume a pre-compiled library? I had assumed it was a pre-compiled library based on the .a file mention. I think that's accurate, but it would be good to confirm that. If the library is intended to be a pre-compiled asset, then what you'd deliver to the client is an XCFramework. This is meant to be a single container that has everything a library client needs — copies of a built binary for each platform and simulator your library supports, plus the header files. While you can hand your clients the XCFramework so they can drag-and-drop it in their Xcode project, one nice vehicle you can use for distribution is a Swift package, which will point to a compressed (zipped) copy of the XCFramework, along with a checksum for verifying its integrity. This way, it's easy to ship updates of the library to your clients. Distributing binary frameworks as Swift packages h
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1w
Reply to Universal Links and Cloud-testing platforms
Hi, Thank you for the follow-up and for confirming the AASA multi-App ID support, that is a useful detail. Just to make sure we fully understand the recommendation: are you suggesting we add the testing platform's Team ID + Bundle ID to our AASA file so that their re-signed build is also a trusted app for our domain? If so, we want to understand the security implications of listing a third-party signing identity in our AASA file before going down that path. Regarding TestFlight, we are already using it for manual pre-release testing and it works well for that purpose. Our challenge is specifically with automated UI testing in a cloud device farm, where TestFlight distribution is not part of the workflow. We also wanted to ask about a hybrid distribution approach we are considering, and whether it is permitted under Apple's terms: Use the Apple Developer Enterprise Program to distribute the app internally to our cloud-based testing infrastructure, allowing their re-signing process to work und
Topic: Code Signing SubTopic: Entitlements Tags:
1w
Reply to EASession(accessory:forProtocol:) always returns nil — MFI accessory iAP2
Since I have already ruled out SwiftUI lifecycle interference and simulator limitations, are there specific logging categories in Console.app or internal ExternalAccessory states you recommend I monitor to diagnose why the connection is failing? There isn't a lot that can go wrong from the app side, assuming your app is properly configured and functional. As one more confirmation test, I would suggest testing with the old EADemo sample. The code is fairly old, but you should still be able to get it working without too much effort. If that's failing, then that's pretty strong evidence that it's either a bug in the system or a problem with the accessory. Has your accessory passed certification? And have you ever been able to work with the ExternalAccessory framework/app? Finally, have you filed a bug on this and, if so, what's the bug number? __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Hardware Tags:
1w
Code Signing "Invalid", No Reason Given
Hello, At work, we want to release a new version of our cross-platform desktop application this week. Unfortunately, I've had issues getting the dmg signed by the Apple notary service, which will delay the release until it's successful. However, I remade and successfully signed the previously released version (also dmg) with the same credentials, so I know it's not a problem with the file format or my account. I have tried the following to no avail: Lots of Googling Running xcrun notarytool submit with the -v option (verbose) to see more error messages Going to the URL given (appstoreconnect.apple.com/notary/v2/submissions/{submission_id}) and examining the file it downloaded (not much info, let alone helpful info) Contacting Apple developer support over the phone (they couldn't help with this particular issue, since it's code-level support) The only big change we made this time was switching to Maven for our build tool and dependency management (we previously used Ant with manual dependency
Topic: Code Signing SubTopic: Notarization Tags:
3
0
257
1w
Reply to Universal Links and Cloud-testing platforms
Thanks so much for the reply and the detailed information. Yes, looks like the resigning will cause the issue you have described. I still recommend you to test against your devices to make sure the AASA file get downloaded and works well before sending the build to the App Store. You are correct that we do not offer a native provisioning flag to bypass AASA validation. Apple’s AASA file specification fully supports listing multiple App IDs (Team ID + Bundle ID) for a single domain. You can also use TestFlight to distribute your app to test devices. Wish you luck. Looking forward to your app. Albert Pascual
  Worldwide Developer Relations.
Topic: Code Signing SubTopic: Entitlements Tags:
1w
Reply to Help with visionOS pushWindow issues requested
Hey @drewolbrich, Thank you for filing all of these reports! Having each issue tracked separately is really helpful for our investigations. In terms of workarounds, your suggestions sound reasonable, but I don't have specific workarounds to recommend at this time. If you find anything else that helps you avoid the issue, please share it with the community here. For others encountering similar issues: Even though we're aware of this issue, we still encourage you to open a bug report, and post the FB number here once you do. The specific info you include in your bug report might help our investigation, and filing the bug report allows you to get notified when it is resolved. Bug Reporting: How and Why? Thanks, Michael
Topic: Spatial Computing SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to RealityView attachment draw order
Hey @drewolbrich, Thanks for filing this feedback. I wasn't able to replicate your experience, but I'm curious if you get the same result by replacing opacity(_:) with OpacityComponent? Additionally, have you considered applying a subtle breakthrough effect on your views? This might mitigate the issue and could improve things if you expect your views to collide your content. Are you able to replicate this behavior in a sample project that we could take a look at? Feel free to link it publicly here, or you can privately share any project with us in your Feedback Request. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Thanks, Michael
Topic: Spatial Computing SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to App Store Connect API returning 403 from perfPowerMetrics using Admin / Dev role keys
Since adopting a newer AppStoreConnect API OpenAPI spec, the trailing '/' in the server was added back; this was something I manually patched last summer. Without the patch to remove the trailing '/', when used with the Swift OpenAPI Generator, a URL with two slashes is produced which was invalid against the SCOPE of the token evidently. Notice .com//v1 and the double slash. https://api.appstoreconnect.apple.com//v1/apps/1672441148/perfPowerMetrics There is nothing wrong with the App Store Connect API itself other than perhaps the scope should honor two slashes since the spec declares it? I submitted a feedback for this last summer to have the Apple minted OpenAPI spec remove the trailing slash in the server url. FB18389250 - AppStoreConnect API: OpenAPI spec file has a server trailing '/' which results in Swift OpenAPI Generator code to have paths with two slashes unexpectedly
Topic: App Store Distribution & Marketing SubTopic: App Store Connect API Tags:
Replies
Boosts
Views
Activity
1w
The Xcode 26.3 project build failed
0 0x1001bd52c __assert_rtn + 252 1 0x100132054 void std::__1::__introsort(ld::Atom const**, ld::Atom const**, ld::AliasAddressOrderer&, std::__1::iterator_traits::difference_type, bool) + 0 2 0x1001319a4 ld::LayoutLinkedImage::assignAtomOffsetsInSection(ld::SectionLayout&, unsigned int, bool) + 680 3 0x100136724 void dispatchForEach(std::__1::span, unsigned long, ld::LayoutLinkedImage::sortAtomsWithinSections()::$_0)::'lambda'(unsigned long)::operator()(unsigned long) const + 7852 4 0x19dca8aec _dispatch_client_callout2 + 16 5 0x19dca37f8 _dispatch_apply_invoke3 + 336 6 0x19dca8ad4 _dispatch_client_callout + 16 7 0x19dc91a60 _dispatch_once_callout + 32 8 0x19dca2938 _dispatch_apply_invoke + 252 9 0x19dca8ad4 _dispatch_client_callout + 16 10 0x19dcc59dc _dispatch_channel_invoke.cold.5 + 32 11 0x19dca113c _dispatch_root_queue_drain + 736 12 0x19dca1784 _dispatch_worker_thread2 + 180 13 0x19de47e10 _pthread_wqthread + 232 ld snapshot written at /tmp/****app.debug.dylib-2026-03-24-092748.ld-snapshot ld: A
Topic: Developer Tools & Services SubTopic: Xcode
Replies
0
Boosts
0
Views
82
Activity
1w
"Invalid Certificate Signing Request" error when generating MDM Push Certificate
Hello, I am currently developing an MDM solution, including both the sever-side(.NET) and the client app. I have recently been granted the MDM CSR signing permission in the Certificates, Identifier & Profiles of my developer account. I am following the official Apple documentation, Setting up Push Notifications for your MDM Customers, to generate the required MDM Push Certificate. However, I keep encountering the Invalid Certificate Signing Request error when uploading the encoded .plist file to the Apple Push Certificates Portal(identity.apple.com/pushcert). The steps I have taken so far: Generated .csr file via Keychain Access Used the MDM SCR certificate to sign the request. Created a .plist file for th final upload containing : Customer CSR: Base64 encoded Signature : Signed using the SHA256withRSA algorithm and Base64 encoded. Certificate Chain : Including my MDM Vendor Signing Certificate, the Apple WWDR intermediate certificate, and the Apple Root CA. Issues/Questions: Is
Topic: App & System Services SubTopic: Notifications Tags:
Replies
0
Boosts
0
Views
44
Activity
1w
macOS 26.4 regression with Mac Catalyst apps using PhotoKit: Photos do not appear when using limited access - Failed to get sandbox extension for url - Image request failed with error PHPhotosErrorDomain Code 3303
I just submitted FB22318443. In Mac Catalyst apps running on macOS 26.4, if you choose to limit the app's access to specific photos (as opposed to granting full access), the photos do not appear in the app. 💀 This issue does not occur on iPadOS. It is a macOS 26.4 regression. It occurs even with apps built using a previous version of the SDK such as 26.2. A sample of the console logs: [RM]: 4-1-1 failed to decode for asset: 9290CC20-B85D-47B5-BDBE-D330FE61773D, error code: 3303, description: Error Domain=PHPhotosErrorDomain Code=3303 (null) Failed to get sandbox extension for url: file:///Users/Jordan/Pictures/Photos%20Library.photoslibrary/resources/derivatives/masters/9/9290CC20-B85D-47B5-BDBE-D330FE61773D_4_5005_c.jpeg, error: Error Domain=com.apple.photos.error Code=44001 sandbox extension not in the cache after requesting them for path: /Users/Jordan/Pictures/Photos Library.photoslibrary/resources/derivatives/masters/9/9290CC20-B85D-47B5-BDBE-D330FE61773D_4_5005_c.jpeg UserInfo={NSDebugDescript
Topic: Media Technologies SubTopic: Photos & Camera Tags:
Replies
0
Boosts
0
Views
249
Activity
1w
Reply to symbolicate crashlog using .symbols files instead of dSYMs
In a threaded comment, @kambala said: right now CI (GH Actions) produces iOS builds as well as the .symbols files (which are generated from dSYM using symbols command), but I upload builds manually from my Mac (this will be changed in the future to upload from CI directly). I can of course also store dSYM as a build artifact, but wondered if it's possible to avoid that and store the minimal amount of artifacts on CI. As I said above, you should be keeping the entire Xcode archive, which includes the original dSYM file for any build that you ship to your customers. There's a few things that underpin this advice, including the ability to symbolicate any crash report coming from the field on any version of your app in active use, but also the ability to export your app for different types of distribution, which can enable some further testing and debugging workflows. I can't speak to the storage details of your particular CI system, but for Xcode Cloud, you are provided with the ability to down
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to System-wide deadlock in removexattr from revisiond / APFS
I opened one last week. Case-ID: 18860388 I don't think that’s a valid bug number. Details on the bug filing process are here, and the numbers are prefixed FB. Again, please upload the full spintrace to that bug and then post the bug number back here. It definitely revised (well, APFS), that's holding the lock. Sure, but the question is why, not who. Causes this kind of hang are the interactions between multiple locks and multiple processes. It's hard to pick up unless you're looking at the full log and know what you're looking for, but the basic form is that there are two locks: The outer lock, which the blocking thread (in this case, thread 0xc0616d) is inside and holding. The inner lock, which the blocking thread (thread 0xc0616d) is stuck waiting on. You can actually see this dynamic in the traces you sent. This lock is an APFS-owned lock: *940 apfs_vnop_getattr + 312 (apfs + 604336) [0xfffffe000beacff0] *940 IORWLockRead + 144 (kernel.release.t6000 + 496568) [0xfffffe00088e53b8] And, unsurprisin
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Static library links on device but fails on iOS Simulator
There is potentially one detail I jumped over that is relevant — are you expecting clients of your library to build from source, or to consume a pre-compiled library? I had assumed it was a pre-compiled library based on the .a file mention. I think that's accurate, but it would be good to confirm that. If the library is intended to be a pre-compiled asset, then what you'd deliver to the client is an XCFramework. This is meant to be a single container that has everything a library client needs — copies of a built binary for each platform and simulator your library supports, plus the header files. While you can hand your clients the XCFramework so they can drag-and-drop it in their Xcode project, one nice vehicle you can use for distribution is a Swift package, which will point to a compressed (zipped) copy of the XCFramework, along with a checksum for verifying its integrity. This way, it's easy to ship updates of the library to your clients. Distributing binary frameworks as Swift packages h
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
1w
Reply to Universal Links and Cloud-testing platforms
Hi, Thank you for the follow-up and for confirming the AASA multi-App ID support, that is a useful detail. Just to make sure we fully understand the recommendation: are you suggesting we add the testing platform's Team ID + Bundle ID to our AASA file so that their re-signed build is also a trusted app for our domain? If so, we want to understand the security implications of listing a third-party signing identity in our AASA file before going down that path. Regarding TestFlight, we are already using it for manual pre-release testing and it works well for that purpose. Our challenge is specifically with automated UI testing in a cloud device farm, where TestFlight distribution is not part of the workflow. We also wanted to ask about a hybrid distribution approach we are considering, and whether it is permitted under Apple's terms: Use the Apple Developer Enterprise Program to distribute the app internally to our cloud-based testing infrastructure, allowing their re-signing process to work und
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
1w
Reply to EASession(accessory:forProtocol:) always returns nil — MFI accessory iAP2
Since I have already ruled out SwiftUI lifecycle interference and simulator limitations, are there specific logging categories in Console.app or internal ExternalAccessory states you recommend I monitor to diagnose why the connection is failing? There isn't a lot that can go wrong from the app side, assuming your app is properly configured and functional. As one more confirmation test, I would suggest testing with the old EADemo sample. The code is fairly old, but you should still be able to get it working without too much effort. If that's failing, then that's pretty strong evidence that it's either a bug in the system or a problem with the accessory. Has your accessory passed certification? And have you ever been able to work with the ExternalAccessory framework/app? Finally, have you filed a bug on this and, if so, what's the bug number? __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Hardware Tags:
Replies
Boosts
Views
Activity
1w
Code Signing "Invalid", No Reason Given
Hello, At work, we want to release a new version of our cross-platform desktop application this week. Unfortunately, I've had issues getting the dmg signed by the Apple notary service, which will delay the release until it's successful. However, I remade and successfully signed the previously released version (also dmg) with the same credentials, so I know it's not a problem with the file format or my account. I have tried the following to no avail: Lots of Googling Running xcrun notarytool submit with the -v option (verbose) to see more error messages Going to the URL given (appstoreconnect.apple.com/notary/v2/submissions/{submission_id}) and examining the file it downloaded (not much info, let alone helpful info) Contacting Apple developer support over the phone (they couldn't help with this particular issue, since it's code-level support) The only big change we made this time was switching to Maven for our build tool and dependency management (we previously used Ant with manual dependency
Topic: Code Signing SubTopic: Notarization Tags:
Replies
3
Boosts
0
Views
257
Activity
1w
Reply to Universal Links and Cloud-testing platforms
Thanks so much for the reply and the detailed information. Yes, looks like the resigning will cause the issue you have described. I still recommend you to test against your devices to make sure the AASA file get downloaded and works well before sending the build to the App Store. You are correct that we do not offer a native provisioning flag to bypass AASA validation. Apple’s AASA file specification fully supports listing multiple App IDs (Team ID + Bundle ID) for a single domain. You can also use TestFlight to distribute your app to test devices. Wish you luck. Looking forward to your app. Albert Pascual
  Worldwide Developer Relations.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
1w
Reply to Xcode 26.2 Can't download
If you end up filing a bug please post the FB number here for our records. Bug Reporting: How and Why? has tips on creating your bug report. Albert Pascual
  Worldwide Developer Relations.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
1w
Reply to Xcode 26.2 Can't download
Could you also file a feedback assistant bug report with a sudo sysdiagnose, and xcrun simctl diagnose to help our analysis? thank you!
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
1w