-
Notifications
You must be signed in to change notification settings - Fork 503
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
Sending proactive message example fails (+fix) #11461
Comments
Hi ChetanSharma-msft! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies. Best regards, Teams Platform |
@roeeoz - Thanks for reporting your issue. Could you please check and confirm this? |
Steps to reproduce
Copied bug from: OfficeDev/teams-toolkit#12206
Details from original post:
Describe the bug
This line fails with both in test tools and in Azure due to process.env.MicrosoftAppId being undefined
//await adapter.continueConversationAsync(process.env.MicrosoftAppId, confRef, async (context) => {
Changing to this line works at least on local.
await adapter.continueConversationAsync(
new ClaimsIdentity([], true),
confRef,
async (context) => {
await context.sendActivity("proactive hello");
}
);
Does this fix makes sense? Or do I need to change something else?
roee.oz<>microsoft.com
Expected behavior
Changing to this line works at least on local.
await adapter.continueConversationAsync(
new ClaimsIdentity([], true),
confRef,
async (context) => {
await context.sendActivity("proactive hello");
}
);
Actual behavior
This line fails with both in test tools and in Azure due to process.env.MicrosoftAppId being undefined
//await adapter.continueConversationAsync(process.env.MicrosoftAppId, confRef, async (context) => {
Error details
No response
The text was updated successfully, but these errors were encountered: