Error 400 when using open bot with AppId+Password
See original GitHub issueVersion
4.3.3 on MacOS
Describe the bug
I created an echo bot using the yeoman generator following this doc, but I was unable to test the locally hosted bot in the emulator using the open bot with URL (+ AppID and password) feature. This bug only exists when we add an AppId and Password to the local bot. I got that AppId and Password from a newly created ABS Web App Bot. The workaround to this problem was to create a .bot
file with the local endpoint, AppId and Password.
To Reproduce
Steps to reproduce the behavior:
- Follow this doc to create a bot locally.
- Follow this doc to create Web App bot to gather an appid and password
- Deployment is optional
- Add AppId and Password to
.env
of my yeoman generated bot that is hosted locally. - Open the emulator and click on Open Bot
- Enter my localhost endpoint, AppId and Password
- Say
hi
or anything to the bot - ends with a
400 directline.postActivity
issue
Expected behavior
This should just work out of the box as it does with a local bot without an AppId and Password.
Additional context
The work around to this problem was to create a new bot configuration file, add the endpoint, AppId and password. Save the file and then talk to the bot. This worked fine, but took us a while to figure this out.
[bug]
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top GitHub Comments
@stevengum was able to reproduce. we’ll be taking a work item to continue the thread. cc @justinwilaby
hi @ovishesh & @brandonh-msft. we will take a look at this. thanks