Have you gotten any of this stuff to work for you? I started experimenting with accepting drops from outside my app, and it's been brick wall after brick wall.

Discovered using a negative spacing in the VStack+HStack technique that matches the relative shape inset works well enough: HStack(spacing: -3) {                     VStack(spacing: -3) {                         ContainerRelativeShape()                             .inset(by: 3)                             .fill(.yellow)                         ContainerRelativeShape()                             .inset(by: 3)                             .fill(.yellow)                     }                     VStack(spacing: -3) {                         ContainerRelativeShape()                             .inset(by: 3)                             .fill(.yellow)                         ContainerRelativeShape()                             .inset(by: 3)                             .fill(.yellow)                     }                 }

I've had problems where the project had types that matched SwiftUI types and the preview would never really finish loading. Things like "Coordinator" "View" or "Button", despite being in the namespace of your project and not the swiftUI namespace, seem to confuse the preview compiler.

Hey, me too! My guess is it's a passing validation bug with the beta. Could be worth submitting a feedback for, though.

Does this impact all AnchorEntities created with an ARAnchor? What other behaviors have you seen with this?

Sending a single image works, so I’m guessing it’s an undocumented or overlooked limitation.

Well, I'm a dork. The thing that I expected to see in my ARWorldMap was an AnchorEntity, not an ARAnchor. AnchorEntities, while containing an ARAnchor internally, may not actually be getting persisted to the ARWorldMap? It's something that I will be investigating more tonight, but I wanted to add this additional information.

Oh man, this could be almost anything. Are you using storyboards or Xib files? Are all your IBOutlets and IBActions connected? Does your app run if you remove some components, or try rendering with zero rows? Is your UITableViewCell properly registered on the table before you try to dequeue it?

Yeah, this is a known bug where sidebars styling is not fully supported in SwiftUI catalyst. See this sample project by STS that has work around: https://github.com/steventroughtonsmith/CatalystSwiftUISidebar?ref=swiftobc.com

Update: It appears that the main reason I'm getting this error is because one of my dependencies is failing to clone. This dependency is located in a private repository also hosted on GitHub, and I've granted authorization to this additional repo. Could this be because Xcode-Cloud is trying to look in keychain for my normal git authentication info (username and token), but it's not available on the host?