MQDH - Multi OBB package upload
Hello! I'm looking for some help/clarification for the Meta Quest Developer Hub's build deployment feature. The Documentation Page covers the basics of using MQDH to upload an application to the Quest, which seems to work fine as long as the app only requires a single OBB file. Unfortunately our Unreal Engine game has recently exceeded the 4gb limit and we've had to split the package into multiple OBBs. When I install the app through MQDH the app fails to launch. If I then manually push the patch OBB (like the install script Unreal generates does) the app will launch correctly. This indicates to me that MQDH will only grab the main OBB file (i.e. `main.1.com.___.obb`) Does anyone know how to get MQDH to install all OBBs present in the same folder as the APK file? Do I need to follow any specific naming conventions or processes? I'd like to continue using MQDH as for some reason it seems that installing the Android commandline tools themselves has been... troublesome for some of our remote team members.
quest 3 newbie dev connect issue mistakes
Hi! So, day 1 and the Mrs has setup the quest, I've also got my Dev account but as a visitor / guest / additional profile. I'm trying to connect to mqdh but it won't connect. The instructions say "make sure you are logged in with the same account" and mine is the active profile. Do I need to be the admin user? (I.e. wipe and restart)? Bonus question, if we wipe and restart, will the game sharing only work from the admin account and any games my wife has already bought only work under her profile?
MQDH / Developer Dashboard - Server Error - API Error - No Tests Ran on Build
I am having a number of issues with Meta Quest Developer Hub and Developer Dashboard. For the past three days I have been unable to upload a build through MQDH due to a few different errors. I am using the latest version of MQDH. When uploading a build I either get an API_ERROR, ECONNRESET error, or PROCESSING_ERROR "please try again later". Looking at the logs it said server error, attempting to try again, and does this over and over. It doesnt seem to be an issue with my actual build, or manifest or anything that I am able to solve on my end. Have tried reinstalling MQDH or switching the adb file path to match unity. After repeated attempts failing through MQDH I decided to try using the OVR Platform Utility Tool. I was able to upload my .apk with an OBB file, though I received multiple server errors in the process. After about and hour and a half the upload process finally succeeded through the server errors and I am able to see my new build in developer dashboard inside a new release channel. My new issue is that the new build uploaded has not yet gone through the automated testing. I uploaded the build over 16 hours ago. Dashboard still says "No test runs were found to be associated with this build." Because of this I cant actually install and play this new build. And with both MQDH and Dashboard causing issues I am at a complete standstill on my project. Is there some sort of server issue on Metas side that is causing this? Any assistance is greatly appreciatted
Unable to add additional account to quest pro
Not able to connect the quest pro to neither mobile app nor quest developer hub. All the required settings are enabled including developer mode and the device gets recognised on the Developer hub but doesn't connect . The Only issue that I see is two different accounts are logged into the quest pro and quest developer hub...but both are developer accounts. And previously in quest and quest2 there was an option to add additional accounts. I don't see that option in quest pro. Arbor xr (If that matters) is installed on this quest pro for device management but I can exit out of it and use the device as a regular one.