@jkdufair oh wow! I have photo widgets in both rooms now that you mention it. I will try removing them and see if I can still trigger this issue.

@Vision Pro Engineer The only solution is to restart the headset. I've heard from dozens of people in my community that they are seeing the exact same behavior. Not always triggered by room changes, but the same issue where they can't move or translate an entity using Manipulation Component. I don't think the room changes are the only trigger for this issue. But it is the best for me to reproduce this.

@Vision Pro Engineer This has happened on every version visionOS 26 released, including the shipping version. It is still happening. As I showed in the video: I put the headset on in room A and use manipulation IN ANY APP (not just mine) Then I'd go to room B and use manipulation IN ANY APP (not just mine) When I return to room A, manipulation will break. I will be unable to translate–or move–the entity. Rotation and scaling will still work, but the entity will be stuck in place.

Thanks for the update. It is good know this tool has a future.

Thanks, that's good to know. Hopefully this can be resolved soon

Yes, I know how to combine gestures like that. But that isn't really the same thing as multiple gestures. For example Tap to toggle a value (show a popover, presentation, etc) Drag to translate an entity We can easily do that by using gestures on a RealityView. But it looks like the new GestureComponent only takes a single gesture. I'll file a feedback re: pass an array of gestures.

In the mean time as a possible work around, can you use ViewAttachmentComponent instead? The new sample Canyon Crosser has several examples of using this new component. I have already switched all my attachments to ViewAttachmentComponent and can confirm the behavior is the same as regular RealityView attachments. I'll work on a feedback when I have a chance.

I ran into this several times during Beta 1, but not yet on Beta 2. When it happened to me, it impacted anything using manipulation across visionOS, not just the app I'm working on. I also happened in Safari and QuickLook. Restarting was the only solution I found. If it happens again on Beta 2, I'll file a feedback. You might consider doing the same thing

This has absolutely nothing to do with my question.

@Vision Pro Engineer thanks for the response. If I understand correctly this doesn't work because the AnchorEntity is a point on a plane, not a the plane itself. Is that correct? Is it possible to use an AnchorEntity (with SpatialTrackingSession) to get the plane/bounds/rect of the floor that visionOS detected?

it's usually better to put the code that configures the SpatialTrackingSession into a class instead of an @State property on your view Sure, I would do that in most apps. This is just an example where I was trying to keep everything in one file. Do you have any details on the why it is better to place SpatialTrackingSession in an observable class instead of state on a view? Several of the WWDC sessions and examples store the session in the view and I was using them as a starting point.

pushWindow isn't supported for volumes. This definitely worked during the visionOS 2 betas, but now it's not supported? There is nothing in the pushWindow documentation that indicated that this is not supported. Apple should update that documentation to make this clear.

Very interesting. I didn't realize that User Defaults contained anything other than the data I write to it. I always thought it was essentially an empty plist where I could add key:value pairs. I'll add the manifest for now. Maybe it's time to reconsider using UserDefaults at all. I suppose I could get the same behavior from creating a local JSON file and saving the settings there.