Still cannot use built in mic for casting on MQDH... Extremely obnoxious oversight...
I just don't understand. Meta is advertising this as the best way to cast gameplay and yet to this day there isn't even an option to turn on the mic. You can hear the mic when you record, but not when you cast? Make it make sense. The fact that this has been a common complaint for a couple years now just makes this all the more frustrating. If /casting can do it, what's stopping Dev Hub from doing it? Can anyone here think of a legitimate and logical reason for MQDH to lack this basic feature?
MQDH / Continue in your Browser
Hello! I am unable to login to the MQDH desktop application. I already tried the "WIN+R - google.com"-Solution, but it did not work. I tried Edge and Chrome as default browsers. I just see a little flash in the MQDH after i click the blue Start-as-Button. But it stays at "Continue in your browser" without an error message. EDIT: I am on windows 10. Hoping for some ideas Thanks, StefanMeta Developer hub stuck in Login loop
Good morning, i am looking into getting into Meta quest 3 development. However i am having issues with the developer hub application. I have my developer account set up, and everything seems to be good. However what happens is, the app will redirect me to a browser to login, when i login it then redirects me back to the app, however when it refreshes it simply refreshes the "Continue in browser page" Not logging in. It was suspected that this may be caused by my facebook acount being linked to my meta account. I have disconnected and reinstalled the hub, however this issue persists. Anyone have any issue with this and can advise?
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!
