Quest 2 and ADB stopped working
Hello! I've been using MQDH with Quest2 for almost a year now and they used to work perfectly fine, but since a few days ago, every time I connect my Quest 2 via Link Cable, it is detected and shown as below: However, if I try to issue any command whatsoever, be it a push, install, reconnect, etc, it turns offline. This can be seen by simply opening the Meta Quest Developer Hub. It initially appears as following: But as soon as one of those commands "finishes" (they always fail), this is the screen I'm left with. I have tried issuing `adb reconnect offline`, which simply makes the device completely vanish from the devices list. Needing a reboot of the device (and a unplug/plug of the USB cable) for it to reappear. I have tried deleting the adb keys and re-authorizing; rebooting the adb server; disabling and re-enabling the developer mode; factory resetting the Quest 2; disabling Oculus Air Link; changing which adb version to use; clean reinstall of Windows; all above with no other program running on PC, to no avail. Any help would be greatly appreciated. Maybe it was something in the last update? I can't find a way to rollback and test. INFOS Headset System Version: 49068160412800150 Version: 47.0.0.282.341.428237303 Runtime Version: 47.0.0.282.341.428237138 OS Version: user-49068160412800150 No lock pattern Oculus Android App Version: 198.0.0.4.103 MQDH Version 3.1.1 ADB Version 1.0.40 4986621 OS Windows 10 Pro 22H2 Build: 19045.2486Unable to upload builds after migrating to meta account (CLI, ODH, OVRPlatform Tool)
Ever since I migrated from my FB account to a meta account, I've been unable to upload any builds from the Oculus CLI, the Unity OVR Platform Tool and ODH which is completely blocking me from upload any new builds. CLI - Attempt to login says "You're using a version thats no longer allowed ..." even though I am on the latest update. Unity OVR Platform Tool: "ERROR: Unable to fetch initial upload config", Although I CAN successfully login to the Oculus Platform Settings (note image below) Finally the ODH Isn't working either suck on "Waiting for process to begin" I am completely stuck unable to make any uploads for my development team. I've tried changing passwords and logging out and back in with no luck. Is there any way I can got back?
Cast Device and Record Video don't work in ODH 2.7.2
Is it just me or someone else also face with this ? I can do screenshot from ODH, but not Record Video and Cast Device. Here is the screen shot of error when I try to cast device using ODH, although casting over the web via https://www.oculus.com/casting still work normally. An Error Occurred... Check to see if your headset and computer are using the same network. VPN’s have been known to cause casting errors. Try switching to the same network to allow casting. Firmware build ID / build flavor in headset can cause instability in casting. This information can be found in the tooltip if you hover over the device image on the device page. Check to see if the account on the headset is the same as the logged in account in ODH. There is a known issue with secondary accounts logged into the headset that would conflict with the account that is logged into ODH. This is a rare occurrence. Please try logging out and back in from the Settings Page to refresh your session.
Oculus Developer Hub can't find headset
Hi, ODH can't find my headset.. Works with the OculusClient without any problems and detects the headset instantly.. Latest ADB is installed Deveoper mode is enabled.. In the docs, it says when connected to PC, you should get a message in headset to connect to PC.. I only get the Oculus Link (beta) message.. Anyone got a clue..
node:fs:585 Error uploading Quest build with Unity, ovr-platform-util, and ODH
This error occurs whenever I try to do an build upload. I've tried uploading from ODH, Unity and the ovr-platform-util. All generate the same error. I even just tried using ovr-platform-util with no arguments and also get the same error. For reference, - I don't have a D:/ drive (shouldn't matter) - The app was installed and run on my M:/ drive (SSD) Details below: node:fs:585 handleErrorFromBinding(ctx); ^ Error: UNKNOWN: unknown error, open 'D:\full-fbsource\arvr\js\node_modules\yargs\locales\en.json' at Object.openSync (node:fs:585:3) at Object.openSync (pkg/prelude/bootstrap.js:739:32) at Object.readFileSync (node:fs:453:35) at Object.readFileSync (pkg/prelude/bootstrap.js:1025:36) at o._readLocaleFile (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) at o.__ (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) at C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js at Object.<anonymous> (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) at C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js at a (C:\snapshot\D_Zfull-fbsource\edenfs\redirections\arvr\js\temp\build-ovr-platform-util\lib\ovr_platform_util.js) { errno: -4094, syscall: 'open', code: 'UNKNOWN', path: 'D:\\full-fbsource\\arvr\\js\\node_modules\\yargs\\locales\\en.json' }
Cannot cast from test account to ODH
Hi, Im a developer developing a multiplayer app, Id like to be able to cast from my different devices into the developer hub. I am using test accounts created using the ODH under my account organization. yet when i try to cast from my device, it says: Multiple Accounts Detected The headset you are trying to cast from is using a different account than Oculus Developer Hub. Casting requires the same account on both the ODH and the headset. Is there a way to enable casting from test accounts, or to link the test accounts to the ODH account to allow casting?
