Notifications - “Failed to decrypt conversation id” when sending activity

[I566748]

Describe the bug
We are facing issue while trying to decrypt conversation id when sending notifications from Bot. Below is the code to find the member using email to which notification has to be sent.

const member = await commandApp.notification.findMember(
async m => m.account.userPrincipalName.toLowerCase() === notificationData.email
);

Currently it works only for 1 bot service while we have issues with remaining.

[qinezh]

@I566748 would you please provide the SDK version and the related error message?

[I566748]

Version details : "@microsoft/adaptivecards-tools": "^1.3.2",
"@microsoft/teamsfx": "^2.3.2",
"@six/concur-translator": "^1.0.9",
"botbuilder": "^4.22.0",
"botframework-connector": "^4.22.0",

[I566748]

comments: request: {
method: POST,
url: https://smba.trafficmanager.net/apac/v3/conversations/.../activities/...
},
response: {
body: '{"error":{"code":"BadArgument","message":"Failed to decrypt conversation id"}}',
headers: HttpHeaders { _headersMap: [Object] },
status: 403
},
body: {
error: {
code: 'BadArgument',
message: 'Failed to decrypt conversation id'
}
}

[qinezh]

If the notification installation doesn't match the bot ID or password, you can get a Failed to decrypt conversation ID error. One possible cause for this error is that the bot ID or password is changed.

You can resolve this issue by cleaning your notification storage and reinstall your bot in Teams to ensure the new installation is up to date.

Each stored notification installation is bound with one bot. If you're able to check your notification storage, its bot field should match the bot you're running such as the bot ID with the same GUID.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[microsoft-github-policy-service]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.