Taking your solution for wall colliders and putting that up as a HUD-like entity could work. I'm not convinced that this is needed here, though, when there's a video entity that could easily be tapped/pinched on.

Ah you added the secret sauce! I'm going to follow your example from now on. 😄 Anyway, thanks for the reassurance that all our feedbacks haven't been filed in vain.

Thank you, glad to hear it! I never received any response to my visionOS related bug reports, so it's good to know that Apple are reacting to our feedback.

After fixing up all attachments closures, I can build in Xcode 15 beta 8 and don't get that error, sorry.

You're welcome! When you say, you update the attachment, I assume this means RealityViewAttachments doesn't change, but the respective attachment entities get added to RealityViewContent for the first time? In case another delay doesn't help, maybe it is necessary to add all attachment entities in the make closure at once and then show and hide them as needed. That would be an ugly solution, but it's all a hack anyway right now. I hope, we're going to see another beta with a fix soon.

I found a workaround for this issue which I posted in another thread.

Thanks @J0hn, box.setPosition([0, 0, 0], relativeTo: nil) indeed fixes it for me! So weird, nil meaning world space is the exact reason I didn't even try this. It's one more prove that at this point we need to try everything - although I'll always be worried that inconsistent API like this might break with the next beta.

You see the error since that API also has been renamed to originFromAnchorTransform. There is no documentation in the current beta, but you can still check out the current interface at ARKit/DeviceAnchor.

Filed this issue as FB13125516.

Filed this with sample code demonstrating the issue as FB13121010.