Hi,
I'm experiencing an issue where all RealityView content disappears when the user selects "Lock In Place" from the window management menu (long press on close button). "Follow Me" works correctly and this happens in Testflight builds only not reproducible when I run locally
I have reproduced this with a minimal project containing nothing but a simple red cube — no custom anchors, no app state, no dependencies.
Steps to Reproduce:
- Open an ImmersiveSpace.
- A red cube is placed 1m in front of the user via RealityView.
- Long press the X button on any floating window
Select "Lock In Place". The cube disappears immediately.
Expected: Cube remains visible after window is locked
Actual: Cube disappears.
Minimal reproducible code:
var body: some View {
RealityView { content in
let cube = ModelEntity(
mesh: .generateBox(size: 0.3),
materials: [SimpleMaterial(color: .red, isMetallic: false)]
)
cube.setPosition(SIMD3<Float>(0, 1.5, -1), relativeTo: nil)
content.add(cube)
}
}
}
Device: Apple Vision Pro
visionOS version: Vision OS 26.2 (23N301)
Xcode version: Version 26.3 (17C529)
Is this a known issue? Is there a recommended workaround to preserve RealityView content during Lock In Place transitions?
Thank you!
Hi Michael,
Thanks for confirming the behavior on the TestFlight build.
You're right that from a robustness standpoint our app already handles ImmersiveSpace dismissal gracefully, we handle the Digital Crown case and the state sync. So in that sense, no workaround is strictly needed to avoid a broken state.
However, I'd like to flag that the graceful-dismissal path isn't really the concern here. My expectation for "Lock In Place" is that it behaves like it does for regular windows, the window gets pinned to a world anchor and stays put, while the rest of the scene (including the ImmersiveSpace and its content) continues as-is. "Follow Me" already works this way and doesn't tear down the ImmersiveSpace, so the asymmetry feels unintentional. The fact that it only reproduces on TestFlight/Release builds and not on Debug also suggests this isn't by design.
So while I agree the app-side handling is fine, I'd push back that the ImmersiveSpace being dismissed as a side effect of locking a window is itself the bug, not just something to handle. Could you confirm whether the dismissal behavior is intended, or whether FB22290781 will stay open as an OS-level issue? I'd like to make sure it doesn't get closed as "works as designed," because from a user-experience perspective, Lock In Place tearing down immersive content is surprising and inconsistent with Follow Me.
Happy to provide anything else that would help the investigation.
Thanks,
Kunal
