We have the same issue. Can someone answer this?

More information. I just had ARKit stay in .pause and while await openImmersiveSpace(id: "OurSpace") returned .opened: there were no graphics visible. I took the AVP off, waited 5 second, put it back on, entered my passcode and our App resumed with graphics in place and ARKit in .running As such I believe the problem might not be ARKit failing to start running but rather Immersive Space saying it is open but it isn't. Either is a problem of course but ImmersiveSpace saying it is open but actually isn't is a bigger problem as it is hard to detect. I will create FB but a minimal sample is going to be difficult. I did try updating to 1.2 beta 4 but I still see the issue. I would say once out of 30 times. Feels like a race condition but I have no idea what I might be able to change to alleviate the issue.

After on the load of the Immersive View

I will see if the Object Placement Sample Project exhibits the same issue. One question we have is what order should the monitoring tasks be kicked off? We have a Task that does for await event in arkitSession.events We have another that does for await anchorUpdate in worldTracking.anchorUpdates These are started before ARKitSession.run() Perhaps these should be started after??

Sure thing, thanks! I created this issue FB13713944 which includes a couple other issues which, unfortunately, are a bit more troublesome. We can internally track removed anchors and ignore them.

Any idea when this will be added? I've paid $4700 for a great device but it is useless unless I can render with Metal in mixed immersion. Should I return the device and wait?

Still broken, thanks for the work around.