stevkan
commented
2 years ago @rmgitting - Thank you for reporting this. A couple questions:
- If you downgrade the BotBuilder packages to a previous build, does the error then go away?
- Do you specifically use Newtonsoft.Json in your project? If so, can you try aligning the version you use with the version used in the BotFramework SDK? Because of a new implementation on a recent version of Newtonsoft, some errors have been showing up when the versions don't align.
rmgitting
So basically I downgraded three libraries: bot.builder.AI.Luis, Bot.Builder.AI.QnA, and Bot.Builder.Dialogs.Adaptive.Runtime.
But the same problem persisted (only on Teams).
but I am not sure what version this is? and what version exists in the SDK, and how to align them.
Could you please give me more details about that.
Users588
Describe the bug
Hello, we are encountering a very weird thing happening on Microsoft Teams while working with the QnA Maker. We had a bot developed for a client. It was working fine this morning, nothing really changed. Other than an update to the different libraries used. The versions of the libraries are shown below:
We are using .NET 3.1
Then it started behaving weird when it comes to QnAMaker prompts. The last prompt, always gives this error:
As you can see when you click on the prompt, it gives:
Unable to cast object of type 'Newtonsoft.Json.Linq.JObject' to type 'System.Int64'.
This problem only occurs on Teams, on other channels such as web chat or emulator, it doesn't happen.
And on teams if you write the question yourself, then it will be fine, but if you click on the button it gives this error.
Then what we did is that we created a completely new bot, there is literally nothing in it other than a QnA Maker, as shown below:
So really nothing is there.
And we published this bot, and again the same thing happened. On teams, it is showing this weird error, on other channels, it is not.
We are testing on Teams through the link in the Azure portal, and it is not an option to create a teams app and link it to the bot at this stage, because the bot is deployed on a different tenant (client's tenant), and we are testing on our teams for now.
But my concern is that we always used to work this way, and even this morning, it was working just fine. The QnAMaker was working as expected in Teams.
So I don't know what changed, especially that we created a completely new project with only QnA.
Version
The version of the composer is v2.1.2 and I put the versions of the libraries above.
OS
We are deploying to an Azure App Service (I believe it is Windows)
To Reproduce
Just create a simple knowledge base on qnamaker.ai and create some questions with prompts. On the composer, only create a chatbot with QnAMaker dialog in the unknown intent, we dind't really do anything else. We deployed to Azure, and we used the Teams link in the channels to test. Again, we always do it like that, and it was working just this morning.
Expected behavior
To just go with the flow and execute the QnA Maker prompts naturally.
Additional context
I checked old bots that we have deployed a couple of days ago (on Teams), they are still working fine, now I am afraid if I publish again the QnAMaker will do the same on Teams.
Also there is this message that started appearing after pressing the QnAMaker buttons: "You response was sent to the app". as shown below:
this was not the case, and this is not the case in the other bots deployed a couple of days ago that are still working. They don't show this message, for example:
After clicking the QnA prompt, it just simply shows the right answer.
I am not sure if it is something related to us, or something twisted happened with Microsoft Teams.
Note: we tried to connect to other qnamaker KBs and also publish to other App Services, but it still gave the same error.
Appreciate your responses.