Skill
Typescript
I have a virtual Assistant connected to one skill, the skill is using the updateActivity function to render and update some adaptive cards to be shown in MS Teams. The UpdateActivity work well if I run the application directly from the skill, but as soon as I try it from the Virtual Assistant (this means that the VA routes the call to the skill) it crash with this error : Error: Http Request/Response model doesn't support UpdateActivityAsync call!
Error: Http Request/Response model doesn't support UpdateActivityAsync call!
at CalendarSkillAdapter.updateActivity (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-skills/lib/http/skillHttpBotAdapter.js:49:15)
at emit (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:262:79)
at emitNext (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:451:40)
at Promise.resolve.list.(anonymous function) (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:72)
at Array.context.onUpdateActivity (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/transcriptLogger.js:50:36)
at emitNext (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:51)
at Promise.resolve.list.(anonymous function) (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:72)
at Array.context.onUpdateActivity (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/telemetryLoggerMiddleware.js:60:36)
at emitNext (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:51)
at Proxy.emit (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:457:16)
Error: Http Request/Response model doesn't support UpdateActivityAsync call!
at CalendarSkillAdapter.updateActivity (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-skills/lib/http/skillHttpBotAdapter.js:49:15)
at emit (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:262:79)
at emitNext (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:451:40)
at Promise.resolve.list.(anonymous function) (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:72)
at Array.context.onUpdateActivity (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/transcriptLogger.js:50:36)
at emitNext (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:51)
at Promise.resolve.list.(anonymous function) (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:72)
at Array.context.onUpdateActivity (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/telemetryLoggerMiddleware.js:60:36)
at emitNext (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:449:51)
at Proxy.emit (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/botbuilder-core/lib/turnContext.js:457:16)
Trace
at Console.originalConsole.(anonymous function) [as trace] (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/node_modules/diagnostic-channel-publishers/dist/src/console.pub.js:42:39)
at DialogBot.turn (/Users/user/Desktop/project/GitLab/src/wa-meeting-skill/lib/bots/dialogBot.js:56:21)
at process._tickCallback (internal/process/next_tick.js:68:7)
Hi Tommy,
Thanks for raising the issue, yes - this (was/is) a limitation of using HTTP for Skill invocation and is one of the main reasons we had to move to the websockets approach for skill invocation using the Streaming Extensions.
We completed the C# work for this at Build and a couple of weeks ago got the js version bits which we are actively integrating as we speak. This, like with the c# variant will enable you to use update activities especially for Teams scenarios as you highlight.
Working on a timescale to have the bits this week, will leave this open so we can provide an update to a daily build that you can test in the not too distant future.
Hi @darrenj,
Thanks for the update. Would be great if you could keep me update on the Typescript enablement.
:)
Hi @darrenj,
Do you know if the library has been released ?
I'll update this issue once we have the changes integrated.
Work is tracked here and targeting next release. Please keep an eye on the issue and we'll point at daily builds when available.
@darrenj Cool thanks.