Android: pairing with the Tailscale code succeeds, then shows "Not on the same network"
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- android, typescript
- Domain
- mobile
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 27
- Avg merge
- 2h 47m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 DuskBotAI/duskbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 pageOpen
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443Possibly taken @viniciusbregoli claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in DuskBotAI/duskbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day