Tried more things. I observe that xcodebuild is still attempting to execute metal from here: /Applications/Xcode-26.0.0-Beta.2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/metal -c This complains the toolchain does not exist. How can I point this to a different metal install? Xcode shows that I have two metal toolchains installed. 17.0 (17A5241l) and 17.0 (17A5241n). Xcode is able to build my code via the UI, but not via command line when executed by Fastlane.

I'm trying to build with fastlane and none of the shell snippets here are helping with that :\ . Also Xcode cloud can't build either.

It’s one of the great ironies that the slower Xcode cloud is the more it profits from users. So is there a true business reason to make it faster? This paradox is one of the reasons I probably won’t move off the free tier. (Which for all I know is slower by default).

This should be fixed now but builds will still fail if the use the metal toolchain.

AppStoreConnect is no longer accepting builds with Xcode 26 Beta1. Beta2 not available.

Maybe Apple does not want applications created completely with AI code gen tools on their store front. also, check your tool provider for documentation like the following: https://thunkable.com/blog/three-ways-to-avoid-rejection-from-app-stores

Still broken with the new release, though Xcode Cloud is still not showing that the "latest" is using the new Xcode...

You can achieve something like this in an Immersive scene, but you will not be able to interact with other apps while your scene is active.

-moved to threaded reply-

@DTS Engineer It looks like the system, when invoking an OpenIntent, knows the input target of the intent, and knows the "ID" of the "target". In my case it's the special FileEntityIdentifier Using the code on the documentation will not work because func entities(for identifiers: [FilesEntity.ID]) async throws -> [FilesEntity] { [] } is not converting the system provided FileEntityIdentifier to a "FilesEntity", so there's no target to invoke the OpenIntent with. Here's the fix for that: func entities(for identifiers: [FilesEntity.ID]) async throws -> [FilesEntity] { identifiers.map { FilesEntity( id: $0, creationDate: nil, fileModificationDate: nil ) } } I've resolved this and ALSO provided the OpenIntent using the "AppShortcutsProvider". Otherwise it does not appear in shortcuts. The good news: When invoked from the provided shortcuts area it works! I am not able to add it to a custom-shortcut as an action, though, I can only invoke it directly from the provided shortcuts card. Questions Now that I know the OpenIntent works, how can I invoke it with Siri? It seems any phase with "open" in it still just opens my app. Does the OS provide a "file" to Siri anywhere? How can I know this? I've tried a quick looked file in the Files app and phrases like "Open this in ".

The documentation indicates that you should use performDrop to load from the item provider. enter and exit is only to indicate that a drag operation is targeting a view.

I think it will be called on re-build if the identity of the view is the same, so SwiftUI considers them the ”same”

:facepalm: I needed to call .compositingGroup() before applying the .layerEffect. I'm gonna go lie down.

Bump? Any framework engineers know how to use this stuff?

I think you need to explore “deep linking” solutions in your app. That’s the concept of entering the application at a screen lower than the first view. I chose to solve it with a singleton but I think there’s a new @Dependency you can use these days.