Developer Hub - Build Upload Failed - PROCESSING ERROR, API ERROR, ECONNRESET
I am trying to upload a new build of my game through the Meta Quest Developer Hub. I am uploading it to a private release channel for alpha testing. I am getting a number of errors after multiple attempts with a different error each time. I get upload failed errors sometimes showing Processing Error please try again later, API error, or ECONNRESET Network error. I've tried looking at the log files but Im not experienced enough to know what to do. It is strange because I havent had these issues before, I've uploaded multiple builds with the most recent being a little over a week ago. I am using unity 2021, the most recent version of MQDH, and am attempting to upload an apk and single OBB file (2.2 GB). I have tried copying the adb files associated with my unity project and pasting them into the "Meta Quest Developer\resources\bin" file path. I've also tried changing the MQDH ADB file path to match the unity version in the file path "C:\Program Files\Unity\Hub\Editor\2021.3.15f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools" Nothing seems to work and its more strange that different errors pop up instead of a single consistent error. I've made sure my manifest file is correct and am increasing the version and bundle code with each build, and done other things like make sure MQDH is able to pass through my firewall, tried making a fresh release channel. I also sometimes receive this error when attempting to open MQDH and I have to uninstall it and reinstall just to get it to reopen. Am i doing something completely wrong? Here are two of the errors, with the other one saying PROCESSING_ERROR please try again later. I can send log files if needed. Thank you for any help in advance!
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.Meta Quest Developer Hub - Change FFR, GPU & CPU Level and refresh rate
Hi there! I really enjoy using the Developer Hub and have a few requests for features which would be beneficial to us developers. I am currently using these as custom commands, but it would be much more convenient to have dedicated controls in "Device Actions" for them. The features are as follows: Change Dynamic FFR to Static and explicitly control its level Change Dynamic CPU & GPU level to Static and explicitly control their level Change headset refresh rate between 72, 90 and 120 Hz These settings would me the MQDH an ultimate developers tool, so in advance thanks for considering these ideas. Cheers, FilipI don't manage to submitt my game to the Oculus Rift store
Hi,i would release an app on the rift store but when i try to upload it via the developer hub i receive an error "API_ERROR" (i will attach the screen). In my Unity3d project i use the XR toolkit and i build it for pc for oculus (i will attach a screen of the build settings). Can you please help me?
NEW Developer, how do I upload a build?
Hi everyone, I'm a new developer. I'm uploading my SaaS network...think Netflix and I'm almost at the end and ready to submit, but the submit button is grayed out and when I hover over it is says, my first submission needs to have a binary attached!! what is a binary and how do I get one? How Do I upload a build? How Do I sign my app? Can someone help me?macOS MQDH 4.4.1 ships with x86_64 adb
Title says it all. Current (as of this writing) revision of MQDH for macOS ships with adb built only for x86 when it should probably be a universal build like the rest of the app. Evidence from the CLI: my-fancy-prompt$ pwd /Applications/Meta Quest Developer Hub.app/Contents/Resources/bin my-fancy-prompt$ ls Casting.app/ NOTICE.txt aapt2 InputForwardingService.apk OculusDeveloperHubService adb my-fancy-prompt$ file adb adb: Mach-O 64-bit executable x86_64 This drove me bonkers for a goot bit trying to get my Quest 3 connected to the developer hub. My Ventura-based Mac does not have Rosetta installed on it as it's actually a clean install and I avoid Rosetta unless it's absolutely necessary. When attempting to connect my Q3 to MQDH it went through the whole process and ultimatley did nothing with zero feedback, error or otherwise. There was no indication that adb failed to launch because of the "Bad CPU type" of the binary. I grabbed the platform-tools from android.com and those are indeed a universal build as they should be. I pointed MQDH at that adb and it's good for now. Please consider packaging a universal arch adb with a near-future release of MQDH for macos. Cheers!
Help! I set up test users, but in companion app it requires a confirmation code sent via email
Hi, I set up multiple test accounts from my Meta organization and am trying to assign them to different Quest headsets. However, when trying to log in either on the companion app or headset I'm asked for a confirmation code. But because these test apps don't use real email addresses I can't access the confirmation codes, making the headsets unusable. What's the solution please?
Developer Mode Quest Pro
Hey 🙂 I bought a Meta Quest Pro because I would like to develop some small projects for these glasses. I'm also very excited about the device, but I've already encountered a more or (I hope) less big problem pretty quickly and hope you can help me here. The issue is that I can't get the glasses properly into Developer Mode and thus connected to my PC or the app. I have tried many different ways, downloaded software updates, used different cables, worked with the app and dev hub, run power cycles and rebooted all devices, but I have not been able to solve the problem. I always get to the step where I have to allow debugging via USB on the headset. I remember this from the Quest, where it worked fine, but on the Pro this prompt just doesn't appear for me to give my permission. After some searching, I came across a thread here that also describes exactly this problem and where in the further course, quite current is written that there is a solution for it...can you help me find this solution? I have already looked around a bit in the forums as I said and ended up here: https://communityforums.atmeta.com/t5/Get-Help/Quest-Pro-Developer-Mode/m-p/994506 I had then written to the support chat, as well as the mod from the forum entry, both of which unfortunately could not help me directly, but forwarded me to the PM of the meta support and they forwarded me to the consumer support and this page... i would really appreciate if someone can help me... It also works really everything great, except the last step "allow access". When I connect the headset via cable to the pc, there is a nice sound, but no window to confirm. Thank you very much and with kind regards Karo
