在 MS Teams 桌面应用程序中使用 ToggleVisibility 操作时自适应卡发送错误消息

Question

This morning we started getting the standard bot error message in MS teams desktop client when using a card with toggleVisbility actions. Selecting the button to toggle visbility on part of the card results in the below error, even though the toggle works as expected!

bot error message

The adaptive card code looks something like this:

{
                    "type": "ActionSet",
                    "actions": [
                        {
                            "type": "Action.ToggleVisibility",
                            "title": "Alerts",
                            "targetElements": [
                                "Incidents",
                                {
                                    "elementId": "Metrics",
                                    "isVisible": false
                                },
                                {
                                    "elementId": "Admin",
                                    "isVisible": false
                                }
                            ]
                        },
                        {
                            "type": "Action.ToggleVisibility",
                            "title": "Actions",
                            "targetElements": [
                                "ActionButton"
                            ]
                        }
                    ]
                }

This message would be expected if the bot app doesn't respond to a message/action, however the toggle action shouldn't be sending any data to the bot applicaiton. I confirmed this in the teams web client using the network tracing dev tool. When selecting the toggle action no new network calls are made.

We are not seeing this error in either the web client or the mobile client, only in Teams Desktop app.

This bot has been running for months without this issue and we didn't change the code, which makes me believe this is a MS teams side bug that was recently introduced.

Answer 1

Also: This same issue was independently identified in the Adaptive Cards Project. https://github.com/microsoft/AdaptiveCards/issues/8145