keybase / keybase/client

There was an error provisioning

Open
#3,421 3 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

Upon installing the app then try to login:

"There was an error provisioning
Unknown error: Error: Bad key found: no private key material or GPGKey"

my log id: bee588cad611e512edad8b1c

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

Start by reproducing the provisioning error after installing the app and attempting login, then inspect the report associated with log ID bee588cad611e512edad8b1c. Determine why provisioning reports missing private key material or a GPGKey; done means login completes without this error and the relevant regression is covered by a test.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, security
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.