-
Notifications
You must be signed in to change notification settings - Fork 207
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
Error - "This card action is disabled because you've blocked" #298
Comments
I also have a customer facing this exact issue--he can access Icebreaker on his phone and his old computer, but not on his new computer. Would you prefer I created a new ticket, or simply follow this ticket? |
@kf-paulbrown Thank you for your query. We will check on it and keep you updated |
I also have one customer who has reported this problem. |
Hi @kf-paulbrown , |
EXCEPTION 1 EXCEPTION 2 |
Please give us sometime to get back to you on this issue |
we are noticing same issue to few users. Please share if any fix is identified |
@kf-paulbrown, please share your outlook id so that we can discuss the issue internally. |
|
we still got few users who are noticing this issue. please share any fix if identified to resolve this issue in timely manner. |
I also noticed this behavior after 20-30 min after the bot sends the matchmaking card. |
I also have a user with this issue. (We are not yet running the latest version of Icebreaker.) |
Update: I spent some time with the dev team a couple of weeks ago and redeployed the IceBreaker application, but we are still seeing the issue. I am still in contact with them and will update with details when we have resolved the issue. This issue would be kept "Open". |
Logging this further to @v-royavinash's request to log this as a fresh issue (ref: #239 (comment)).
One of our users has reported an issue with IceBreaker whereby when a match is made and they click on any of the chat/propose/pause buttons they receive an error saying "This card action is disabled because you've blocked":
Note that this isn't occurring for all users, only one has reported it so far.
The text was updated successfully, but these errors were encountered: