I was able to work around this by: Creating a public link in the External Group of Testers. I opened the link on my iPhone and installed the app. Finally I disabled the public link

Nothing here worked for me: killall -9 CoreDeviceService Rebooting my Mac Deleting the iOS 27 runtime and redownloading it. Important: Make sure xcode-select -p points to Xcode 27 What Did Work: xcrun simctl list runtimes == Runtimes == iOS 17.5 (17.5 - 21F79) - com.apple.CoreSimulator.SimRuntime.iOS-17-5 iOS 18.6 (18.6 - 22G86) - com.apple.CoreSimulator.SimRuntime.iOS-18-6 iOS 26.5 (26.5 - 23F77) - com.apple.CoreSimulator.SimRuntime.iOS-26-5 No iOS 27 available xcrun simctl runtime list == Disk Images == -- iOS -- iOS 27.0 (24A5370g) - 4EAB5C4B-49E0-4B36-8246-675516A14272 (Ready) iOS 26.5 (23F77) - 1918693C-F6E5-4415-8F9A-736276226458 (Ready) iOS 17.5 (21F79) - D8736FD3-D7AB-46DE-817B-950AC88F927A (Ready) iOS 18.6 (22G86) - CB3CC73B-14BD-4280-89F3-DEFE16123B5B (Ready) iOS 27 is Downloaded Run command xcrun simctl runtime list -v to get the location of the Image Path .dmg file then run the command xcrun simctl runtime add <.dmg> on my system the command was xcrun simctl runtime add /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/12fedd911678cfd66b3cf9a6e4cd2dc16e5a2a8e.asset/AssetData/Restore/094-14693-083.dmg D: 94DF7EC5-2697-4AEF-AAB1-24D09B19F216 iOS (27.0 - 24A5370g) (Ready) xcrun simctl list runtimes == Runtimes == iOS 17.5 (17.5 - 21F79) - com.apple.CoreSimulator.SimRuntime.iOS-17-5 iOS 18.6 (18.6 - 22G86) - com.apple.CoreSimulator.SimRuntime.iOS-18-6 iOS 26.5 (26.5 - 23F77) - com.apple.CoreSimulator.SimRuntime.iOS-26-5 iOS 27.0 (27.0 - 24A5370g) - com.apple.CoreSimulator.SimRuntime.iOS-27-0 Victory

Also I was cleaning up my screenshots from WWDC and saw this question of yours in a Q&A Is there a way to open the Terminal on the project root folder in Xcode? I have a Behavior in Xcode and a script ~/bin/openterminal.sh #!/bin/bash env | sort > ~/Xcode_behaviors.out echo "XcodeWorkspace = $XcodeWorkspace" >> ~/Xcode_behaviors.out echo "XcodeProject = $XcodeProject" >> ~/Xcode_behaviors.out if [ "$XcodeWorkspace" == "package.xcworkspace" ] then echo "open dir: $XcodeProjectPath/.." >> ~/Xcode_behaviors.out open -a Terminal "$XcodeWorkspacePath/../../.." elif [ -n "$XcodeProject" ] then echo "open dir: $XcodeProjectPath/.." >> ~/Xcode_behaviors.out open -a Terminal "$XcodeProjectPath/.." else echo "open dir: $HOME" >> ~/Xcode_behaviors.out open -a Terminal "$HOME" fi # PROJECT # # XcodeDeveloperApplicationsDirectory=/Applications/Xcode 15.app/Contents/Developer/Applications # XcodeDeveloperDirectory=/Applications/Xcode 15.app/Contents/Developer # XcodeDeveloperPlatformsDirectory=/Applications/Xcode 15.app/Contents/Developer/Platforms # XcodeProject=TestCodeScanner.xcodeproj # XcodeProjectPath=/Users/gdunham/Library/CloudStorage/Dropbox/Development/DDS Experiments/TestCodeScanner/TestCodeScanner.xcodeproj # XcodeWorkspacePath=/Users/gdunham/Library/CloudStorage/Dropbox/Development/DDS Experiments/TestCodeScanner/TestCodeScanner.xcodeproj/project.xcworkspace # PACKAGE # # XcodeDeveloperApplicationsDirectory=/Applications/Xcode 15.app/Contents/Developer/Applications # XcodeDeveloperDirectory=/Applications/Xcode 15.app/Contents/Developer # XcodeDeveloperPlatformsDirectory=/Applications/Xcode 15.app/Contents/Developer/Platforms # XcodeWorkspace=package.xcworkspace # XcodeWorkspacePath=/Users/gdunham/Library/CloudStorage/Dropbox/Development/DDS Swift Packages/DDSUtilities/.swiftpm/xcode/package.xcworkspace

The toolbar button defults to the last used. To select a different provider you need to use the "Coding Assistant" Navigator "New Conversation" Button. To select the Model use you need to change the model setting in "Xcode Settings" -> "Intelligence" -> "Claude Agent" If this is a problem you and every one that reads this should submit a Feedback.

The issue is that you can open an AI Conversation in an Editor Pane using the contex menu but not a source coded file. With out tweaking your Xcode Navigation Settings to use either Destination Chooser or Open in Editor Pane. I file a Feedback FB23258229 on this Here is how to change your Xcode Navigation Settings

I totally missed the inspector. I filed a feedback FB23141979 using the Feedback Assistent App. You should too the more feedback the more likely it will be fixed.

In the Xcode Group Lab they state that Xcode 27 projects are compatible with Xcode 26 except for one project setting check box "Strictly Validate" You will also need to set the "Minimum Deployment" version to 26.0 or earlier. If you use an API not available in your minimum deployment version you will get an error. if #available(macOS 27.0, *) You cannot add an if available conditional check because macOS 27.0 is not defined when open the project in Xcode 26. My suggestion would be to comment out the API you would like to use with a note and use an older API. Then when Xcode 27 is released for submissions you can uncomment it and use an if available test.

In the Xcode Settings -> General you can set the Navigator Size to Small | Medium | Large

Menu File -> New -> Project produces the following for me Down Arrow x 2

I have a Claude Pro subscriptions and tried this with a Claude Agent and it worked just like in the video. But if I use the free OpenAI GPT-5 Chat then I don't get the links. There is a significant capability difference between an agent and just a plain chat. The agents have tools that make them much smarter and have access to your file system, but other than running an open source agent on your own hardware, you will need a subscription. I got an open source chat model running on my laptop last night using MLX. I have yet to get the OpenCode Agent working yet. Cheers.

The fix if you want to keep ENABLE_USER_SCRIPT_SANDBOXING enabled is to add the files as inputs and outputs. I use a script to set the build number in the build info plist file. I just need to set "${TARGET_BUILD_DIR}/${INFOPLIST_PATH}" as an output of the script build setting ENABLE_USER_SCRIPT_SANDBOXING was added in Xcode 14 but enabled in the update to recommend setting in Xcode 15 From the Xcode 14 Release Notes: You can now enable sandboxing for shell script build phases using the ENABLE_USER_SCRIPT_SANDBOXING build setting. Sandboxing blocks access to files inside the source root of the project as well as the Derived Data directory unless you list those files as inputs or outputs. When enabled, the build fails with a sandbox violation if a script phase attempts to read from or write to an undeclared dependency, preventing incorrect builds. Thanks to Daniel Jalket's Blog Post: Xcode Build Script Sandboxing - https://indiestack.com/2023/06/xcode-build-script-sandboxing/

From the WWDC Q&A (Apple) answered: Simply do not use a CloudKit container identifier when configuring the SwiftData stack. There is currently a bug with this, so please file a feedback report. I expect this will be fixed in the next Beta Release of Xcode.