Quest Remote Desktop (macOS): login fails with null TypeError, device invisible to Meta web
Meta Quest Remote Desktop on macOS fails at login every single time with "Something went wrong. Please wait 2-5 minutes and try again." Waiting doesn't help. The failure is instant and deterministic, so it is not rate limiting despite what the message implies.
The app's own log shows the real error. The browser login succeeds and the deeplink comes back fine. The crash happens in credential verification, 275ms later:
I0807 22:24:09.961064 AppDelegate.mm:232 MainThread] Received deeplink
I0807 22:24:10.585398 LoginManager.cpp:302 LoginThread0] Verifying credentials
E0807 22:24:10.860221 LoginManager.cpp:233 LoginThread0] Login failed: TypeError: expected dynamic type 'int/double/bool/string', but had type 'null'
App version 101.0.0.1.112, build 1029758790, macOS on Apple Silicon.
There is a related null earlier in the same session:
I0807 22:23:03.527899 Roadblock.cpp:37 Received roadblock query result {"extensions":{"is_final":true},"data":{"xfb_remote_desktop_roadblock_logged_out_check":null}}
WHERE THE NULL LIKELY COMES FROM
Meta's own systems disagree about whether my Quest 3 is linked to my account. Same account, same session, no account switching.
Systems that DO see the headset:
Accounts Center, Manage accounts (mobile) — lists Meta Quest 3 under my Meta account, next to my Horizon profile and Meta Store order history
Meta Horizon mobile app, Devices — Meta Quest 3, status Connected, under "Devices you own"
Systems that DO NOT see it:
meta.com, Account, Devices — "We couldn't find any devices associated with your Meta account."
auth.meta.com/settings/my/devices/ — renders empty, nav and a Log Out link only
secure.oculus.com/my/devices/ — "Whoops, the link you followed may be broken"
Meta Store support intake, while fully logged in — "We couldn't find any devices associated with this Meta account"
Meta Quest Remote Desktop on macOS — null, login fails
Both mobile surfaces see it. No web surface does, and neither does the desktop app.
I CANNOT OPEN A SUPPORT TICKET
Because the support intake can't see my device, there is no way to file this properly. Entering my serial returns "Support isn't available for this device." Logging in returns the no-devices message above. The only remaining option offered is "I do not own a device", which isn't true. That is why this is a forum post.
WHAT I RULED OUT
macOS not supported — no, Meta's own help article states Remote Desktop is the supported path for Mac
VPN or network filtering — reproduced with VPN fully disconnected; auth.meta.com and graph.oculus.com both reachable from the same machine
Broken install — signed Universal build, correct version, present in /Applications
Duplicate app copy hijacking the callback URL scheme — DMG ejected, no stray copies anywhere
Browser handoff failure — log confirms "Received deeplink"
Missing or incomplete Meta Horizon profile — profile exists, has a username, in good standing
No headset linked to the account — visible on both mobile surfaces
Rate limiting — failure is immediate and independent of how long I wait
TWO ASKS
First, fix the data inconsistency. Device association resolves on mobile but not on web or desktop for the same account.
Second, make the client handle a null in the credential verification response. Whatever that field is, the correct behaviour is a specific, actionable error, not "wait 2-5 minutes", which sends people chasing a rate limit that doesn't exist and generates duplicate reports.
Happy to provide full logs. Serial number withheld here, available privately.
Related unresolved threads, same symptom, no fix:
communityforums.atmeta.com/discussions/OtherTroubleshooting/meta-quest-remote-desktop-stuck-in-login-loop-in-my-mac/1373848
communityforums.atmeta.com/t5/Get-Help/Meta-Quest-Remote-Desktop-Something-went-wrong-Please-wait-2-5/td-p/1309169