[Bug]: T3Code Android nightly google group is banned #17905

Activity

1. niteshbalusu11

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Oct 10, 2026
2. labeebbappu commented on Oct 11, 2026

   

   labeebbappu

   on Oct 11, 2026

   More actions

   Confirming this reproduces, and adding a detail that I think changes the triage priority: the banned group is t3-code-v2-beta@googlegroups.com, which gates the Play Store closed beta track — not only nightly.

   The screenshot in the issue body is the same group I'm hitting. Identical banner:

   Banned content warning
   T3 Code V2 Beta has been identified as containing spam, malware, or other malicious content.

   URL: https://groups.google.com/g/t3-code-v2-beta

   The title says "nightly", so I wanted to flag the broader scope in case it gets triaged as nightly-only.

   Why this is currently blocking, not just inconvenient

   There's a second problem that the banned group turns into a dead end.

   I'm an existing beta tester (the Play listing shows "T3 Code (Beta)" and "You're a beta tester for this app"), but Play is still serving me 1.4.0 on an OPPO CPH2603. Clearing Google Play Store cache did not move it.

   1.4.0 speaks orchestration protocol 1. My desktop is on nightly 0.0.46-nightly.20261010.2908, which advertises protocol 2 — confirmed directly:

   $ curl -s http://<desktop>:3773/.well-known/t3/environment | jq .orchestrationProtocolVersion
   2
   

   So every environment in the Android app shows "Client not supported" and the enable toggle is latched off. That part is expected behaviour per #14871 — the client just needs to be on a protocol-2 build.

   The community workaround for a stuck Play version is the full re-enrol cycle: leave the beta → leave the Google Group → rejoin the group → rejoin the beta → wait → clear cache. Steps 2 and 3 are impossible while the group is banned.

   Net effect: a tester who is already enrolled but whose Play client is stale has no path to a protocol-2 build. Not via the app, not via re-enrolment.

   Suggestions

   • Appeal the Google Groups ban (the T3 Code V2 Beta group looks like a false positive — Groups auto-flags low-traffic groups created mainly as Play test-access gates fairly often).
   • Independently of the appeal, consider not gating closed testing on Google Groups at all. Play accepts an email list uploaded directly to the testing track, which removes this entire failure mode. This also overlaps with the APKs-in-GitHub-releases request in [Feature]: Provide Android APK for nightly builds #6880.

   Workaround for anyone else stuck here

   The desktop server ships a web client on the same port, built from the same source as the server — so it speaks protocol 2 and the Android app version stops mattering:

   http://<desktop-lan-ip>:3773/
   

   Confirmed working: 200, text/html, <title>T3 Code (Alpha)</title>. Needs a pairing credential (Settings → Connections → + Create link, or t3 pair). Caveat: a plain-HTTP LAN origin is not a secure browser context, so secure-context-only features are unavailable; t3 pair --tailscale gives an HTTPS MagicDNS URL instead.

   Environment

   • Android app: 1.4.0 (Play beta track), OPPO CPH2603
   • Desktop: T3 Code Nightly 0.0.46-nightly.20261010.2908, macOS 15 (Darwin 25.6.0), Apple Silicon

   👀React with 👀4Reacted by Ashley Buckingham, Jan Poth, Hampus Sjöberg and Gadejo
3. niteshbalusu11 commented on Oct 11, 2026

   

   niteshbalusu11

   on Oct 11, 2026

   Author

   More actions

   Thanks for explaining in more detail. I had to build the apk myself from source to get around the problem. Though, this means t3 connect won’t work and I’m just using Tailscale for now.

   👀React with 👀1Reacted by labeebbappu
4. juliusmarminge commented on Oct 11, 2026

   

   juliusmarminge

   on Oct 11, 2026

   Member

   More actions

   Note

   Grok responding on behalf of Julius.

   #16271 just merged, and it was written for exactly this: since the testing group can't take new members, CI now publishes the Play-signed v2-preview APK to a rolling android-nightly release. It has the same signature as the Play install, so you don't need to join the group or build it yourself. The page fills in after the first run once the maintainer setup is done, so give it a little time if it 404s. Closing this as fixed.
5. juliusmarminge

   removed

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Oct 11, 2026
6. juliusmarminge

   closed this as completedon Oct 11, 2026