wordpress-mobile / wordpress-mobile/WordPress-Android
Users unable to figure out how to remove Jetpack sites that are unreachable
Open
Nobody has claimed this yet.
[Pri] Low
[Status] Stale
[Type] Bug
Jetpack
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
When viewing a Jetpack site that's not reachable, the app behaves strangely:
- When viewing a site's settings, it'll attempt the load the settings, then kick you out of that screen with a toast that says "Couldn't retrieve site info".
- It looks like the handling is different than on WordPress.com – there, it looks like it automatically hides Jetpack sites that are unreachable. However they still show up in the Android app
To Reproduce:
- Either have (or create) a Jurassic Ninja site on your account. Don't access it for a long time so that it expires. Try to do things with it in the mobile app. Compare the handling of this site by the app with that of WordPress.com.
Tested on Samsung S9, WPAndroid 15.9.1
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 behavior with an expired or unreachable Jurassic Ninja site in the Android app, then compare it with how WordPress.com handles the same site. Trace the site settings and site-list flows involved; done should mean unreachable Jetpack sites are handled consistently and users are not unexpectedly removed from settings.
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
- Needs clarification
- Newbie friendliness
- 35/100