Sign up
View stargazersSign up

[Bug]: Android 2.2.0: browser preview fails with 404 on /websocket-ticket/media, and no push notifications#29597

opened9d agobyOOrPat14

Versions

  • Android app 2.2.0 (Samsung Galaxy Z Fold5)
  • macOS T3 Code Nightly 0.1.7-nightly.20261102.4093
  • Connected through T3 Connect (relay)

Preview Opening a thread's browser preview on the phone shows: "Remote environment endpoint https://prod-…t3coderelay.com/api/auth/websocket-ticket/media returned undeclared status 404." Retry gives the same error. It also happened on the previous desktop nightly (0.1.1-nightly.20261020).

Push notifications Notifications are enabled in the app and in Android settings, but no push has ever arrived (completed runs, approvals, agent push).

Expected The preview streams to the phone, and pushes arrive.

JJulius Marminge9d ago

Reproduced the preview error against a server built from v0.1.1-nightly.20261020.3401: POST /api/auth/websocket-ticket/media returns 404 there, while the bare /api/auth/websocket-ticket returns a ticket that the preview stream accepts (upgrade 101). Current clients didn't fall back to the bare route for media tickets the way they do for RPC tickets. The fix is in https://git.cafe/pingdotgg/t3code/pull/29616. Main's server (a9ac1e8e54) answers 200 on /media, so a host on a nightly from 2026-10-24 or later should not return this 404. If it still does after the desktop app has fully restarted, please say so here.

The push-notification part has a separate cause; Android registration failures are tracked in https://git.cafe/pingdotgg/t3code/issues/26530.