Two physical devices seen as one device in Keybase, successfully logged into both

未关闭
#4,277 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
android
领域
mobile

调研方向

从 Keybase Android 应用的 Devices 标签页以及报告中的 Pixel 5 到 Pixel 9 Pro 数据迁移场景开始。复现登录流程,并比较迁移前后的设备身份;当两部手机显示为独立设备,且新手机遵循预期的设备设置流程时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

I was logged into Keybase on my Google Pixel 5. I just received a new Google Pixel 9 Pro, and as part of the initial setup had Google copy data from my Pixel 5.

When I launched Keybase, it already knew I was "jdmallen" and asked me to sign in. After I provided my password, I was immediately presented the home screen. I thought this was a bit weird, since I usually have to explicitly add a device using an existing device or paper code. When I pulled up the Devices tab in the app, I saw that both phones self-identify as the same device.

CV6A1971

CV6A1973

This feels like a serious bug. I tried reporting this on Hacktivity, but it appears to be a 404 now.

image

I have not done anything with Keybase yet just in case y'all want me to try something. I have a feeling if I clear storage and reinstall, it'll have me set up the new phone like normal.

主要语言
没有语言数据
星标
899
派生
40
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

keybase/keybase-issues 的其他 Issue

查看 keybase/keybase-issues 的全部 Issue

相似的 Issue

更多 Mobile Dev Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。