Botframework-sdk: [Skype Web Control] Wrong behaviour when using dialogAction button

[fms-santos]

Bot Info

• SDK Platform: Node.JS
• SDK Version: 3.14.0
• Active Channels: Skype, SWC
• Deployment Environment: Azure App Service
• App-ID: 6cd7cd5b-47ad-40a8-a319-9dd7846977b7
• SWC SDK: https://swc.cdn.skype.com/sdk/v1/sdk.min.js

Issue Description

My bot is deployed both in Skype and in Skype Web Control. When using Skype Web Control version, users get the wrong behavior when clicking in dialogAction buttons.

Code Example

exports.createWelcomeCard = function (session) {
    var welcome = new builder.HeroCard(session)
        .title('Olá!')
        .subtitle('Pretende aceder à sua área pessoal?')
        .text('Na área pessoal poderá consultar o estado das suas faturas.')
        .images([
            builder.CardImage.create(session, 'xxx')
        ])
        .buttons(
        [
            builder.CardAction.dialogAction(session, "access_login", "", "Sim "),
            builder.CardAction.dialogAction(session, "get_goodbye", "", "Não ")
        ]);
    return welcome;
};

Reproduction Steps

1. Talk to bot
2. See Welcome Card
3. Click "Sim"
4. Expected behaviour shoud be a prompt "Por favor indique-me..." but when in SWC the welcome card shows up again

Expected Behavior

The image below shows the expected behaviour as seen on the Skype App.

Actual Results

When in Skype Web Control (SWC), the bot always shows the same welcome card after clicking "Sim" or "Não".

[fms-santos]

Any news on this issue ? @JasonSowers ?

[JasonSowers]

Just getting to this now sorry for the delay, Can you please share your code that handles the clicked responses?

[fms-santos]

@JasonSowers sure, no problem. So, after clicking "Sim" ("Yes") the dialog flow is as follows:

bot.beginDialogAction('access_login', 'login'); which will trigger the "login" dialog:

// Login message flow bot.dialog('login', [ function (session) { session.beginDialog('askNif'); }, function (session, results) { // All EU VATs accepted var nif = results.response.toUpperCase(); session.sendTyping(); api.login(nif) .then(result => { // Save user variables to TableStorage session.userData[config.tableStorage.nif_key] = result[0].nif; if (result.length === 1) { session.beginDialog('homepage'); } else { session.beginDialog('retryNif'); } }).catch(err => { if (err.error === 'No NIF') { session.beginDialog('retryNif'); } else { errorHandler(err, session); session.beginDialog('/'); } }); session.endDialog(); } ]);
This dialogflow is basically the same for all buttons and works pretty well in the Skype App and in the emulator.

[fms-santos]

@JasonSowers any news? We want to deploy this chatbot to our clients in SWC but right now it doesn't seem the best thing to do. Getting a bit worried about the stability of SWC as it's not the first time this kind of issues happen to me.

[fms-santos]

@JasonSowers anything? My bot is still not working properly on SWC...

[EricDahlvang]

Hi @fms-santos

Please share the code you use to show this welcome card. Is it in response to an event, or response to a user's message?

[fms-santos]

Here you go. It's basically the root dialog. When a user first writes anything to the bot, the bot goes to:

//Root Dialog 
bot.dialog('/', [ function (session) {
 if(session.userData[config.tableStorage.supplierID]) { 
session.beginDialog('homepage');
 } 
else { 
var welcome_card = cards.createWelcomeCard(session); var welcome_msg = new builder.Message(session).addAttachment(welcome_card); 
session.send(welcome_msg); } } ]); 

I must emphasize again that everything works as expected on the Skype app for Windows, iOS, Android and also on the emulator and web chat.

[renebrandel]

@fms-santos we're looking into the issue now! Do you have a test page where we can try this bot?

[fms-santos]

Yes, I do have. http://mockedpinfospot.azurewebsites.net/

[fms-santos]

@brene @JasonSowers I still can't pass through the first welcome card. Can you please check on your side? It has been a couple of days now.
I can't really rely on deploying this to the final client. It's really a shame...

[renebrandel]

@fms-santos we're still trying to figure out what's wrong and what's the difference between our implementation and the native Skype client. Sorry for the inconvenience.

[fms-santos]

any updates on this issue @brene ?

[fms-santos]

Hey @brene and @JasonSowers , I was wondering if this issue is still being solved or at least taken into account.

[JasonSowers]

@fms-santos I cannot speak for @brene and his team but I will reach out and see what I can find out.

[JasonSowers]

@fms-santos I was waiting for the SWC team to respond, but you have been waiting forever on this issue. They have put bot related development on the back burner for the time being so I would not count on this being fixed anytime soon. I have no timeline or information other than that, unfortunately.

[fms-santos]

Ok thank you @JasonSowers . That's a shame.

[amitbend]

@brene @JasonSowers This is a serious bug in the functionality of SWC I really hope they will take the time to fix it soon.

[fms-santos]

I must agree with you @amitbend :(

[amitbend]

@brene @JasonSowers @GKulshrestha We are still waiting for a fix, can we push it somehow?

[JasonSowers]

At this time there is no new information or timeline I have for you. I do hope this gets addressed and will continue to poke around about it periodically. Unfortunately, it's not something in our code base that we could just fix for you guys.

[amitbend]

@JasonSowers thanks Jason, I really hope your pokes will work eventually.

[JasonSowers]

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.

From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.

As part of this restructuring, we are closing all tickets in this repo.

For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues

For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues

For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework

Thank you.

The Bot Framework Team