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
Bot Emulator PostBack #1140
Comments
This is related to, or a duplicate of #1134 |
@justinwilaby this does not appear to be a dupe of #1134. This is more of a behavioral issue with the PostBack card action. When emulator responds with postback, the actual message value should not be rendered on the canvas; however the message is rendered to the user the first time the button is clicked. I have a repro set up here -
Expected: Emulator does not show 'hi' as message sent from user Note that subsequent times you click on '[Post Back] hi' does the right thing and does not render user's message on the canvas. |
fixes #1140 - postback messages showing up in webchat
I am using v3.15.2.2 and I just noticed this problem. 3.15 was released 8 months ago! I wonder, how this problem went unnoticed for so long? Will there be a fix for v3 too? |
Version
Emulator: 4.1.0
SDK: NodeJs V4.1.5
Description
In response to this StackOverflow question, I created a simple bot with the NodeJs V4 SDK that responds to a user's message with a Hero Card. The card has two action buttons: a PostBack and an ImBack Action. The first time the user clicks the PostBack action in a new conversation the emulator sends the value of the action as a message from the user; however, all subsequent times the user selects the PostBack action, it does not send the value as a message. I also deployed this bot to the WebChat channel where everything worked as expected. Consequently, I suspect this is an issue with the emulator.
Code
onTurn Function
Hero Card Helper Function
Expected behavior
PostBack Actions are not supposed to send a visible message from the user in the emulator channel; however, one is being sent the first time a PostBack action is invoked.
Screenshots
The text was updated successfully, but these errors were encountered: