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
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.
Removing Users from Release Channel
My org is hoping to do a user test with a demo for our game. For the test, we'd want to add users to a release channel, then after the demo period, remove the game from their device. However, it seems that removing a user from the test channel just means that they can't get new builds. Is there a better way to do this? Or how can we prevent users from playing after the demo period?
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?
Meta Quest Developer Hub Network Error
When trying to upload an app via 'App Distribution' I receive this error message: Upload Failed The build you were trying to upload has failed. Error NETWORK_ERROR getaddrinfo ENOTFOUND graph.oculus.com My internet isn't amazing but should be able to get the job done. Any ideas?Unable to add new member to Developer Hub
Hello, For about 4 days, I have been trying to add a new member to our developer hub for them to assist with keycodes and release channel access. This person made a meta account and a meta developer account, but they do not possess a headset. I made sure they were logged into their account. When I enter in their email or username, it is unable to locate them. I confirmed that the spelling was correct and escalated this to my developer relations coordinator. If you have any resources on a fix for this, I would appreciate it. Thank you!
