Skip to main content
New Participant
October 5, 2025
Solved

Shared Mode via Meta Horizon Managed Services (HMS) Error: "contains Insight SDK"

Hello,

We have exactly the same problem as described here

https://communityforums.atmeta.com/discussions/dev-unity/xr-build-upload-fails-auto-update-due-to-insight-sdk-warning-unity-6000--oculus-/1338471

and here

https://communityforums.atmeta.com/discussions/dev-general/deploying-passthrough-app-in-shared-mode-without-insight-sdk-blocking-hms-horizo/1334603


We cannot deploy  APKs via HMS due to the error “Shared mode: contains Insight SDK.”
The problem exists only in shared mode not in single user mode.
Even simple demo scenes in Unity without  other SDK's cause this problem. 

Is this a Oculus XR Plugin / Open XR plugin Bug?

We would be grateful for any advice on how to solve this problem so that we can use "Horizon Managed Services" for our apps.

Regards

New Participant
October 5, 2025

We have noticed that when we switch from shared mode to single user mode and back to shared mode (and reset the Quest 3S device), the APK is installed correctly.

However, when we try to update the APK in the “Meta Managed Service,” the update is not performed due to the compatibility issue “Shared mode: contains Insight SDK.”

4 replies

HotteUltimoAuthorAnswer
New Participant
October 5, 2025

We have noticed that when we switch from shared mode to single user mode and back to shared mode (and reset the Quest 3S device), the APK is installed correctly.

However, when we try to update the APK in the “Meta Managed Service,” the update is not performed due to the compatibility issue “Shared mode: contains Insight SDK.”

Participant
November 24, 2025

This is not a solution. This is a workaround that drops you into the exact same issue the next time you try to update the application. 

Hotte_Ultimo​  Do you know if an issue/bug report was filed for this?

I am experiencing the same thing 😅 and I need deployed shared mode apps to work for a customer. 

Participant
November 24, 2025

Ok, I reached out to meta support for this. It does appear that that warning throws, and while Meta for Work shows the app as not being installed, the app gets downloaded and installed on the headset. So while it is an annoying bug it doesn't appear to block the app from being installed.

New Participant
January 7, 2026

This bug still exists - for devices in shared mode, you can remove the app entirely, causing the app to be uninstalled on all devices. Once the devices check-in and successfully remove the app. You can deploy a new app with the updated APK.

I've only had the pipeline upgrade work once, using two separate apps. I.E. v1 and v2 

With v1 still deployed, I added a SHA256 hash to it, and then deployed v2 as normal with both deployments still active. I have no been able to repeat this success in subsequent versions of the app.

While the visuals of the app change, the app still uses a prior version of the APK.