[BUG] QRCode detection doesn't work on organization-managed Quest 3

[Softelectro]

Unity version

6000.0.60

Where does the issue occur?

• In Unity Editor
• In Quest builds

Description

We are currently developing an industrial application in which we would like to integrate QR code detection in order to attach descriptions to various objects.

QR code detection works perfectly on a unmanaged Meta Quest 3 headset. However, when the headsets are configured in Shared Mode and managed through Meta Horizon Management, QR code detection does not work at all.

Steps to reproduce

I compiled the project using Unity 6000.0 and installed it on several headsets to test the QRCodeDetection scene.

In this scene, the values QRCodeTrackingSupported, HasPermission, and QRCodeTrackingEnabled are active.

• On the unmanaged headsets, visual markers appear correctly around the detected QR codes.
• On the managed headsets, no visual markers appear.

Logs

no relevant error or/and warning detected on managed headset

Additional info

On the managed headsets, I installed the application in two different ways:

• directly from Unity (Build And Run)
• via the Meta for Work interface
  In both cases, the result is the same.

Additionally, on the managed headset, the other scenes in the application work normally.

Managed headsets have OS : V85
Unmanaged headsets have OS : V83.1034 and V2.1

All tests have been done with the experimental feature disable.

[felixweilbach]

Are unmanaged devices running on V85 or V83?
What is meant with V2.1?

These samples QR Code Tracking should work on v83 OS. There was a change in the internal API from v81 to v83 which means these samples QR Code Tracking wouldn't work on v81. But as you are saying the managed devices have v85 as well I would expect it to work. The OpenXR API that needs to be supported on the device for QR Code Tracking is named XR_EXT_spatial_entity and XR_EXT_spatial_marker_tracking. Do the samples work on a unmanaged v83 and v85 device?

[Softelectro]

Are unmanaged devices running on V85 or V83?
What is meant with V2.1?

One of the unmanaged Quest 3 device is running on OS V2.1 Release notes for Meta Quest
The other unmanaged Quest 3 device is running on OS V83.1034

These samples QR Code Tracking should work on v83 OS. There was a change in the internal API from v81 to v83 which means these samples QR Code Tracking wouldn't work on v81. But as you are saying the managed devices have v85 as well I would expect it to work. The OpenXR API that needs to be supported on the device for QR Code Tracking is named XR_EXT_spatial_entity and XR_EXT_spatial_marker_tracking. Do the samples work on a unmanaged v83 and v85 device?

This github project and my application work correctly on both unmanaged devices.
So, one of the main differences between the devices lies in whether they are managed through Meta Horizon Management or not.

If it helps with the diagnosis, I can retrieve the webcam texture via PassthroughCameraAccess and analyze it with ZXing on all devices.

Thanks in advance for your support

[felixweilbach]

I've been told that for managed devices permissions could be the problem. Could you try to give the application the spatial data permission and check if its working with it?

[Softelectro]

I have added a small script to check permissions related to QR code tracking and camera access, and to log the results. I ran this script both in my application and in this project, on managed and unmanaged devices.

In all cases, I obtained the same output:

RequestUserPermission >> com.oculus.permission.USE_SCENE : True
RequestUserPermission >> com.oculus.permission.USE_ANCHOR_API : True
RequestUserPermission >> com.oculus.permission.USE_STAGE : False
RequestUserPermission >> com.oculus.permission.PASSTHROUGH : False
RequestUserPermission >> horizonos.permission.USE_CAMERA : False
RequestUserPermission >> horizonos.permission.HEADSET_CAMERA : True

Furthermore, in the app’s authorization settings, both spatial data and headset camera permissions are enabled, which is consistent with the logged results.

For reference, the managed devices are configured in Shared Mode, which restricts user capabilities such as accessing full settings, Store App installing, .... Could there be any firmware-level parameters or policies in Shared Mode that disable or limit this type of tracking for safety or confidentiality?