wordpress-mobile / wordpress-mobile/WordPress-Android
Follow conversation: Improve error message when request fails due to settings
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
The API call to follow a conversation in the Reader can return success:false as part of its response. One way to replicate this is by setting WordPress.com's Reader Subscription notification settings to block all emails, and then try to follow a conversation.
When this happen an error message appears that says "Invalid response received". Let's figure out what other cases might produce this error, and then let's see if we can improve this error message and perhaps nudge the user with a path forward. For example, to check their settings to see if they are blocking email.
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 at the Reader's follow-conversation API call and reproduce the failure with Reader Subscription notification settings configured to block all emails. Trace other responses that produce “Invalid response received,” then define an actionable message and verify it covers the identified cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100