Automattic / Automattic/pocket-casts-android
Tapping on the "Sign In Error" notification takes you to email login with no Google log in option
- Dominant language
- Kotlin
- Stars
- 2.8k
- Forks
- 308
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 143
Description
### Description
When there is an authentication issue and the user is signed out of the app, we present a notification informing the user of this and asking them to sign back in. Tapping on this notification pulls up a screen for email and password login. It should be opening our onboarding flow, which allows logging in with Google.
### Step-by-step reproduction instructions
1. Have the app get an unauthorized response when it tries to refresh the token
2. Observe the notification that you've been logged out and asking you to log in
3. Tap on the notification
### Screenshots or screen recording


### Did you search for existing bug reports?
- [X] I have searched for existing bug reports.
### Device, Operating system, and Pocket Casts app version
Samsung A13, Android 13, 7.41-rc-3
Contributor guide
Research direction
Reproduce the unauthorized token-refresh flow on Android, then trace the notification tap handling and the destinations used for email login and onboarding. Done means tapping the sign-out notification opens the onboarding flow and exposes the Google login option rather than only the email-and-password screen.
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
- 35/100