arkit-visionos-developer

To use ARKit on visionOS, you must run your experience in a Full Space because ARKit data is unavailable in a Shared Space. Add NSWorldSensingUsageDescription and NSHandsTrackingUsageDescription to Info.plist as needed, then create a long-lived ARKitSession and request authorization for provider-required data types before running the session.

ARKitSession data providers on visionOS include world tracking, plane detection, hand tracking, and scene reconstruction. You select the specific providers needed for your immersive experience, request their required authorizations, and run them concurrently within the ARKitSession to observe anchorUpdates streams.

Handle ARKit authorization in visionOS by adding NSWorldSensingUsageDescription and NSHandsTrackingUsageDescription to Info.plist, requesting authorization for provider-required data types before running the ARKitSession, and observing ARKitSession.events for authorization changes and errors.

Bridge ARKit anchors to RealityKit in visionOS by observing the ARKitSession anchorUpdates stream, mapping the anchor data to RealityKit entities, and keeping the state in a model layer to render anchors and content within your immersive space.

ARKit data is unavailable in a visionOS Shared Space because world tracking, plane detection, hand tracking, and scene reconstruction require a Full Space environment. You must ensure your immersive experience runs in a Full Space to access ARKitSession data providers and anchor updates.

Manage the ARKitSession lifecycle on visionOS by stopping the session and canceling tasks when leaving the immersive space. During the session, observe ARKitSession.events for authorization changes and errors to properly handle data provider flow and debug your ARKit implementation.