This has absolutely nothing to do with my question.

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.

@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?

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.