Skip to main content
MKTrickpark2
New Participant
February 20, 2026
Question

Spatial Anchors not working, when app is deployed via MHMS

Hello,

we are currently depveloping an AR app that relies on spatial anchors. We intend to deploy it via MHMS in the future.

For the development we are using Unity and are currently testing the deployment. We tried it a few months ago and there were some crucial errors regarding spatial anchors. The problem is, when the app is deployed via MHMS the spatial anchor feature doesn't seem to work. Coming back to it now, the errors still persist.

When saving a spatial anchor, the system always returns a platform error and the anchor cannot be loaded or saved.

This ONLY occurs when deploying over MHMS. Deploying from Unity directly or sideloading the app always works perfectly fine. It also is not Unity or OpenXR version dependent as there have been multiple updates of both since we tried it first. When the headset is managed via MHMS, no option works.

Is there any way to handle this problem or any fix for this in sight?

Thanks!

 

 

1 reply

MKTrickpark
New Participant
February 23, 2026

So - the solution seemed to be, that you need to officially register the app in the store and upload an apk.

It is not publicly released so far, and you can still distribute it via MHMS. It just get's more permissions, when there is an official app entry.

Edit - It came back but we finally solved it for real. The store bit was correct but I guess for a Meta Quest Store app, the apk has to be on the Production channel or at least RC Channel. We switched to a privately distributed app. You have to unlock your company being able to create a private app first. Then upload the app to the "Business"(Production) Channel.

What we did as well was to add the "Meta Platform SDK" to the unity project. It will add an OculusPlatformSettings.asset to your project. There you can enter the AppID from your developer hub. Then in your app startup youe need do call 

Oculus.Platform.Core.AsyncInitialize(PlatformSettings.AppID).OnComplete(OnComplete);

somewhere in your code. After connection the app from the Development Hub into the MHMS via invite, everything worked. This is just a rough write up but I hope it helps.

Terms & ConditionsAccessibility statement