You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 20, 2024. It is now read-only.
When a bot sends a message to a user from within a dialog (convo), the user value appears to be missing from the message (at least when using the botbuilder-adapter-web).
In fact, in printing out the message out for debugging purposes, this is what shows up:
{ type: 'message',
inputHint: 'acceptingInput',
suggestedActions: { actions: [ [Object], [Object] ] },
text: 'Should we resume the previous chat or start a new one?',
channelData: { quick_replies: [ [Object], [Object] ] } }
As you can see, neither the 'user' nor the 'recipient' fields are available (each of them would give us useful user information).
Needless to say, send middleware is unable to do anything useful with this information, so I believe this is actually a bug. I noticed that there are a couple of prior, related issues created by @cbouvard : #2030 and #2043. I'm hoping that #2043 can actually resolve this issue, as it stores the 'user' value in convo vars, but it is awaiting a review since September. It would be great if somebody could please verify that this is actually a bug, and also review the submitted PR in #2043 in order to fix it . Better still, it would be best to have a solution that does not depend on the bot asking the user for their name during the interaction (so that it can be stored in the convo vars), as access to the 'user' value should be a given within send middleware.