Android: pairing with the Tailscale code succeeds, then shows "Not on the same network"
维护者通常 1 天内回复
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- android, typescript
- 领域
- mobile
调研方向
Read src/mobile/connection/connections.ts, especially connectToWorkspace, and check the pairing flow where onLinked runs after redeemLegacyPairing. The issue reports a local one-condition fix and offers a test; an open linked pull request (#60) shows the work is already underway.
由索引模型根据 Issue 内容生成。
描述
What happened
Settings → Phone → Tailscale → Pair, then scan on Android: the phone shows "Not on the same network", although the Mac is reachable over the tailnet (the …ts.net:8810 health check loads in the phone's browser).
With an on-screen trace: the Tailscale QR is a legacy payload (no via). POST /api/pair returns 201, and GET /api/auth/session returns 404 through the companion. redeemLegacyPairing accepts a 403/404 session answer for companion pairings (companionRefused), but connectToWorkspace (src/mobile/connection/connections.ts), which onLinked runs right after, treats any non-OK session answer as a failed route and ends with PairError("unreachable"). The onboarding screen shows that as "Not on the same network".
Fix that worked locally (one condition in connectToWorkspace):
const companionRefused = route.kind === "companion" && [403, 404].includes(response.status);
if (signal.aborted || (!response.ok && !companionRefused)) {
Happy to send this as a small PR with a test.
Setup: desktop 0.2.17 on macOS; phone app built from main at 7791c1f (apps/mobile, Android debug build, Samsung Galaxy S26), paired over the companion (port 8810).
Steps to reproduce
- Mac with Tailscale running (MagicDNS on); the Android phone on the same tailnet.
- Desktop: Settings → Phone → Tailscale → Pair.
- Scan with the Android app → "Not on the same network".
Version
0.2.17 (desktop, macOS); phone app from main @ 7791c1f
Platform
Android
Engine
No response
Logs or screenshots
- 主要语言
- TypeScript
- 星标
- 277
- 派生
- 27
- 平均合并
- 2 小时 47 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
DuskBotAI/duskbot 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 page未关闭
难度 3/5 1-2 天 新手友好度 65/100
维护者通常 1 天内回复
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443可能已有人在做 @viniciusbregoli 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
查看 DuskBotAI/duskbot 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
inabagumi/shinju-date#7406 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
umami-software/umami#4787 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复