Botframework-emulator: Emulator does not render valid adaptive card in an activity

Created on 30 May 2020  ·  7Comments  ·  Source: microsoft/BotFramework-Emulator

Version of emulator: 4.9.1

The below activity has a valid adaptive card that renders properly in adaptivecards.io. In emulator it looks like the below. It seems related to having a curly bracest in the string value. If I change it to obj= and remove the trailing curly brace it works fine.

In emulator (wrong):
image

In adaptive cards designer (right):
image

Activity:

{
    "type": "message",
    "attachments": [
        {
            "contentType": "application/vnd.microsoft.card.adaptive",
            "content": {
                "type": "AdaptiveCard",
                "version": "1.0",
                "body": [
                    {
                        "type": "TextBlock",
                        "text": "simple",
                        "size": "large"
                    },
                    {
                        "type": "FactSet",
                        "facts": [
                            {
                                "title": "due",
                                "value": "{timex: [2020-06-01], type: date}"
                            }
                        ]
                    }
                ],
                "$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
            }
        }
    ]
}
Bug

All 7 comments

We should test this in Web Chat.

Possibly related to Web Chat bug #3165

This is still an issue. This:
image
Renders as this:
image

I just tested this with the latest Web Chat and the bug is still present in 4.10.0.

The issue (https://github.com/microsoft/BotFramework-WebChat/issues/3165) has been labeled for R11 and can be tracked there.

This was not fixed in R11 or R12. Is it ever going to be fixed?

@chrimc62 this is a Web Chat bug so it will be present in Emulator until it is fixed in Web Chat. If you look at https://github.com/microsoft/BotFramework-WebChat/issues/3165 you can see that it was moved into the R13 milestone last week.

In progress now - sorry @chrimc62 for the wait. Low on manpower haha.

Was this page helpful?
0 / 5 - 0 ratings