[BUG] Send button on adaptive card broken about adaptivecards HOT 15 OPEN

Hi @sschoeb and @sueess, this issue should be filed with the Teams team directly. I can find contact info for you if you need :)

from adaptivecards.

@anna-dingler pinging you as this bug/issue makes an adaptivecard within a bot completely useless. As we see customers having 80 to 100% of the time issues with these actions, I would consider that somehow urgent. I hope your team can find time to look into it (or at least guide us to another place to report that issue, if this repository should be wrong).

from adaptivecards.

Additional information:

• We do not see any error in Azure Bot services, which relate to that problem.

from adaptivecards.

@anna-dingler thank you very much, a contact info would be great :-)

from adaptivecards.

@dclaux Do you have a contact here?

from adaptivecards.

@dclaux / @anna-dingler we found an additional (maybe important) information:

Having my own teams which is working, I could see that my invoke request looks like this:

{
   "name":"messageback",
   "messageType":"RichText/Media_Card",
   "value":{
      "sendText":"Falsch"
   },
   "imdisplayname":"<display name>",
   "userAadToken":"<token>",
   "serverMessageId":"1712326154213",
   "clientMessageId":"13250346427536952513",
   "conversation":{
      "id":"<id of the conversation>"
   }
}

What we can see here is, that in my (working) environment, teams does send additionally a conversation with an id. (which in my understanding also makes sense). This information is missing in the request we have above where we get a "Invalid JSON" back from the backend.

Do you need any further information on this? I could link you with our customer where we can 100% reproduce this issue if you need a real example.

Edit: I double checked the HAR-file I got from our customer and there I can see that requests to the /invoke-endpoint with the conversationId do work and all the requests without a conversationId do fail. Sadly most of the time teams does not send this conversationId!

from adaptivecards.

@sueess, As previously mentioned, the solution will not involve AdaptiveCards (AC), since AC does not manage the communication between the hosting application that utilizes AC and the bot. It would be best to contact the teams that can directly address your issue.

from adaptivecards.

@jwoo-msft thank you very much for the proper tagging. May I ask you for a response if the report here is where it should be or if we should report this kind of issue somewhere else?

As from the 1 of april on based on your teams rollout policy the new teams client will be the default client, we consider this as urgent, as we expect to see this issue on way more of our customers. Would be great if we could at least find the correct place to report the issue and of course we would highly appreciate if someone could even look at it.

from adaptivecards.

@anna-dingler thank you very much for the link!

@dclaux Sorry for pushing, but a contact or any feedback on that would be great, as the new teams version is default since yesterday our first customers start to move away from using teams but the web version instead (which is an absolute downgrade, but as teams is absolutely unusable the only workaround :/).

from adaptivecards.

Is there any progress on that one? We are getting more and more reports of users for which the bots a completely not working. Is there any place to report issues like that? I guess it must be also in the interest of Microsoft, that the bots start to work reliable with the new Teams version.

from adaptivecards.

@jwoo-msft Thanks for your reply.

We would love to contact the teams that can directly address the issue, but we just do not know how - any link to a person would be very much appreciated. Or is there another place to report that bug?

from adaptivecards.

@jwoo-msft I understand your point. However, isn't it also in your interest, that the stuff you guys develop is at the end working? What is a nice train on broken rails? We are more then eager to report the issue at the right place, but so far nobody could give us any hint, how to reach a responsible person.

We would really appreciate a contact, to reduce the pain of "our" customers and the users. I guess we would all be happy about that. Many thanks for some directions!

from adaptivecards.

Dear @jwoo-msft @dclaux @anna-dingler - I understand, that we are in the wrong repository here. But it is super hard to figure out where to report these kind of bugs? We tried multiple repositories, we tried our support on azure (which does not care to much about teams).. so it would be great if you could give us any hint on where we should go next with this one. Is there any support plan where we could get access to someone who cares about bug reports? Or any other option?

from adaptivecards.

@sschoeb the issue should now be fixed in Teams. Are you still able to repro in Teams web/desktop?

from adaptivecards.

@dclaux No we do currently not see this error on any of our clients. But as we never had a feedback and the bug also before was not consistent we were not sure if it was fixed or not. But these are great news - thank you very much for your fixing the issue and also the update in here!

As a last question: As you may have seen in this report here, we are having a hard time reporting these kind of bugs to Microsoft. We wonder if this what we are doing here is the way to go or if you would recommend to contact Microsoft somehow else?

from adaptivecards.