Search results for

“Xcode”

93,850 results found

Post

Replies

Boosts

Views

Activity

Reply to Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
We just updated to Tahoe and having same issue; works with CLI and hangs with Xcode 26.3 and 26.4. Note via the CLI we see: ** WARNING: connection is not using a post-quantum key exchange algorithm. ** This session may be vulnerable to store now, decrypt later attacks. ** The server may need to be upgraded. See https://openssh.com/pq.html So perhaps Xcode also sees this warning and is having issues parsing it?
5d
Xcode's built-in AI chat feature (IDEIntelligenceChat) crashes.
According tho Claude, The crash is clearly a bug in Xcode's built-in AI chat feature (IDEIntelligenceChat), not an authentication issue or anything on your end. What the crash log shows: The crash is happening in IDEIntelligenceChat — specifically in ChatInputEditorView.updateView and SourceEditorDataSource.ideChat_gracefullyApplyChangesToReflect. It's a SIGTRAP (assertion/precondition failure) triggered while SwiftUI is trying to lay out the AI chat panel. This is an Apple bug in Xcode 26.2 itself.
1
0
35
5d
Reply to Xcode 26.4 rc
Same issue with Xcode 26.4 (17E192): Failed to authenticate. API Error: 401 {type:error,error:{type:authentication_error,message:OAuth token has expired. Please obtain a new token or refresh your existing token.}request_id:req_...}
5d
Does your Canvas in Xcode crash all the time due to AXRemoteElement-BackgroundFetch?
Hi everyone, yesterday I updated my macOS and Xcode to the latest versions and today I have the strangest thing: Canvas is always crashing whenever I click it, in any and all my Projects. The full Simulator works just fine; only the Preview Canvas crashes. All the crash reports say it's because of AXRemoteElement-BackgroundFetch, and ChatGPT says it's not because of my code. These are very simple Projects, just for experimentation. Nothing complex, just native code while I follow examples in a SwiftUI book. Anyone else having this issue? Translated Report (Full Report Below) ------------------------------------- Process: PreviewShell [2179] Path: /Volumes/VOLUME/*/PreviewShell.app/PreviewShell Identifier: com.apple.PreviewShell Version: 16.0 (23.40.29) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd_sim [1405] Coalition: com.apple.CoreSimulator.SimDevice.E9525D59-3C07-43F9-ACC9-18CF5DD0DAA1 [1516] Responsible Process: SimulatorTrampoline [1120] User ID: 501 Date/Time: 2026-03-26 1
4
0
167
5d
Unable to submit for App Review
Hi. I’m unable submit to a new Version of my App. If i want to Add for Review, i get the Error Message: “Unable to Add for Review The items below are required to start the review process: This build is using a beta version of Xcode and can’t be submitted.” The new Version is Uploaded from the Latest Version of Swift Playground for iPad(4.7). No Betas
0
0
51
5d
Xcode fails to compile Blender-exported USDZ in .rkassets with misleading "permission" error — Xcode 26.3
The error: When building a RealityKitContent package that contains a USDZ file exported from Blender, Xcode throws the following error: error: [xrsimulator] Exception thrown during compile: Cannot get rkassets content for path .../RealityKitContent.rkassets because 'The file RealityKitContent.rkassets couldn't be opened because you don't have permission to view it.' error: Tool exited with code 1 The error message mentions permission — but permissions are not the issue. This appears to be a misleading error from realitytool masking a USD validation failure. What I've ruled out File permissions — all files are -rw-r--r--, user has Read & Write on the folder Extended attributes / quarantine flag — other files with the same @ flag work fine Corrupted archive — unzip -t confirms the USDZ is valid (board.usdc + textures) Stale build cache — deleted DerivedData and com.apple.DeveloperTools cache, no change Key observations The same file builds successfully on my colleague's machine running identical Xcode
1
0
539
5d
Migration to Xcode 26: Requirements, Internal Distribution, and Compatibility Concerns
Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary wor
1
0
47
5d
Reply to xcrun -v notarytool -> rc = 69
Glad to hear you’re making progress. [quote='881521022, balunist, /thread/820402?answerId=881521022#881521022, /profile/balunist'] Was this triggered when I installed the xcode update? [/quote] That seems likely. It’s not uncommon for new versions of Xcode to include a new licence agreement. However, it’s hard to be 100% sure without knowing the exact sequences of steps you took to get into this situation. One little-known gem is that xcodebuild has a command that checks whether the installation is copacetic: % xcodebuild -checkFirstLaunchStatus ; echo $? 0 See the xcodebuild man page for details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
5d
Network Extension "Signature check failed" after archive with Developer ID — works in Xcode debug
I have a macOS VPN app with a Network Extension (packet tunnel provider) distributed outside the App Store via Developer ID. Everything works perfectly when running from Xcode. After archiving and exporting for Developer ID distribution, the extension launches but immediately gets killed by nesessionmanager. The error: Signature check failed: code failed to satisfy specified code requirement(s) followed by: started with PID 0 status changed to disconnected, last stop reason Plugin failed What makes this interesting: the extension process does launch. AMFI approves it, taskgated-helper validates the provisioning profile and says allowing entitlement(s) due to provisioning profile, the sandbox is applied, PacketTunnelProvider is created — but then Apple's Security framework internally fails the designated requirement check and nesessionmanager kills the session. Key log sequence: taskgated-helper: Checking profile: Developer ID - MacOS WireGuardExtension taskgated-helper: allowing entitlement(s) for co
2
0
55
5d
Reply to 90919: Invalid entitlement error in ASC
[quote='820543021, mhenke, /thread/820543, /profile/mhenke'] I filed an issue in the Feedback Assistant [/quote] What was that bug number? Oh, and do you hit this when you choose Validate App in the Xcode organiser? Or only after you’ve uploaded to App Store Connect? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Entitlements Tags:
5d
Reply to sysextd: "no policy, cannot allow apps outside /Applications" - NEFilterDataProvider system extension on macOS 26
It sounds like you’re using Developer ID signing for day-to-day development. That’s a mistake on multiple levels. I talk about this in general in The Care and Feeding of Developer ID, but there are extra issues with system extensions, where system policy requires that Developer ID signed sysexen be notarised. So my advice in this case. Use Apple Development code signing for day-to-day development. Use Developer ID for pre-release testing and distribution. There are a couple of key benefits with this approach: It lets you build and debug without enabling development mode, which is a big win IMO. Xcode’s automatic code signing works well with Apple Development signing. Even if you’re not using Xcode, you can create a small test project in Xcode, get it working, and then follow the same path it took. See Debugging a Network Extension Provider for specific advice on how to bring up a provider in Xcode. One thing that Xcode doesn’t handle is the -systemextension suffix
5d
Reply to Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
I've just updated to Tahoe 26.4, and having similar issues that Xcode can't pull nor fetch but command line git works fine.
Replies
Boosts
Views
Activity
5d
Reply to Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
We just updated to Tahoe and having same issue; works with CLI and hangs with Xcode 26.3 and 26.4. Note via the CLI we see: ** WARNING: connection is not using a post-quantum key exchange algorithm. ** This session may be vulnerable to store now, decrypt later attacks. ** The server may need to be upgraded. See https://openssh.com/pq.html So perhaps Xcode also sees this warning and is having issues parsing it?
Replies
Boosts
Views
Activity
5d
Xcode's built-in AI chat feature (IDEIntelligenceChat) crashes.
According tho Claude, The crash is clearly a bug in Xcode's built-in AI chat feature (IDEIntelligenceChat), not an authentication issue or anything on your end. What the crash log shows: The crash is happening in IDEIntelligenceChat — specifically in ChatInputEditorView.updateView and SourceEditorDataSource.ideChat_gracefullyApplyChangesToReflect. It's a SIGTRAP (assertion/precondition failure) triggered while SwiftUI is trying to lay out the AI chat panel. This is an Apple bug in Xcode 26.2 itself.
Replies
1
Boosts
0
Views
35
Activity
5d
Reply to Does your Canvas in Xcode crash all the time due to AXRemoteElement-BackgroundFetch?
Same. I thought it might be an Xcode 26.4 issue. But the same thing happens on Xcode 26.3. I'm on macOS Tahoe 26.4 (25E246).
Replies
Boosts
Views
Activity
5d
Reply to Xcode 26.4 rc
Same issue with Xcode 26.4 (17E192): Failed to authenticate. API Error: 401 {type:error,error:{type:authentication_error,message:OAuth token has expired. Please obtain a new token or refresh your existing token.}request_id:req_...}
Replies
Boosts
Views
Activity
5d
Can’t paste into Simulator after updating to Xcode 26.4
After updating to Xcode 26.4 (public release), I’m no longer able to paste from the Mac clipboard into the Simulator. Automatically Sync Pasteboard is on, and I have content on the clipboard, but paste doesn’t work—Cmd+V does nothing, and there’s no Paste option in the context menu. Is anyone else seeing this?
Replies
15
Boosts
0
Views
1.4k
Activity
5d
Does your Canvas in Xcode crash all the time due to AXRemoteElement-BackgroundFetch?
Hi everyone, yesterday I updated my macOS and Xcode to the latest versions and today I have the strangest thing: Canvas is always crashing whenever I click it, in any and all my Projects. The full Simulator works just fine; only the Preview Canvas crashes. All the crash reports say it's because of AXRemoteElement-BackgroundFetch, and ChatGPT says it's not because of my code. These are very simple Projects, just for experimentation. Nothing complex, just native code while I follow examples in a SwiftUI book. Anyone else having this issue? Translated Report (Full Report Below) ------------------------------------- Process: PreviewShell [2179] Path: /Volumes/VOLUME/*/PreviewShell.app/PreviewShell Identifier: com.apple.PreviewShell Version: 16.0 (23.40.29) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd_sim [1405] Coalition: com.apple.CoreSimulator.SimDevice.E9525D59-3C07-43F9-ACC9-18CF5DD0DAA1 [1516] Responsible Process: SimulatorTrampoline [1120] User ID: 501 Date/Time: 2026-03-26 1
Replies
4
Boosts
0
Views
167
Activity
5d
Unable to submit for App Review
Hi. I’m unable submit to a new Version of my App. If i want to Add for Review, i get the Error Message: “Unable to Add for Review The items below are required to start the review process: This build is using a beta version of Xcode and can’t be submitted.” The new Version is Uploaded from the Latest Version of Swift Playground for iPad(4.7). No Betas
Replies
0
Boosts
0
Views
51
Activity
5d
Xcode fails to compile Blender-exported USDZ in .rkassets with misleading "permission" error — Xcode 26.3
The error: When building a RealityKitContent package that contains a USDZ file exported from Blender, Xcode throws the following error: error: [xrsimulator] Exception thrown during compile: Cannot get rkassets content for path .../RealityKitContent.rkassets because 'The file RealityKitContent.rkassets couldn't be opened because you don't have permission to view it.' error: Tool exited with code 1 The error message mentions permission — but permissions are not the issue. This appears to be a misleading error from realitytool masking a USD validation failure. What I've ruled out File permissions — all files are -rw-r--r--, user has Read & Write on the folder Extended attributes / quarantine flag — other files with the same @ flag work fine Corrupted archive — unzip -t confirms the USDZ is valid (board.usdc + textures) Stale build cache — deleted DerivedData and com.apple.DeveloperTools cache, no change Key observations The same file builds successfully on my colleague's machine running identical Xcode
Replies
1
Boosts
0
Views
539
Activity
5d
Migration to Xcode 26: Requirements, Internal Distribution, and Compatibility Concerns
Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary wor
Replies
1
Boosts
0
Views
47
Activity
5d
Reply to xcrun -v notarytool -> rc = 69
Glad to hear you’re making progress. [quote='881521022, balunist, /thread/820402?answerId=881521022#881521022, /profile/balunist'] Was this triggered when I installed the xcode update? [/quote] That seems likely. It’s not uncommon for new versions of Xcode to include a new licence agreement. However, it’s hard to be 100% sure without knowing the exact sequences of steps you took to get into this situation. One little-known gem is that xcodebuild has a command that checks whether the installation is copacetic: % xcodebuild -checkFirstLaunchStatus ; echo $? 0 See the xcodebuild man page for details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
5d
Network Extension "Signature check failed" after archive with Developer ID — works in Xcode debug
I have a macOS VPN app with a Network Extension (packet tunnel provider) distributed outside the App Store via Developer ID. Everything works perfectly when running from Xcode. After archiving and exporting for Developer ID distribution, the extension launches but immediately gets killed by nesessionmanager. The error: Signature check failed: code failed to satisfy specified code requirement(s) followed by: started with PID 0 status changed to disconnected, last stop reason Plugin failed What makes this interesting: the extension process does launch. AMFI approves it, taskgated-helper validates the provisioning profile and says allowing entitlement(s) due to provisioning profile, the sandbox is applied, PacketTunnelProvider is created — but then Apple's Security framework internally fails the designated requirement check and nesessionmanager kills the session. Key log sequence: taskgated-helper: Checking profile: Developer ID - MacOS WireGuardExtension taskgated-helper: allowing entitlement(s) for co
Replies
2
Boosts
0
Views
55
Activity
5d
Reply to 90919: Invalid entitlement error in ASC
[quote='820543021, mhenke, /thread/820543, /profile/mhenke'] I filed an issue in the Feedback Assistant [/quote] What was that bug number? Oh, and do you hit this when you choose Validate App in the Xcode organiser? Or only after you’ve uploaded to App Store Connect? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
5d
Reply to sysextd: "no policy, cannot allow apps outside /Applications" - NEFilterDataProvider system extension on macOS 26
It sounds like you’re using Developer ID signing for day-to-day development. That’s a mistake on multiple levels. I talk about this in general in The Care and Feeding of Developer ID, but there are extra issues with system extensions, where system policy requires that Developer ID signed sysexen be notarised. So my advice in this case. Use Apple Development code signing for day-to-day development. Use Developer ID for pre-release testing and distribution. There are a couple of key benefits with this approach: It lets you build and debug without enabling development mode, which is a big win IMO. Xcode’s automatic code signing works well with Apple Development signing. Even if you’re not using Xcode, you can create a small test project in Xcode, get it working, and then follow the same path it took. See Debugging a Network Extension Provider for specific advice on how to bring up a provider in Xcode. One thing that Xcode doesn’t handle is the -systemextension suffix
Replies
Boosts
Views
Activity
5d
Reply to iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
Have you solved it ? I am facing same issue with IPhone 14 (26.04) and Xcode (26.4). CoreDevice / devicectl layer the device remains unavailable, and Xcode cannot use it for on-device build/run.
Replies
Boosts
Views
Activity
6d