Adaptive Cards on Android are blank when "ActionSet" is added

Copper Contributor

I'm trying to post an Adaptive Card to Teams, and it works fine in the browser, Mac client, and iOS.  In the Android Teams client, however, it's just blank white space.  Here's the json:

 

 

{
  "type": "AdaptiveCard",
  "body": [
    {
      "type": "Container",
      "style": "default",
      "items": [
        {
          "type": "TextBlock",
          "text": "Welcome User!",
          "size": "Small",
          "spacing": "Small",
          "weight": "Lighter"
        }
      ]
    },
    {
      "type": "Container",
      "style": "default",
      "items": [
        {
          "type": "ColumnSet",
          "columns": [
            {
              "type": "Column",
              "width": "stretch",
              "items": [
                {
                  "type": "Input.Text",
                  "placeholder": "Info",
                  "spacing": "Small",
                  "id": "my_info"
                },
                {
                  "type": "TextBlock",
                  "text": "50 characters max",
                  "horizontalAlignment": "Left",
                  "size": "Small",
                  "weight": "Lighter",
                  "spacing": "None"
                }
              ]
            }
          ],
          "spacing": "Small"
        },
        {
          "type": "Container",
          "items": [
            {
              "type": "ActionSet",
              "actions": [
                {
                  "type": "Action.Submit",
                  "title": "Submit ➝",
                  "style": "positive",
                  "id": "submit_btn"
                }
              ],
              "id": "action_set_submit"
            }
          ]
        }
      ]
    }
  ],
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.0"
}

 

 

 

 

If I remove the "ActionSet" block, it works fine. Is that feature not yet supported on Android? And are there plans to add it?  Thanks! 

1 Reply

@Terry550 Thanks for reporting this issue. We could repro it and we have raised a bug for this and we are tracking it internally.