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

[Onboarding] Add proper handling of failed keycard's set pin operation #17034

Closed
micieslak opened this issue Jan 7, 2025 · 5 comments
Closed

Comments

@micieslak
Copy link
Member

Description

Currently that situation is not covered in Figma nor the UI flow.

@jrainville
Copy link
Member

#17127 adds some placeholder. We need some designs to have the final state

@caybro
Copy link
Member

caybro commented Feb 3, 2025

CC @benjthayer

@benjthayer
Copy link

CC @benjthayer

Thanks @caybro !

Couple of questions so I can design this screen accurately if ok:

  1. Do we have any known reasons why this might occur? Assuming its an issue outside of the card or reader not being inserted correctly?

  2. Is there anything the user can do to rectify this? Or is it just there is a fault with the card that will never be able to be rectified?

  3. Dependent on 2 I suppose, we'll need to decide where the user is taken back to in the flow depending on what they are able to do to resolve the issue

@caybro
Copy link
Member

caybro commented Feb 4, 2025

CC @benjthayer

Thanks @caybro !

Couple of questions so I can design this screen accurately if ok:

  1. Do we have any known reasons why this might occur? Assuming its an issue outside of the card or reader not being inserted correctly?
  2. Is there anything the user can do to rectify this? Or is it just there is a fault with the card that will never be able to be rectified?
  3. Dependent on 2 I suppose, we'll need to decide where the user is taken back to in the flow depending on what they are able to do to resolve the issue

@igor-sirotin should be able to answer those ^^

@caybro caybro moved this from Next to Blocked in Status Desktop/Mobile Board Feb 5, 2025
@caybro
Copy link
Member

caybro commented Feb 6, 2025

Will be handled as part of #17232

@caybro caybro closed this as completed Feb 6, 2025
@github-project-automation github-project-automation bot moved this from Blocked to Done in Status Desktop/Mobile Board Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants