-
Notifications
You must be signed in to change notification settings - Fork 79
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
[Onboarding] "Unblock using PUK" keycard flow #17092
Milestone
Comments
6 tasks
caybro
changed the title
[Onboarding] U(b)nlock keycard flows (seedphrase/PUK)
[Onboarding] Un(b)lock keycard flows (seedphrase/PUK)
Jan 20, 2025
caybro
changed the title
[Onboarding] Un(b)lock keycard flows (seedphrase/PUK)
[Onboarding] Un(b)lock using PUK keycard flow
Jan 20, 2025
caybro
changed the title
[Onboarding] Un(b)lock using PUK keycard flow
[Onboarding] "Un(b)lock using PUK" keycard flow
Jan 20, 2025
caybro
added a commit
that referenced
this issue
Jan 21, 2025
- integrate the PUK unlock flow into the Onboarding and added a dedicated SB page for it - TODO: integrate into Login screen - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
2 tasks
caybro
added a commit
that referenced
this issue
Jan 21, 2025
- integrate the PUK unlock flow into the Onboarding and added a dedicated SB page for it - TODO: integrate into Login screen - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 21, 2025
- integrate the PUK unlock flow into the Onboarding and added a dedicated SB page for it - TODO: integrate into Login screen - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 21, 2025
- integrate the PUK unlock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
2 tasks
caybro
added a commit
that referenced
this issue
Jan 21, 2025
- integrate the PUK unlock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 22, 2025
- integrate the PUK unlock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 22, 2025
- integrate the PUK unlock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 23, 2025
- integrate the PUK unlock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 23, 2025
- integrate the PUK unlock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
changed the title
[Onboarding] "Un(b)lock using PUK" keycard flow
[Onboarding] "Unblock using PUK" keycard flow
Jan 23, 2025
caybro
added a commit
that referenced
this issue
Jan 23, 2025
- integrate the PUK unlock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 23, 2025
- integrate the PUK unblock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
caybro
added a commit
that referenced
this issue
Jan 24, 2025
- integrate the PUK unblock flow into the Onboarding and Login screen - added a dedicated SB page for it - remove the `Locked` keycard state everywhere in favor of `BlockedPIN` and `BlockedPUK` - fix the various "Locked" buttons, based on the context and the state of the keycard Fixes: #17092
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As part of the onboarding or login, we need to deal with a (b)locked keycard:
The purpose of this task is to implement pure QML UI based components/flows/modals to make it possible to un(b)lock the keycard from the new onboarding or login screen.
Old design (to be updated):
https://www.figma.com/design/idUoxN7OIW2Jpp3PMJ1Rl8/%E2%9A%99%EF%B8%8F-Settings-%7C-Desktop?node-id=7258-183484&m=dev
The text was updated successfully, but these errors were encountered: