Title: OpenXR Runtime Missing on ML2 → Plane Detection & Spatial Mapping Not Working (Only Stub Runtime Loaded)
Body:
Hi everyone,
We are currently unable to get plane detection working on Magic Leap 2 when using Unity OpenXR. The app builds and runs, but no planes or spatial mapping data are ever returned, and the system appears to fall back to a stub OpenXR runtime instead of the actual Magic Leap OpenXR runtime.
Environment
-
Unity Editor: 6000.1.17f
-
Magic Leap 2 OS: 1.12.0
-
MLSDK: 2.6.0-pre.R15
-
Unity XR Plugin: OpenXR + MagicLeap OpenXR Features enabled
Problem
When ARPlaneManager / meshing subsystems attempt to start, the following log appears repeatedly:
OpenXR-Loader:
getActiveRuntimeCursor: Querying URI: content://org.khronos.openxr.runtime_broker/openxr/1/abi/x86_64/runtimes/active
Failed to find provider info for org.khronos.openxr.runtime_broker
Got runtime: package: , so filename: libopenxr_runtime.magicleap.so, native lib dir: /system/lib64, has functions: no
Later:
Runtime Name: MAGICLEAP
Runtime Version: 1.0.7
Runtime extensions enabled: (26)
This strongly suggests the headset is initializing the OpenXR loader, but the actual runtime package (com.magicleap.openxr) is missing, so the loader falls back to /system/lib64/libopenxr_runtime.magicleap.so, which contains no spatial mapping or plane detection functionality.
Observed behavior
-
ARPlaneManager.trackablesChangedfires with only 1-2 planes, then only updates -
No plane meshes are ever visualized
-
Meshing providers fail with
RuntimeFailure -
Anchors and Scene Understanding calls also fail
What we have tried so far
-
Verified Unity OpenXR settings + MagicLeap feature configuration
-
Confirmed AR Plane Manager & AR Camera setup is correct
-
Reinstalled the OS
-
Checked package list via
adb shell pm list packages | grep -i openxr -
Only found:
com.magicleap.openxr_runtime_broker→ missing:
com.magicleap.openxr -
Reinstalled MLSDK, Unity packages, and rebuilt project
Key Question
Should com.magicleap.openxr be present as a system package on ML2 OS 1.12.0?
If yes — this seems like an OS-side installation issue, not a Unity configuration issue.
Before we proceed with a full factory reset, we want to confirm this diagnosis.
Any guidance or confirmation from Magic Leap engineers or anyone who experienced similar behavior would be greatly appreciated.
Thanks!