Function bots don't pick up LUIS app ID

[Virtual-Josh]

Describe the bug

Function bots do not appear to pick up the LUIS app ID from app settings despite the data being populated in the field.

Version

Version: 2.0.0-nightly.240366.4a6ec2c
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

Browser

• Electron distribution
• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:
0. Make sure you have the Azure core tools installed

1. Create a .net function bot
2. Create a provision for the bot
3. Create an intent
4. Publish the bot
5. Start the bot and try to invoke the intent

Expected behavior

You shouldn't be able to start the bot without adding the LUIS info

Screenshots

App settings standard view:

App settings advanced view:

Additional context

In the web app version Composer will have an error saying you can't start the bot without updating the LUIS data. I don't know if that check is missing here, or if something else is going on.

[Virtual-Josh]

This repos in the current nightly version: 2.0.0-nightly.241057.db66154

[sgellock]

Shiproom - @peterinnesmsft once you have a PR, lets discuss. feels like a must have, but want to talk through the fix before I approve.

[peterinnesmsft]

As I am OOF 4/30, assigning to @tracyboehrer to take over further investigation.

Using the same nightly version of Composer specified above (v2.0.0-nightly.241057.db66154), as well as the latest Empty Bot template for .NET Functions (@microsoft/generator-bot-empty@1.0.0-rc8), I am unable to get as far as described in the repro steps due to numerous Composer bugs that are inhibiting progress.

It is worth noting that, prior to attempting to create a publishing profile or make any modifications to the bot immediately after creation, running the bot locally works as expected. It is when the additional dialog and the LUIS utilization come into play that issues start manifesting.

Following the repro steps, I created a new Echo dialog and added the intent trigger to my root dialog following the initial provisioning of my resources.

Two prevalent issues I have encountered thus far in just simply trying to get the bot with the added dialog published:

1. Attempting to publish the bot to my provisioned Azure environment hangs on attempting to upload the .zip to my Azure Functions resource.
2. Attempting to connect my LUIS resource to my bot simply doesn't work (i.e. Project settings > Development Resources > Language Understanding > Get LUIS Keys > Choose from existing > Next button does nothing).

It does appear that a LUIS application is getting created, but I am finding I have to manually go to the luis.ai portal and copy over the missing authoring key, as well as specify the region.

Attempting to run my bot locally after this, I am getting an HTTP 500 on calls to the api/messages endpoint, and see the following logs in the console output:

[4/30/2021 12:15:19 AM] Executing HTTP request: {
[4/30/2021 12:15:19 AM]   requestId: "ff2cfc5f-e237-49de-b838-d3ad8bde8ca7",
[4/30/2021 12:15:19 AM]   method: "POST",
[4/30/2021 12:15:19 AM]   userAgent: "axios/0.21.1",
[4/30/2021 12:15:19 AM]   uri: "/api/messages"
[4/30/2021 12:15:19 AM] }
[4/30/2021 12:15:19 AM] Executing 'messages' (Reason='This function was programmatically called via the host APIs.', Id=bc030219-2d20-4ea5-9228-960407a80b24)
[4/30/2021 12:15:19 AM] Executed 'messages' (Failed, Id=bc030219-2d20-4ea5-9228-960407a80b24, Duration=40ms)
[4/30/2021 12:15:19 AM] System.Private.CoreLib: Exception while executing function: messages. Microsoft.Bot.Connector: Could not load file or assembly 'System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.
[4/30/2021 12:15:19 AM] Executed HTTP request: {
[4/30/2021 12:15:19 AM]   requestId: "ff2cfc5f-e237-49de-b838-d3ad8bde8ca7",
[4/30/2021 12:15:19 AM]   identities: "",
[4/30/2021 12:15:19 AM]   status: "500",
[4/30/2021 12:15:19 AM]   duration: "170"
[4/30/2021 12:15:19 AM] }

There appears to be an issue with an expected dependency on System.IdentiyModel.Tokens.Jwt being triggered in Microsoft.Bot.Connector. It should be noted that I added my Microsoft App ID and Password using the 'Add from publishing profile' option after manually entering my LUIS details.

To the particular error that was originally surfaced ("" is not a valid LUIS application id.), this comes from the LUIS recognizer settings that are generated by Composer and placed into the generated folder. We should verify that the application ID is indeed present in the file - if not, that's most likely the culprit to that particular issue. Otherwise, if we can confirm that publishing to Azure Functions includes that particular file in the expected location, then it is likely to be a runtime issue in being able to read in that file and add it as a configuration source.

[tracyboehrer]

For the "System.Private.CoreLib: Exception while executing function: messages. Microsoft.Bot.Connector: Could not load file or assembly 'System.IdentityModel.Tokens.Jwt" issue, add the following to the csproj:

  <PropertyGroup>
	<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>
  </PropertyGroup>

[tracyboehrer]

Also, the function project is not including the LUIS config located in generated, nor the appsettings.development.json.

That too requires csproj changes to include those in the build.

[tracyboehrer]

With the above two comments applied to the csproj, the bot will function correctly locally (in the Azure Function Emulator). Assuming the app id, password, and LUIS settings are put into appsettings.development.json.

Having a different issue when deployed.

[tracyboehrer]

On Azure, am now getting an error:

System.Private.CoreLib: Could not load file or assembly 'DotnetFunctions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.

"DotnetFunctions" is the name of my project.

[tracyboehrer]

Moving this issue to Components and opening another P0 for Composer.

This is a two part issue:

1. What this issue refers to is resolved by csproj changes.
2. There is a second issue where the Azure resource is created at 32-bit, but the deploy build appears to be using 64-bit. The Function will not run until the resource is manually switched to 64-bit.

[tracyboehrer]

microsoft/BotFramework-Composer#7538

[sgellock]

Shiproom - @benbrown can you work the build issue?