wordpress-mobile / wordpress-mobile/WordPress-Android
Login: If error notification prompts to enter password, bring user to password entry
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Expected behavior
When I see an error message with a suggested alternate workflow, help me do the right thing faster by bringing me there first.
In this scenario, I tried to login using a magic sign in link, and saw the notification that that sign in method wasn't available.
I would expect to then have the screen change / my focus moved to the password entry field.
Actual behavior
I remain on the screen with the tempting button to send a link again. In order to do the right thing, I have to tap the back button myself.
This occurs in both the Jetpack and WordPress apps.
Steps to reproduce the behavior
- Start logging in
- Rather than entering password, tap option to send magic sign in link
- (Note -- not sure why this failed for my user, but in order to see the issue it has to)
- Note notification about error appears but you're still in the screen to send a link
Tested on [Pixel 7], Android [13], WPAndroid [21.1-rc-1], Jetpack [21.1-rc-2]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failed magic sign-in flow on Android using the steps in the issue, then trace the login screen's error handling and navigation. Done means that after the unavailable sign-in-link notification, the screen or focus moves to password entry instead of leaving the user on the link-sending screen in both WordPress and Jetpack apps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100