[Bug]: Android 2.0.0 shows "Client not supported" for every published desktop build (orchestration protocol 2 vs 1) #14901

Before submitting

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

Area

apps/mobile

Steps to reproduce

1. Run the desktop app on the latest nightly (0.0.45-nightly.20261002.2595) or latest stable (v0.0.45), with the machine registered via T3 Connect.
2. Update the Android app from the Play Store to 2.0.0.
3. Open the environment in the Android app.

Expected behavior

The Android app connects to the latest published desktop build, or the mobile release waits until a desktop nightly/stable that speaks the same orchestration protocol is available.

Actual behavior

The environment shows "Client not supported" and the connection toggle is forced off. The T3 Connect relay itself is fine.

Cause: de343914 (feat(orchestrator): introduce new orchestrator, #2829) bumped ORCHESTRATION_PROTOCOL_VERSION from 1 to 2, and e9298af6 bumped mobile to 2.0.0 right after. orchestrationProtocolCompatibilityError (packages/client-runtime/src/connection/compatibility.ts) requires an exact match, so the 2.0.0 app rejects every protocol-1 server. As of now:

So the store mobile build currently can't connect to any desktop build users are meant to install.

Impact

Major degradation or frequent failure

Version or commit

Android 2.0.0 (Play Store); desktop 0.0.45-nightly.20261002.2595 (Linux AppImage), also applies to v0.0.45

Environment

Android phone → T3 Connect managed endpoint → Linux desktop app

Logs or stack traces

Client not supported

Workaround

Wait for the next nightly built from main (protocol 2), or install the 0.0.46 preview build. It may also help to show the specific detail text ("This client requires a newer server…") in the mobile UI, since the generic "Client not supported" makes it look like the phone is too old.