keybase / keybase/client

ERROR No device found No device found for device ID a5a<redacted>3018

Open
#1,508 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

All keybase commands that interact with the keybase server produce this error, and always have. E.g., keybase track foo.

Bash+Curl commands work fine, and are how I've got my profile to its current state.

I installed v1.0.5 via the deb package. Also tried reinstall.

Help?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with the installed deb package by running keybase track foo; the issue identifies the command entry point but no source file or test. Trace the client path that reports “No device found” and compare it with the working Bash+Curl behavior. Done means keybase commands that contact the server no longer report this device error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.