Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blocking a user does not retain state in UI until back in the room #846

Closed
Tracked by #1106
kittykat opened this issue Jul 11, 2023 · 0 comments · Fixed by #847
Closed
Tracked by #1106

Blocking a user does not retain state in UI until back in the room #846

kittykat opened this issue Jul 11, 2023 · 0 comments · Fixed by #847
Assignees
Labels
A-User-Profile O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@kittykat
Copy link
Contributor

Steps to reproduce

  1. Open the room details screen and tap People.
  2. Tap on a user to open their info screen.
  3. Tap on Block user. The button state doesn't change for a while,then changes to unblock user indicating the user has been blocked.
  4. Go back to the room details People screen and tap on the same user, note the state of the block button.

Outcome

What did you expect?

If the user is blocked they should appear as blocked.

What happened instead?

The block button has changed back to Block user even though the user is currently blocked. You can verify they are blocked by going back to the room and seeing their content gone from the timeline. As well, if you go back to the info screen for that user from the room timeline it reflects the correct state.

Your phone model

Pixel 6a

Operating system version

Graphene OS

Application version and app store

0.1.0-nightly (1001000)

Homeserver

matrix.org

Will you send logs?

Yes

Are you willing to provide a PR?

No

@kittykat kittykat added S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems O-Uncommon Most users are unlikely to come across this or unexpected workflow A-User-Profile Z-Schedule labels Jul 11, 2023
@bmarty bmarty self-assigned this Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-User-Profile O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants