microsoft / botframework-sdk

Bot Framework provides the most comprehensive experience for building conversation applications.
MIT License
7.48k stars 2.44k forks source link

[Direct Line] Chatbot only fully works on Bot Framework Emulator? #3866

Closed fms-santos closed 6 years ago

fms-santos commented 6 years ago

Bot Info

Issue Description

As of today (Dec 4th, 2017), my Azure App deployed chatbot only appears to be working correctly on the Bot Framework Emulator. On every other channel that I have connected, the bot keeps sending the welcome card (default dialog "/") everytime I try to send it a new message.

Code Example

Just send a type message to the bot and it goes back to the default "/" dialog.

Reproduction Steps

  1. Say something to the bot
  2. Bot keeps going back to the "/" dialog on every channel besides Emulator

Expected Behavior

The bot should proceed with the analysis and show the correct answer like in the emulator as in the picture below. Expected behavior

Actual Results

The results on the directline channel are shown below. Wrong Behavior

pascalrijk commented 6 years ago

I have the exact same problem! I got an 500 error when I'm trying send an activity to my chatbot (postman) with Direct Line. I am using .NET btw!

fms-santos commented 6 years ago

@pascalrijk I have the same error on other bot as well. This one also works on Skype directly.

pdpferreira commented 6 years ago

I'm having the same problem here.

JasonSowers commented 6 years ago

@pascalrijk @pbonder can you please provide app IDs?

pdpferreira commented 6 years ago

App ID: 6cd7cd5b-47ad-40a8-a319-9dd7846977b7 The SDK Platform is also in Node.js

JasonSowers commented 6 years ago

@fms-santos @pascalrijk @pbonder Are your bots using the default state store or have you implemented a custom state store.

Additionally, Are any of you able to capture the JSON your bots are receiving and responding to? If so please post it in this thread.

fms-santos commented 6 years ago

@JasonSowers I'm using the default. My bot is working now. I can enter the dialogFlow and it's not stuck anymore.

pdpferreira commented 6 years ago

Using the default, my bot is still answering the first dialogFlow.

JasonSowers commented 6 years ago

When testing your bot in the portal @pbonder I am seeing the following dialog flow. Is this the intended dialog flow or not?

image

pdpferreira commented 6 years ago

the correct flow is this one. It seems that everytime I input something on the keyboard it goes back to the "/" dialog. On the emulator it does the right thing. Also last friday everything was working fine

untitled

JasonSowers commented 6 years ago

it would help us tremendously if you could capture the JSON your bot is receiving and responding to.

pdpferreira commented 6 years ago

from the emulator?

From user to bot: { "type": "message", "text": "1007796", "from": { "id": "default-user", "name": "User" }, "locale": "en-US", "textFormat": "plain", "timestamp": "2017-12-04T17:43:46.039Z", "channelData": { "clientActivityId": "1512409416434.13233502048924928.0" }, "entities": [ { "type": "ClientCapabilities", "requiresBotState": true, "supportsTts": true, "supportsListening": true } ], "id": "jndjnlm5f1i8" }

From bot to user: type": "message", "text": "Login feito com sucesso ✔️", "locale": "en-US", "localTimestamp": "2017-12-04T17:43:46+00:00", "from": { "id": "default-bot", "name": "Bot" }, "recipient": { "id": "default-user" }, "inputHint": "ignoringInput", "id": "km6dfk3aaja4", "replyToId": "jndjnlm5f1i8", "channelId": "emulator", "timestamp": "2017-12-04T17:43:46.564Z", "conversation": { "id": "k0nc6h9hh3k8" } }

JasonSowers commented 6 years ago

directline

pdpferreira commented 6 years ago

I'm using Skype Web Control. How can I capture JSON from directline? Thanks

JasonSowers commented 6 years ago

Apologies, I thought you were using directline as well

fms-santos commented 6 years ago

@pbonder I have another bot using Skype and some userData. I've changed to cosmosDB storage and now it's working again.

JasonSowers commented 6 years ago

closing this issue please refer to #3870 for more information