[Bug]: iOS still shows "Failed to connect. Retrying" on every resume (follow-up to #5695)
维护者通常 1 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 72/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- ios, typescript
- 领域
- mobile
调研方向
标签逻辑位于 apps/mobile/src/features/threads/floating-working-status.ts 中：当 connectionError 不为 null 时，它会显示“Failed to connect”，而不是“Reconnecting to ...”。请检查应用恢复时 connectionError 在何处被设置和清除，因为报告怀疑是应用挂起期间断开的 socket 留下了过期的值。完成标准是：恢复后的会话在重新连接期间显示重连文案，并且在重连真正失败时仍然显示失败文案。
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- TypeScript
- 星标
- 24.8k
- 派生
- 6.4k
- 平均合并
- 5 小时 30 分钟
- 30 天内合并 PR
- 215
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pingdotgg/t3code 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
[Bug]: Diff panel hides the current branch name and the arrow overlaps the base ref when the panel is narrow可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭accepted bug via-triage
难度 2/5 1-3 小时 新手友好度 72/100
pingdotgg/t3code#19048 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug] Windows repository cloning fails while creating an existing drive root可能已有人在做 @pujitha24 于 3 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
[Bug]: Server git tests sign fixture commits with the developer's key when run from the repo root可能已有人在做 @Mnigos 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
AvaProtocol/ava-sdk-js#276 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
apollographql/apollo-client#13493 ·
维护者通常 1 天内回复
-
Custom hosts written as trailing-dot FQDNs (`host.local.`) aren't detected as local backends可能已有人在做 @roboomp 今天认领。 未关闭bug prio:p2 providers triaged
难度 2/5 1-3 小时 新手友好度 82/100
can1357/oh-my-pi#15798 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
code-yeongyu/oh-my-openagent#10172 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
PDFCraftTool/pdfcraft#189 ·