[Bug]: macOS v1.4.200 — profile connection fails with "fetch failed" and Relay pairing is unavailable
- Dominant language
- TypeScript
- Stars
- 71.3k
- Forks
- 4.7k
- Avg merge
- 17h 8m
- Merged PRs (30d)
- 475
Description
### Operating system
macOS
### Orca version
v1.4.200
### Details
Short summary
On macOS with Orca v1.4.200, mobile pairing through Orca Relay fails with relay_control_not_active. Attempting to connect my Orca account/profile also fails with fetch failed.
The problem persists after restarting Orca. GlobalProtect is turned off.
What happened?
Initially, I tried to generate a mobile pairing invitation using the automatic / Anywhere (Orca Relay) connection mode. Orca could not create the invitation.
I then attempted to connect my Orca account/profile, but the desktop app displayed this error in Spanish:
Error al conectar perfil
fetch failed
English equivalent: “Failed to connect profile — fetch failed”.
Restarting Orca and retrying did not resolve the issue.
Steps to reproduce
Open Orca v1.4.200 on macOS.
Attempt mobile pairing through Anywhere (Orca Relay).
Observe that creating the pairing invitation fails.
Attempt to connect/sign in through Settings → Orca Account.
Observe the “Failed to connect profile — fetch failed” error.
Restart Orca and retry; the problem persists.
Expected behavior
The account/profile should connect successfully, allowing Orca Relay to generate a mobile pairing invitation.
If the connection fails, the error message or diagnostics should identify the underlying cause.
Relay diagnostics
{
"kind": "mobile_pairing_relay_failure",
"preferredConnectionMode": "automatic",
"failure": {
"code": "relay_control_not_active",
"stage": "create_pairing_relay",
"message": "Relay pairing invite request failed"
},
"at": "2026-09-11T13:08:05.930Z"
}
Additional information
Orca version: v1.4.200, released September 11, 2026.
Operating system: macOS 26.6.2 Tahoe.
GlobalProtect is turned off.
Restarting Orca does not resolve the problem.
Related reports: #10758, #19410 and #19976. These describe similar symptoms, but I cannot confirm whether the underlying cause is the same.
Please let me know which diagnostic steps or logs would help investigate this.
Contributor guide
Assessment
This issue has not been assessed yet.