You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up task to address the concerns identified in #13046.
The fix for the issue above was to switch to regular login whenever the biometric login fails in status-go. The rationale is that the user cannot mitigate this error from the biometrics login screen and the regular login has been designed to show the errors description.
@benjthayer We'll need your help here. Is this flow correct?
Screen.Recording.2024-05-20.at.15.44.37.mov
Feel free to update or close the task.
The flow here is not clear for me.
From the issue description I understand that the problem here is invisible error message in case of failed biometric login. But nothing about automatic switch to password mode. Isn't it confusing for potential user to switch automatically with no chance to do another attempt with biometrics and only optionally explicitly switch to password mode by clicking button?
This is a follow-up task to address the concerns identified in #13046.
The fix for the issue above was to switch to regular login whenever the biometric login fails in status-go. The rationale is that the user cannot mitigate this error from the biometrics login screen and the regular login has been designed to show the errors description.
@benjthayer We'll need your help here. Is this flow correct?
Screen.Recording.2024-05-20.at.15.44.37.mov
Feel free to update or close the task.
From the issue description I understand that the problem here is invisible error message in case of failed biometric login. But nothing about automatic switch to password mode. Isn't it confusing for potential user to switch automatically with no chance to do another attempt with biometrics and only optionally explicitly switch to password mode by clicking button?
Originally posted by @micieslak in #14860 (review)
The text was updated successfully, but these errors were encountered: