Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After factory reset keycard is broken (applied to blue keycards) #22006

Open
Parveshdhull opened this issue Jan 31, 2025 · 7 comments
Open

After factory reset keycard is broken (applied to blue keycards) #22006

Parveshdhull opened this issue Jan 31, 2025 · 7 comments

Comments

@Parveshdhull
Copy link
Member

Summary

I was using the factory reset flow during onboarding, and my keycard likely got disconnected in the process. Now, both the mobile and desktop clients are displaying the message, 'This is not a keycard.'

Image

cc @flexsurfer

@flexsurfer
Copy link
Member

cc @bitgamma

@bitgamma
Copy link
Member

bitgamma commented Jan 31, 2025

this could happen on old cards and is fixable by doing a new factory reset or by using keycard-cli to reinstall the applet. With orange cards it is not possible to end up in this state anymore

@Parveshdhull
Copy link
Member Author

Hi @mobile-qa,

Please keep an eye on the factory reset feature on mobile and let us know if this issue occurs again.

Thanks to the information provided by @bitgamma, we now know:

  • This behavior is quite rare and It only happens with blue cards (older ones).
  • It occurs if the card gets disconnected during the factory reset.

@pavloburykh
Copy link
Contributor

pavloburykh commented Feb 4, 2025

@Parveshdhull @flexsurfer @bitgamma

This behaviour is quite rare and It only happens with blue cards (older ones).

I was able reproduce it on with the new Keycard (not the old one). The issue is quite serious as now my keycard is broken. I cannot reset it neither on mobile nor on desktop. So we should prioritise this bug. cc @ilmotta

The steps are the same described by @Parveshdhull in the issue description. Although I do not recommend to reproduce it as keycard will be broken, at least for now I do not know how to reset it and make work again.

Steps:

  1. Take not an empty Keycard and initiate reset process
  2. During final reset scan disconnect keycard before reset is completed
  3. Try to scan keycard again

Actual result:

telegram-cloud-document-2-5264816120262584225.mp4

@pavloburykh pavloburykh added this to the 2.33.0 milestone Feb 4, 2025
@pavloburykh
Copy link
Contributor

Although I do not recommend to reproduce it as keycard will be broken, at least for now I do not know how to reset it and make work again.

@Parveshdhull I have found a workaround how to reset the broken keycard: you can do it using Status v.1, here is a link for downloading apk https://status-im-releases.ams3.digitaloceanspaces.com/StatusIm-Mobile-v1.20.5-c86ad1-universal.apk

@pavloburykh
Copy link
Contributor

@Parveshdhull @flexsurfer @bitgamma

Final update from me: the card I considered to be a new one (black) turned out to be an old one. I was not able to reproduce the issue using orange card, so I am deprioritising the issue back to its initial status and removing from the milestone.

Sorry for confusion and false alert.

@pavloburykh pavloburykh removed this from the 2.33.0 milestone Feb 4, 2025
@pavloburykh pavloburykh moved this from Next to Backlog in Status Desktop/Mobile Board Feb 4, 2025
@churik churik removed the no-steps label Feb 5, 2025
@churik churik changed the title After factory reset keycard is broken After factory reset keycard is broken (applied to black keycards) Feb 5, 2025
@churik churik changed the title After factory reset keycard is broken (applied to black keycards) After factory reset keycard is broken (applied to blue keycards) Feb 5, 2025
@flexsurfer
Copy link
Member

flexsurfer commented Feb 10, 2025

one more case, now on unblock ( because there is a reset step) #22030 (comment) , seems like old cards really easy to break

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

5 participants