OBB file ownership issue on managed Quest 3 devices with Horizon OS v209
Investigation titles and descriptions are summarized by AI from Meta based on submissions from developers
Investigating
10 similar submissions
Created 14 days ago
12
Add your submission
Subscribe
Suggest an edit
Copy link
Investigation summary
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.
Get answers from the community
If you're having trouble, find answers to your questions from Meta Quest users around the world.
Go to community forum