You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adaptive Card with actions using mode=secondary do not open a menu on Android in Teams Task Dialogs. To reproduce create a staticTab with contentUrl, open a teams with example javascript. Works as expected on web/desktop/ios, only Android issue.
Use example card below. Open in Android and observe non-functional behavior shown in video.
@boog - Could you please confirm if my understanding is correct that the card having secondary actions doesn't work when the card is shown inside a task module? Issue happens only on Android.
@Meghana-MSFT yes that is correct, I tried a simplified card with only a secondary action and a few different types of actions etc using adaptive cards 1.4-1.6 and I was not able to get any to work as expected on Android in the Microsoft Teams native app. The button appears as [...] but nothing happens when you click it (as shown in video). Interestingly, secondary actions work as expected on Android when using a custom renderer in a staticTab iframe using the JavaScript library, they just don't work in the task dialogs that use the Microsoft Teams native renderer.
Target Platforms
Android
SDK Version
1.5
Application Name
Microsoft Teams
Problem Description
Adaptive Card with actions using mode=secondary do not open a menu on Android in Teams Task Dialogs. To reproduce create a staticTab with contentUrl, open a teams with example javascript. Works as expected on web/desktop/ios, only Android issue.
Use example card below. Open in Android and observe non-functional behavior shown in video.
Screenshots
bug.mp4
Card JSON
Sample Code Language
JavaScript
Sample Code
let taskInfo = { title: action.title, size: { width: 520, }, card: JSON.stringify(card), completionBotId: botId, }; dialog.adaptiveCard.bot.open(taskInfo, (err, result) => { if (err) console.log(err); if (result) console.log(result); });
The text was updated successfully, but these errors were encountered: