microsoft / botframework-sdk

Bot Framework provides the most comprehensive experience for building conversation applications.
MIT License
7.45k stars 2.44k forks source link

[onTurnError] unhandled error RestError: Failed to decrypt conversation id #6651

Closed AngelELopezM closed 2 weeks ago

AngelELopezM commented 1 month ago

Version

4.22.2

Describe the bug

I have an adaptive card that has a form with inputs the user can interact with, somehow, in my local environment when I interact with the adaptive card the Action.Execute is successful and the card is replaced with another. In the other hand, when I deploy my app the endpoint is hit with the new information but my card never gets replaced.

To Reproduce

Steps to reproduce the behavior:

  1. Hit the endpoint so the user receives the card through teams.
  2. The user interacts with the card they just received.
  3. When the submit button is hit, this error is displayed "Something went wrong. Please try again."

Expected behavior

The card should get replaced like in the local environment.

Screenshots

Additional context

The service is being deployed in azure web app(Windows OS) and using azure bot service, when I go to the log I get this error. [onTurnError] unhandled error RestError: Failed to decrypt conversation id{ "name": "RestError", "code": "BadArgument", "statusCode": 403, "request": { "streamResponseStatusCodes": {}, "url": "https://smba.trafficmanager.net/amer/v3/conversations/REDACTED/pagedmembers", "method": "GET", "headers": { "_headersMap": { "accept": "/", "user-agent": "Microsoft-BotFramework/3.1 botframework-connector/4.22.2 core-http/3.0.4 Node/v18.19.1 OS/(ia32-Windows_NT-10.0.20348)", "authorization": "REDACTED" } }, "withCredentials": false, "timeout": 0, "requestId": "REDACTED" }, "details": { "error": { "code": "BadArgument", "message": "Failed to decrypt conversation id" } }, "message": "Failed to decrypt conversation id" }

stevkan commented 1 month ago

@AngelELopezM - A few questions:

stevkan commented 2 weeks ago

Closing due to inactivity. Please feel free to reopen if the issue persists or you have new details to share.