[visionOS] 10s+ freeze in ArcGISView constructor on Apple Vision Pro hardware (Unity 6 / v2.2.0)

yhikishima

Hi,

I am reporting a performance issue with ArcGIS Maps SDK for Unity v2.2.0 on Apple Vision Pro hardware.

The application freezes for more than 10 seconds during the initialization. The bottleneck is the following line in ArcGISMapComponent.cs:

view = new ArcGISView(ArcGISGameEngineType.Unity, GameEngine.MapView.ArcGISGlobeModel.Ellipsoid);

The constructor blocks the main thread. This occurs ONLY on the actual visionOS device.

Measured times for "new ArcGISView" execution:

• Unity Editor (macOS): 0.02s
• iOS Device: 0.02s
• visionOS Simulator: 0.02s
• Apple Vision Pro Hardware: 10.00s - 15.00s

Findings:

• I tested the official xr_sample_project and it also takes about 7 seconds to initialize on AVP hardware. URL: https://github.com/Esri/arcgis-maps-sdk-unity-samples/tree/main/xr_sample_project
• Tested on Unity 6 (6000.3.0f1) with URP.

Hardware Details:

• Device: Apple Vision Pro (MQL83J/A)
• OS Version: visionOS 26.3
• Serial Number: YVXCWGN0GP

Development Environment:

• SDK: ArcGIS Maps SDK for Unity v2.2.0
• Unity: 6000.0.39f1

Questions:

1. Is this 10-second delay a known behavior of the native runtime on visionOS hardware?
2. Is there any way to initialize ArcGISView without blocking the main thread?

Thank you.

yhikishima

I have a further update regarding the official sample project (xr_sample_project).

I tested the official sample on Meta Quest 2 (Android), and the initialization was instantaneous:

Meta Quest 2: 0.02s
Apple Vision Pro (Hardware): 7.00s - 10.00s
This comparison proves that even with the same official sample code, the massive delay is not caused by the complexity of XR rendering itself, but is a visionOS-specific hardware/runtime issue.

I hope this helps your engineering team investigate why the visionOS native runtime behaves so differently from Android, iOS, and the Simulator.

Thank you.