-
Notifications
You must be signed in to change notification settings - Fork 319
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
Unban not working #888
Comments
Thanks for the video, we will soon work on fixing this 👍🏼 |
When i unban user in chat then everything it gives success response when that user try to send message i get error saying `🕸️ ╔ DioErrorType.response 2022-05-03 11:39:19.821 🚨 🕸️ ║ { 2022-05-03 11:39:19.821 🚨 🕸️ ║ code: 17, 2022-05-03 11:39:19.821 🚨 🕸️ ║ "SendMessage failed with error: "Sorry, you do not have access to this feature. Your account is currently suspen 2022-05-03 11:39:19.821 🚨 🕸️ ║ ded from chat."" 2022-05-03 11:39:19.821 🚨 🕸️ ║ StatusCode: 403, 2022-05-03 11:39:19.821 🚨 🕸️ ║ duration: "0.00ms", 2022-05-03 11:39:19.821 🚨 🕸️ ║ more_info: "https://getstream.io/chat/docs/api_errors_response" 2022-05-03 11:39:19.821 🚨 🕸️ ║ } ` |
@developerpaaji |
@imtoori but this happens only after I ban user |
these are permission i have configured for group. [ |
@developerpaaji can you contact support? we can help you more easily since we can ask for your app id |
Which packages are you using?
stream_chat_flutter
On what platforms did you experience the issue?
iOS, Android
What version are you using?
3.3.2
What happened?
Ban command working but not unban command. With ban command when i send user name then its okay but with unban it seems it require user id
Steps to reproduce
1. Go to message screen 2. Click on command icon 3. Click on unban 4. Mention user 5. You will get error - Invalid unban cmd, please specify a valid user Here is the video -
Video Link
Supporting info to reproduce
No response
Relevant log output
No response
Flutter analyze output
No response
Flutter doctor output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: