Skip to main content
LeonVRLab
Up and Coming
Nov 3, 2026 10:17 AM UTC
Question

HMS Shared Mode: issues loading OBB after update to OS version 2.9. Any solutions?

After updating one of our Quest 3s headsets to OS version 2.9 (from a way older version as this headset had not seen updates in recent months) apps using an OBB file will not load. I.e. the app starts, apparently without error, but won't load the OBB file so is stuck on loading (showing the loading indicator, but background audio is playing). This happens with apps shared directly with the HMS org, but also with apps installed from the store. We also got a report from a customer that has exactly the same problem. And a content development company contacted us on Friday to notify us of this issue. Is there a solution? A workaround? This is a problem in production so extremely urgent.
 

10 replies

Maccyb123
Maccyb123
Expert Contributor
Nov 3, 2026 10:32 AM UTC

This can happen if you're missing a lot of previous updates. Try this as a fix. It might work🤞🤞 Let's know how you get on and good luck.

  • Verify and Re-copy OBB Directories: Ensure the OBB folders didn't get orphaned during the multi-version jump. The files must reside in Main Storage > Android > obb > [exact.package.name] > main_[version].[package.name].obb. If they were left in a root or legacy cache folder, the new OS security blocks apps from reading them.
  • ​Use a Modern Local File Manager: Because standard Windows file transfer or older Android explorers can trip over scoped storage permissions on recent OS versions, use a headset-native file manager (like CX File Explorer sideloaded or managed via SideQuest) to verify that the system actually recognizes the OBB directory structure.
  • ​Reinstall the APK Fresh: Sometimes upgrading past an older base version corrupts the registry link between the installed APK and its data container. Completely uninstalling the app, letting a fresh APK recreate its native directory structure, and then re-adding the OBB file can force the system to register the assets correctly.
  • ​Check Developer Permissions: If these are sideloaded or custom apps, verify that Developer Mode hasn't been toggled off or reset during the massive firmware update cycle, as security updates frequently revert developer flags and block unsigned asset loading.

 

Maccyb
LeonVRLabAuthor
Up and Coming
Nov 3, 2026 11:43 AM UTC

What I tested so far:

  • After the update to 2.9 → problem as described (this was my trigger to post)
  • Reinstalling (remove and install) the app → same problem; another app without obb worked just fine
  • Factory reset, HMS Shared Mode, exact same settings, all apps reinstalled automatically → same problem
  • Multiple Quest 3’s running 2.9 but with ArborXR → no problem
  • Developer Quest 3 without HMS but running 2.9 → no problem
  • Factory reset, HMS Individual Mode (though I do not know of any customers using this) → same problem
  • OBB file installed correctly; nothing suspicious showing up in the logs

I still want to test connecting the same headset to ArborXR (third-party MDM enrollment) to verify what we saw on other devices running ArborXR, i.e. that they work well.

    st_hilton
    New Participant
    Nov 3, 2026 10:57 AM UTC

    we have the same issue - its quest 3 and 3S affected  - quest 2 is unaffected

     

    st_hilton
    New Participant
    Nov 3, 2026 10:58 AM UTC

    was working fine until recenetly on the quest 3 and 3S  - seems to be the latest update with OBB files 

     

    Maccyb123
    Maccyb123
    Expert Contributor
    Nov 3, 2026 12:32 PM UTC

    🤞🤞🤞🤞 :) 

    Maccyb
    LeonVRLabAuthor
    Up and Coming
    Nov 3, 2026 4:12 PM UTC

    Initial Meta feedback:

     

    On managed Quest 3 devices running Horizon OS v209, Unity apps hang on the loading screen due to an inability to open Store-delivered OBB files. The error 'ApkAddCentralDirectory: Unable to open' is logged for the main OBB. Investigation reveals that the OBB and asset files in the app's Android/obb folder are owned by com.oculus.ocms (uid 10030) instead of the app's own uid, preventing access. This issue is a regression from v207, where the same managed device preset and app build work correctly. Unmanaged Quest 3 devices on v209 are unaffected, with OBB files correctly owned by the app's uid. Reinstalling the app from the Store does not resolve the issue, suggesting the problem is related to how v208/v209 handles OBB file ownership during Store installation on managed (MDM-enrolled) devices.

    Terms & ConditionsAccessibility statement