microsoft / microsoft/AdaptiveCards

[Rendering] Mentions break on refresh action (manual trigger)

Open
#8,832 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Renderers Bug
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Target Platforms

NodeJS

SDK Version

2.10.0

Application Name

Microsoft Teams

Problem Description

Mentions break on refresh action. 'userIds' are included in the refresh in this case, and refresh action is triggered using manual trigger. The initial card renders correctly.
To reproduce the issue,

  • Define a card where users are mentioned
  • Add 'refresh' action to the card
  • Send the card to a Teams channel through the bot
  • Trigger refresh action manually
  • Observe the @ tags in the card
Screenshots

image

Card JSON
{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.5",
  "type": "AdaptiveCard",
  "body": [
    {
      "type": "TextBlock",
      "text": "<at>User1</at>, <at>User2</at>"
    }
  ],
  "msteams": {
    "entities": [
      {
        "type": "mention",
        "text": "<at>User1</at>",
        "mentioned": {
          "id": "8:orgid:<EntraId>",
          "name": "User1"
          "aadObjectId": <EntraId>
        }
      },
      {
        "type": "mention",
        "text": "<at>User2</at>",
        "mentioned": {
          "id": "8:orgid:<EntraId>",
          "name": "User2"
          "aadObjectId": <EntraId>
        }
      }
    ]
  }
}
Sample Code Language

No response

Sample Code

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the provided Adaptive Card in Microsoft Teams using the manual refresh action, then trace the rendering path for msteams mention entities and refresh handling. Confirm the initial render and refreshed render use the same userIds and that both User1 and User2 remain displayed as mentions.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.