ONGOING ISSUE with split binary APK and OBB uploads not loading
This is still an ongoing issue months later. I have a split binary apk and obb build that I upload using the Oculus Platform Tool. My build is about 5gb. The first scene in my game is the APK, the rest of the game is within the OBB. When I download my game from the Meta servers in my test channel, I cannot load any scene beyond the first. I cannot play my game. As a test, if I remove half of my scenes to reduce the file size it magically loads the next scene. What?! I need the full game to work. This is still an issue months later and I have ZERO issues on Steam. It's getting a bit ridiculous now since I have to push out an update soon on the Meta Quest. Through UNITY, I have tried doing an Asynchronous Scene load and a regular SceneManager load and the results are the same.Solved1.7KViews0likes1CommentOculus Developer Hub obb download
Hi, I'm currently working on porting a Unity game from Rift to Quest 2. The issue I'm facing is regarding split applications using obb files. I uploaded both the apk and the obb file via the Oculus Developer Hub. (ODH) However, when I install the game on the Quest 2 via ODH it installs the apk but does not download the obb file, even though the large file option is checkt in the settings. Now when I manually put the obb file on the Quest 2's file system the game is not able to load the obb file. After I put the obb file on the Quest 2 I have to reinstall the apk by drag and drop in the ODH in order to make it load the obb file. So I'm a bit concerned how the obb file handling is working with the store? Has anyone else experienced this issue? Am I doing something wrong with the ODH?2.7KViews0likes1CommentFirmware Version 51 OBB Correct File Location?
Since firmware version 51 I am no longer able to push OBB files to where I would usually place them e.g. /mnt/sdcard/Android/obb/packageName/. I've read this is due to Android Version 12. Does anyone know the correct location for OBB files now? Just needed to remove mnt from the path and all is well.726Views0likes0CommentsUnity Split Binary Causes APK to Not Open
I posted this in OpenXR thread, but think this is more of just a quest question. I am building my game using OpenXR for the Quest 2. Everything works in editor and plays and runs fine on PC with Link Cable connected. I tried to build the full game in one apk but that was around 3.5 GB, too big to upload with adb. I was able to get a smaller build with just my menu scene working, so I know the first scene works. When I try to build with Split Application Binary, it successfully builds, gives me a 300 mb apk which i can upload to the headset, and gives me a ~3.5GB obb file. I load both onto the headset, with the obb in the correct location. But when I try to run the apk I only see the three loading dots(the loading the shows for a couple second when opening a game) on the Oculus and the app never opens. I am unsure how to fix this issue. I tried ADB Logcat and can't seem to find any error popping up. Any Suggestions2.3KViews0likes2CommentsQuest upload : "Sorry, we encountered a problem while processing the file you uploaded." No error.
We started getting this today, uploads are repeatedly failing at the same point when it tries to fetch a previous build of an OBB: It says "Error" and stops the upload, but the ovr_platform_utility is not returning an errorlevel, so our build system does not know it failed. Any idea what causes this? Is there some other way we should detect errors from the ovr_platform_utility? fetching previous build (2 / 4) ERROR: Sorry, we encountered a problem while processing the file you uploaded. Please try again later.787Views0likes0Commentsthree dots - missing obb patch file?
I keep getting three dots when I download an update from the store. It happens when the download is a partial update, not a full reinstall. I have to uninstall and do a full re-install. Looking at adb logcat, I see that it is not finding an obb patch file: [GameActivity] Checking for file : patch.com.gamecompany.XXXX.obb UE4 : [GameActivity] which is really being resolved to : /storage/emulated/0/Android/obb/com.gamecompany.XXXX/patch.com.gamecompany.XXXX.obb UE4 : Or : /storage/emulated/0/obb/com.gamecompany.XXXX/patch.com.gamecompany.XXXX.obb UE4 : [GameActivity] ... Whoops... missing; go go go download system! What causes that? It's true that if I look at Internal Shared Storage/Android/obb/com.gamecompany.XXXX/, I do not see the obb patch file. I see the main, and the additional overflow obb which is never mentioned in the adb log.1.6KViews1like0Comments