[Bug]: iOS still shows "Failed to connect. Retrying" on every resume (follow-up to #5695)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ios, typescript
- Domain
- mobile
Research direction
The label logic is in apps/mobile/src/features/threads/floating-working-status.ts: when connectionError is non-null it shows "Failed to connect" instead of "Reconnecting to ...". Check where connectionError gets set and cleared on app resume, since the report suspects a stale value from the socket dropped while suspended. Done means a resumed session shows the reconnecting wording while it reconnects, and the failure wording still appears when a reconnect really fails.
Written by the indexing model from the issue text.
Description
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
- Open a thread in the iOS app, connected to an environment through T3 Connect.
- Put the app in the background for a minute or so.
- Open it again.
Expected behavior
A neutral Reconnecting to <env>... while it reconnects. This is the same thing #5695 asked for, but that one is closed and locked so I can't comment there.
Actual behavior
Pretty much every time I come back to the app, the pill says Failed to connect. Retrying <env>... for a second or two, and then it connects fine.
I checked the server side and the reconnect goes through on the first try every time (auth succeeds, socket is up in about 2s), so nothing is actually failing, it's just the wording.
The copy is still in apps/mobile/src/features/threads/floating-working-status.ts on v0.0.45. If connectionError isn't null it shows the "Failed to connect" label instead of "Reconnecting to ...", and I think after a resume it's still set from the socket that got dropped while the app was suspended.
Impact
Cosmetic issue
Version or commit
Server 0.0.45 (stable), iOS app from the App Store
Environment
iPhone, server on Linux x64 connected through T3 Connect
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 12h 40m
- Merged PRs (30d)
- 322
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
needs more info via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
pingdotgg/t3code#18117 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
[Bug]: Server git tests sign fixture commits with the developer's key when run from the repo rootPossibly taken @Mnigos claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
area:tui enhancement platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anthropics/claude-code#101490 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
netlify/netlify-mcp#75 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
atlassian-labs/compiled#1960 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pnp/cli-microsoft365#7639 ·
Maintainers usually reply within 2 days
-
nextjs-tracking
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cloudflare/vinext#3887 ·
Maintainers usually reply within 1 day