Search code examples
botframework

Azure Bot Services templates - botFilePath / botFileSecret fields are missing (Node.js / SDK v4

After using the Azure templates for Basic and Echo bot (Node.js SDK v4) the resources are created and testing the bots via the online WebChat in the Azure portal works fine.

In the application settings, however, the botFilePath and botFileSecret are not visible (only MicrosoftAppId and MicrosoftAppPassWord). After downloading the source code, I noticed that the .env file is created with MicrosoftAppId and MicrosoftAppPassWord.

Any thoughts anyone?

Solution

  • botFilePath and botFileSecret aren't included because the newer Echo and Basic bots don't have .bot files. We're moving away from using them in all BotBuilder SDKs. It will take some time for all of the samples, documentation, and emulator to reflect this. All secrets and settings should be stored in .env (Node) or appsettings.json (C#).

    If you need to test your downloaded bot with the Emulator (for now):

    1. Open Emulator (note: you likely need the latest version)
    2. Click Open Bot

    enter image description here

    1. Add the bot URL (usually http://localhost:3978/api/messages) and click Connect enter image description here

    Note: Leave App ID and App password blank and remove it from your .env file for local testing. Be sure it's in your App Settings when deploying (it should stay there, by default, when you re-deploy/publish).