403 User Blocked Bot Error Unexpected #6655
Labels
Bot Services
Required for internal Azure reporting. Do not remove. Do not change color.
bug
Indicates an unexpected problem or an unintended behavior.
customer-replied-to
Indicates that the team has replied to the issue reported by the customer. Do not delete.
customer-reported
Issue is created by anyone that is not a collaborator in the repository.
Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
4.21.4
Describe the bug
Member_2.sendAdaptiveCard
with no errorHandler passed in foronError
, we get a 403User blocked the conversation with the bot
. Of course, this is expected as we now are purposely blocking the bot to test sending cards. However, what we do not understand is why when someone has the bot blocked, the 403 causes the bot to entirely crash and send the pre-fabbedUser blocked the conversation with the bot
messages to the channel the bot is in. We cannot find documentation to help us better understand how to elegantly handle this error.To Reproduce
Steps to reproduce the behavior:
member.sendAdaptiveCard
(i.e. Member_2.sendAdpativeCard)Expected behavior
Upon completing the reproduction steps, you should see your bot sends 2 messages to the "general channel" (a message of the error, and a message to fix the source code) and produces an "unhandled error" within your console.
What we expect to happen:
Give a clear and concise description of what you expected to happen.
We expect the message to not send, but we do not expect the bot to crash and be told the error is unhandled.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
If someone could help us understand if there are any other ways a bot ends up blocked by a user without using the triple dot menu in the chat section, it would help us write documentation for our end users. Additionally, examples and documentation on how to better and more elegantly handle the 403 error would be extremely appreciated. Apologies in advance if this isn't there this isn't meant to go, but after a few conversations we feel the two scenarios scream more like a potential bug than a stack overflow issue.
Tracking Status
Dotnet SDK TODO
Javascript SDK TODO
Python SDK TODO
Java SDK TODO
Samples TODO
Docs TODO
Tools TODO
The text was updated successfully, but these errors were encountered: