WordPress-Android icon indicating copy to clipboard operation
WordPress-Android copied to clipboard

App does not receive user role changes after they've been modified from another device

Open guarani opened this issue 5 years ago • 3 comments

Expected behavior

If the user's role of a self-hosted site is changed remotely (i.e. not within the app), it should be possible to have the app refresh allowing the user to perform actions in accordance with their newly given role.

Actual behavior

When logged in to a self-hosted site, if I change the user's role remotely, there appears to be no way of refreshing the app so that the user gains their new role. I tried pulling-to-refresh on the site screen (it isn't possible), I also tried looking for a way to log out and log in again (there's no option to do so when logged in to a self-hosted site). Switching between tabs ("My Site"/Reader/Notifications) doesn't cause the app to refresh either.

I ended up clearing the app's data in the device settings (which is the only apparent way to log out of the self-hosted site). Logging back in again and I noticed the user now has their correct role.

Steps to reproduce the behavior

  1. In the app, log in to a site with a user with a role ofcontributor (contributors don't have access to Pages)
  2. Notice that the app correctly does not show the Pages buttons on the site screen
  3. On the web (not in the app), change the user to be an administrator (who do have access to Page-related functionality)
  4. Go back to the app and notice that the Pages buttons is still not present and there's no apparent way to refresh the app to allow it
Tested on Samsung S10, Android 10, WPAndroid 15.8

guarani avatar Oct 15 '20 00:10 guarani

Found while filing https://github.com/wordpress-mobile/WordPress-Android/issues/13139.

guarani avatar Oct 15 '20 00:10 guarani

A possible UX solution to this issue could be to allow pull-to-refresh on the site screen.

guarani avatar Oct 15 '20 00:10 guarani

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.

stale[bot] avatar May 01 '22 13:05 stale[bot]