A jetpack site might disappear when Jetpack is deactivated

[koke]

If you add a self hosted, then connect to Jetpack and later deactivate Jetpack, the site will disappear from the app. This is by design, but could be confusing to users.

I'm not sure what to do about it, if anything, but we could flag any self hosted as manually added in the app, then if it gets removed from the wp.com account, we migrate it back to a self hosted, but needing authentication (or maybe we keep the password from the start). This would require better prompts to re-authenticate though (see #687)

[stale[bot]]

This issue has been marked as stale because:

• It has been inactive for the past year.
• It isn't in a project or a milestone.
• It hasn’t been labeled [Pri] Blocker, [Pri] High, or good first issue.

Please comment with an update if you believe this issue is still valid or if it can be closed. This issue will also be reviewed for validity and priority (cc @designsimply).

[designsimply]

Tested and confirmed that deactivating a Jetpack-connected site makes it disappear from the site picker in the app. Tested with WPiOS 13.3.0.0 (TestFlight) on iPhone 6S iOS 13.1.2.

[stale[bot]]

This issue has been marked as stale because:

• It has been inactive for the past year.
• It isn't in a project or a milestone.
• It hasn’t been labeled [Pri] Blocker, [Pri] High, or good first issue.

Please comment with an update if you believe this issue is still valid or if it can be closed. This issue will also be reviewed for validity and priority during regularly scheduled triage sessions.

[designsimply]

Still valid. I re-tested this in 16.2 beta testing and found that deactivating Jetpack still removes it from the Site Picker when I'm logged in as the connected WordPress.com account in the app an that I must both re-activate and re-connect the Jetpack site to the same account to get it to appear again. (1m4s)

^{Tested with WPiOS 16.2.0.0 TestFlight beta on iPhone 11 iOS 14.1.}

[designsimply]

@yaelirub this is a stale, low priority issue but it's also not very actionable since there isn't a clear path for exactly what to update to improve the situation. Would you mind having a look and letting me know if this is something you'd like to keep open and explore further to make it actionable or if it would be okay to close as wontfix unless it comes up from users?

[yaelirub]

Thanks for flagging, @designsimply! Lets leave it open for now

[stale[bot]]

This issue has been marked as stale because:

• It has been inactive for the past year.
• It isn't in a project or a milestone.
• It hasn’t been labeled [Pri] Blocker, [Pri] High, or good first issue.

Please comment with an update if you believe this issue is still valid or if it can be closed. This issue will also be reviewed for validity and priority during regularly scheduled triage sessions.

[dangermattic]

Thanks for reporting! 👍