Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

500 Error when changing AppId/Pass. Requires Emulator restart.

See original GitHub issue

I’ve seen this happen before, too.

Version

4.4.1-60043 (although I’m fairly certain this isn’t new)

Describe the bug

In order for a change to MicrosoftAppId / MicrosoftAppPassword to take effect in the Emulator, the whole Emulator application must be restarted, not just the opened bot or the “Live Chat” window. I have a feeling this is tied to caching it for an endpoint, but I haven’t tested different endpoints.

This can be a problem in the following scenarios:

Having a typo in appId/pass and then trying to change it. It will appear to never work unless user restarts Emulator
Testing a local bot with and without an appId/appPass
Testing multiple bots on the localhost endpoint
Needing to change the password while testing – maybe user accidentally uploads to repo

To Reproduce

Get two valid AppIds/AppPasswords. I’ll refer to them as AppA/PassA, AppB/PassB.

FAIL:

Start a bot with AppA/PassA set in appsettings.json
Connect to the bot in Emulator using Open Bot, using AppA/PassA
Stop the bot
Change the bot to use AppB/PassB in appsettings.json
Close Live Chat window in Emulator
Open Bot in Emulator with AppB/PassB
Receive 500 Error
Close Emulator entirely
Open Bot in Emulator with AppB/PassB
Success

SUCCESS:

Start a bot with AppA/PassA set in appsettings.json
Connect to the bot in Emulator using Open Bot, using AppA/PassA
Stop the bot
Change the bot to use AppB/PassB in appsettings.json
Close Emulator entirely
Open Bot in Emulator with AppB/PassB
Success

Expected behavior

Opening a new Bot session in Emulator should not use an old AppId/AppPassword.

Additional context

I’ve tested various ways of stopping/restarting the bot and with/without ngrok. Pretty sure this is an Emulator issue.

The completely breaks in C#, presenting the 500 error and then not connecting. In Node, it seems to first try to connect with the old AppId/Pass, but then tries to connect with the new one and works. See image:

Note that when connecting in Emulator, I used 94ea2b04-ccba-437e-b3f1-3f0376fcbc98. It showed the error in console, but actually worked in the Emulator.

[bug]