Messaging Endpoint Form Payload Issue

[Bytezart]

Discussed in #1030

^{Originally posted by Bytezart November 7, 2023}
I'm running into problems with the Azure Bot Service's messaging posts to the sampe TeamsMessagingExtensionSearch project. It appears as though I have the correct AppID's, Passwords and AppTypes set correctly. Specifically, the HTTP post the messaging endpoint doesn't appear to have any form data and is not being flagged as having a HasFormContentType by the runtime.

In the debugger screen shot below I'm sending a message through a Teams Channel for the Azure Bot Service.

[ChetanSharma-msft]

Hello @Bytezart - Thanks for raising your query.
Kindly share more information and sample code, if you have any, so that we can try to repro it.

[Bytezart]

Sure. Fortunately, and speaking to the code snippets, the code I'm using is unaltered from the main Microsoft-Teams-Sample main branch in the TeamsMessagingExtensionSearch project. Obviously, AppSettings were swapped out for my environment though.

As for the messaging integration flow: Teams Extension => Azure Bot (Teams Channel) => Microsoft Dev Tunnels => Visual Studio 2022.

To reproduce the issue I'm simply initiating an interaction with the Teams Search Extension which is ultimately causing a POSTto my running code as denoted below. In the debugger screenshot you can see the request's form post data is causing an exception preventing me from handling the request.

[BasetsanaNjody]

Feedback?

[Meghana-MSFT]

We are also able to repro this issue, we will check this internally and get back to you. Thank you.

[Bytezart]

Please note that this issue did not prevent me in the end from running the application. I had other problems that made this appear to be the source of my problems but it was not. It does appear to be benign in nature.

[Meghana-MSFT]

We have raised a bug for this, we will update here once we have any update.

[BasetsanaNjody]

@Meghana-MSFT are you still unable to repro the issue? As I had asked for feedback 2 weeks ago!

[Meghana-MSFT]

We are also able to repro this issue, we will check this internally and get back to you. Thank you.

We already had a repro for this issue and raised a bug for the same.