wordpress-mobile / wordpress-mobile/WordPress-Android
Misleading snackbar message on page load fail retry
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Could not investigate the reason and/or if it can cover something more, but while looking into this Push Notifications PR I noticed the following
Expected behavior
When a page upload fails, we present a system notification. If user taps on the notification, the pages list is opened (while the page upload is being retried) and a snackbar is presented saying something like "Page upload retrying" or something similar.
Actual behavior
When a page upload fails, we present a system notification. If user taps on the notification, the pages list is opened (while the page upload is being retried) and a snackbar is presented saying "The selected page is not available"
Steps to reproduce the behavior
-
Create a new page and force the upload fail (one way is using the Breakpoint feature of Charles Proxy configuring a breakpoint like this

where is the site id of the site you are using to upload the page -
once the upload fail, notice the upload fail notification is shown

-
tap on the notification and check you get the snackbar saying "The selected page is not available"
Tested on [Pixel 3 Emu], Android [API 29], WPAndroid [alpha-234]
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 tracing the upload-failure notification tap into the pages list, using the linked Push Notifications PR as context. Reproduce the failure with the described Charles Proxy breakpoint on the Pixel 3/API 29 setup, then verify that the snackbar describes the page upload retry rather than saying the selected page is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100