Forum Discussion

shuaibird's avatar
shuaibird
Protege
21 days ago
Solved

Login silently fails on macOS 26.1 (Tahoe) — missing XPC helper com.meta.virtualdesktop-spks

Environment

  • macOS 26.1 (Build 25B78)
  • Meta Quest Remote Desktop version 80.0.0.5.114

 

Issue

Clicking Login shows "Check your browser to continue logging in." but nothing opens and no network request is made.

 

Root cause found in Console.app logs

[0x7b8d71900] activating connection: name=com.meta.virtualdesktop-spks
[0x7b8d71900] failed to do a bootstrap look-up: xpc_error=[3: No such process]
[0x7b8d71900] invalidated after a failed init

The app tries to delegate the login flow to a helper process (com.meta.virtualdesktop-spks) but it doesn't exist. Verified by running:

find /Applications/Meta\ Quest\ Remote\ Desktop.app -name "*spks*"

This returns nothing — the helper is not present anywhere in the app bundle.

 

Steps already taken

  • Full clean uninstall (removed app, LaunchAgents, caches, preferences, killed launchctl entries)
  • Fresh reinstall
  • Same issue persists

 

This appears to be a macOS 26 Tahoe compatibility issue where the helper is either not being packaged or not registering correctly on the new OS. Please update the app for macOS 26 support.

  • Update: resolved this by simply restarting my laptop. The XPC helper registered correctly after reboot and login worked as expected. Leaving this here in case anyone hits the same wall.

5 Replies

    • shuaibird's avatar
      shuaibird
      Protege

      Thanks for the suggestion, but the issue is with the Mac companion app, not the headset itself. The login flow fails silently on the Mac before any connection to the headset is even attempted. The root cause is a missing XPC helper (com.meta.virtualdesktop-spks) in the Mac app bundle, as detailed above.

      • steve_40's avatar
        steve_40
        Honored Visionary

        Can you report the issue within the app without logging in? Meta Engineers don't usually monitor these community forums. But even if you report the problem from the headset, the report might get forwarded to the right people.

  • Update: resolved this by simply restarting my laptop. The XPC helper registered correctly after reboot and login worked as expected. Leaving this here in case anyone hits the same wall.