wordpress-mobile / wordpress-mobile/WordPress-Android
Login: SMS with verification code silently fails to be sent when using Google Sign-In with a disconnected 2FA account
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
I expected to either be able to receive a SMS with a verification code when my Google account is disconnected from my WordPress.com account or at least see an error explaining why it wasn't possible to send one.
Actual behavior
I don't receive a SMS and don't see any error message explaining why.
Steps to reproduce the behavior
- Start with an account with Google sign-in and two-factor authentication enabled via SMS.
- Try to log in with your Google account.
- You should receive the SMS with the verification code and be able to log in normally.
- Quickly log out and try to log in again.
- You should see a "Too many attempts" error, which is expected.
- From the web, disconnect your Google account on the Social Login page.
- Try to log in again.
- Notice how the "Too many attempts" error is never shown.
- Notice the Email/Password screen.
- Enter your WordPress.com account password.
- Tap Continue.
- Notice the 2FA screen.
- Notice how no SMS was received.
- Tap "Text me a code instead".
- Notice how no SMS was received again.
- Notice how no error is shown.
Tested on Pixel 3 XL, Android 10, WPAndroid 15.2-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
Start by reproducing the Google Sign-In, disconnected-account, password, and 2FA flow described on the tested Android setup. Trace the login path around the Email/Password screen, 2FA screen, and “Text me a code instead” action. Done means the flow either sends the SMS or displays an explanatory error instead of failing silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100