[Bug]: Mobile cannot connect to online relays after updating to 0.0.32-nightly.20260730.958

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

This looks related to #4671 and #4901, but those reports cover direct LAN/Tailscale connections and explicitly say the managed relay was not involved. This report is specifically for mobile connections through online T3 Connect relays.

Area

Not sure (mobile / managed relay connection boundary)

Steps to reproduce

1. Update T3 Code Desktop Nightly to 0.0.32-nightly.20260730.958.
2. Leave the existing T3 Connect relay environments enabled.
3. Confirm the relay entries are still online.
4. Open the T3 Code mobile app and try to connect to either linked environment.
5. Observe the mobile connection status.

Expected behavior

Because the relays are online and enabled, the mobile app should connect to each linked environment normally.

Actual behavior

The relays remain online, but the mobile app cannot connect to them. Each entry repeatedly shows a reconnect loop.

The visible errors are:

Failed to connect. Reconnecting... Reason: TDL connection failed unexpectedly.

and the same failure for Andrew's Mac Studio.

This began after updating to 0.0.32-nightly.20260730.958; the relay connection worked on mobile before the update.

Impact

Major degradation or frequent failure

Mobile access through T3 Connect is unusable even though the relay environments themselves remain online.

Version or commit

0.0.32-nightly.20260730.958

Environment

• T3 Code Desktop Nightly
• Host environment shown in the mobile UI: Andrew's Mac Studio
• T3 Code mobile app (mobile OS/app version not captured)
• Connection path: T3 Connect managed relay
• Multiple linked environments affected (TDL and Andrew's Mac Studio)

Logs or stack traces

Failed to connect. Reconnecting... Reason: TDL connection failed unexpectedly.
Failed to connect. Reconnecting... Reason: Andrew's Mac Studio connection failed unexpectedly.

Screenshots, recordings, or supporting files

A screenshot is available showing both relay entries enabled and simultaneously stuck in the reconnect loop. It could not be attached through the API-based submission.

Workaround

No workaround found.

Reproduce the regression in the T3 Code mobile app using the managed relay path described, with the linked TDL and Andrew's Mac Studio environments. Start by tracing the mobile reconnect flow around the reported TDL connection failure and compare behavior with version 0.0.32-nightly.20260730.958. Done means both online relay entries connect normally without repeated reconnect loops, with regression coverage for the failure.