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 #910

Closed
Tracked by #1106
ghost opened this issue May 17, 2023 · 1 comment · Fixed by #1327
Closed
Tracked by #1106

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

ghost opened this issue May 17, 2023 · 1 comment · Fixed by #1327
Labels
A-User-Detail 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

Comments

@ghost
Copy link

ghost commented May 17, 2023

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 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

iPhone 12 mini

Operating system version

iOS 16.3.1

Application version

Element 1.1.0 (214)

Homeserver

matrix.org

Will you send logs?

No

@ghost
Copy link
Author

ghost commented Jul 5, 2023

I retested this on Element X iOS 1.1.8 (271) and it is still reproducing.

@kittykat kittykat added Z-Schedule S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow A-User-Detail labels Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-User-Detail 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants