keybase / keybase/client

Problems with website proof on the mobile phone

Open
#9,702 0 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

Hi. I have added my website on my keybase profile, and it correctly shows as authenticated on all my devices but one. On the mobile phone, in fact, it says that the proof could not be found.
How can I fix it?
screenshot 2017-11-28 16 05 35
img_0344

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

The issue provides no file, test, or entry point. Start by reviewing the screenshots and reproducing the missing website proof on the affected mobile device, then compare it with devices where the proof works. Done means the cause and a verified fix for the mobile proof lookup are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, react-native
Domain
authentication, mobile
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.