-
Notifications
You must be signed in to change notification settings - Fork 44
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
No response after conversation creation #2
Comments
Sorry you're having issues @Tigerdyret! This sample actually takes all messages and gives them a channelId of "emulator" which should be skipping any token checking. That said, I haven't tested the package with a C# bot, so I'll see if I can get one working. Did you change the websockets variable (in your directline instantiation in your webchat project) to false? Also, are you running the offline connector via the npm script command or through code? |
Hi @ryanvolum |
I have and it seems to be working for me! I just tested on the Echo Bot sample (crazy simple) and just had to update the hostname I passed into initializeRoutes to reflect the project I was hosting on. Sorry you're still having trouble - can you try with the EchoBot (in case your bot is somehow doing something above and beyond)? |
I'm having the same problem. |
Fixed it: Apparently you HAVE to specify a BotId in web.config. Still doesn't send system message though. The original emulator sends an initial "ConversationUpdate" message. This one doesn't. |
I use c# echo bot project. i got Autofac.Core.Resolving.ResolveOperation.Execute Error below, I use node echo bot project. The webchat won't get bot's echo message. Fiddler tool got 404 code from |
@ryanvolum Message is properly delivered to the bot but could able to retrieve the response. Not sure how it will work. Can you please guide me? |
Apologies for not keeping up with this. It seems that the C# SDK is making an OPTIONS call against /directline/conversations/:conversationId which the Node SDK is not. The resolution should be to create a new route in bridge.ts for app.options. I'll investigate further if I have the chance |
Is there any update on this? |
Hi Ryanvolum, As you mentioned in C# SDK there is a call the URL : http://127.0.0.1:3000/directline/conversations. |
Hi, thank you for a great library :-)
I'm running into an issue. I have:
When re-loading the WebChat component, I can see that your service creates a new conversation id with a random guid.
When sending a message via the WebChat, I can see via Fiddler that the message is correctly posted to your service (the activities endpoint), but it never responds and eventually times out.
I have also tried to replace my .NET Bot Webservice with a very simple Node.js Bot Webservice (the one from https://docs.microsoft.com/en-us/bot-framework/nodejs/bot-builder-nodejs-quickstart).
I can see that your service correctly post the message to the web service, but then I get the following error: "ERROR: ChatConnector: receive - no security token sent.". In the BotBuilder SDKs ChatConnector I edited the code to skip the token check:
And then the Bot Webservice (Node.js) replies correctly. This leads me to think that it's a security issue and since I do not have the source code for .NET BotBuilder SDK, I cannot skip the token verification, which means that I cannot use my .NET Bot Webservice and instead have to rewrite it to Node.js...
I hope you can help me :-)
The text was updated successfully, but these errors were encountered: