Some teams bot app cannot be added and the button stop working on the Android platform

[JASON-C4]

Steps to reproduce

Actually, I have created multiple bot applications to use in Teams. And the bot will send alert messages in the form of adaptice cards. Users can click on the buttons on the card to perform some operations on it. But the button suddenly stopped working on the Android platform , about two weeks ago. And it can be used normally on both the web and computer ends.

Expected behavior

Under normal circumstances, the bot will receive messages about my actions and reply. One of my bots can still operate normally on the Android platform, as shown below.

Actual behavior

When I click the button on the Android platform, some other bots will ask me to add the Teams bot application.

But when I click add, the card will report an error: "Something went wrong Please try again" and "Sorry, this Teams app was not added. Please try again later.".

Error details

The application has been released in our organization. And the endpoint has been configured. Under normal circumstances, my bot can receive information when I click a button. But in reality, my bot did not receive the message of me clicking the button, instead it asked me to add the Teams app, and it also failed to add and reported an error.

[m365-agent-toolkit-assistant]

👋 Hi @JASON-C4,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

This is a known issue affecting Adaptive Card button actions (e.g., Action.Submit, Action.Execute) on Teams for Android. Microsoft confirmed a regression in recent Android app builds that caused submit/invoke/execute actions to fail or trigger “Please try again” errors, even if the bots worked fine on other platforms.

Resolution:
Microsoft has fixed these bugs in the latest Teams for Android releases.

Action Steps:

1. Update Teams Android app to the newest version (at minimum: 1416/1.0.0.2024042104/0226, or version 15/2025.34.01.9).
2. Restart the app after updating.
3. Test bot again—buttons should work normally.

If the problem persists after updating, provide:

• Teams app version
• Android OS version
• Sample Adaptive Card JSON for the impacted bot

Relevant issue: msteams-docs/issues/6686

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[sayali-MSFT]

Hello @JASON-C4 ,Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[sayali-MSFT]

Hello @JASON-C4 ,We are unable to reproduce the issue on our side. We tested using the sample provided below:
https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-adaptive-card-actions/csharp

If possible, could you please share the relevant code snippets and your app manifest? This would help us investigate further and try to replicate the issue from our end.

[JASON-C4]

Hi, @sayali-MSFT . I think the main issue is that when I click the button on the adaptive card on Android, Teams will ask me to add the bot and the addition fails. But it was still functioning normally two weeks ago.
adaptive card:
{ "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "size": "Large", "weight": "bolder", "text": "${title}", "wrap": true }, { "type": "FactSet", "facts": [ { "$data": "${summary}", "title": "${key}", "value": "${value}" } ] }, { "id": "moreText", "isVisible": false, "type": "RichTextBlock", "inlines": [ { "type": "TextRun", "text": "${text}" } ] }, { "type": "RichTextBlock", "id": "showMore", "inlines": [ { "type": "TextRun", "text": "Show More", "selectAction": { "type": "Action.ToggleVisibility", "targetElements": [ "moreText", "showMore", "showLess" ] } } ] }, { "type": "RichTextBlock", "id": "showLess", "isVisible": false, "inlines": [ { "type": "TextRun", "text": "Show Less", "selectAction": { "type": "Action.ToggleVisibility", "targetElements": [ "moreText", "showMore", "showLess" ] } } ] }, { "type": "ActionSet", "separator": true, "actions": [ { "type": "Action.OpenUrl", "title": "SOP", "url": "${sop}" }, { "type": "Action.OpenUrl", "title": "Query", "url": "${query}" }, { "type": "Action.OpenUrl", "title": "Dashboard", "url": "${dashboard}" } ] }, { "type": "ActionSet", "separator": true, "actions": [ { "type": "Action.ShowCard", "title": "Silence", "card": { "type": "AdaptiveCard", "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "Input.ChoiceSet", "id": "duration", "placeholder": "Silence Duration", "isRequired": true, "choices": [ { "title": "1 hour", "value": "1" }, { "title": "6 hours", "value": "6" }, { "title": "12 hours", "value": "12" } ] } ], "actions": [ { "type": "Action.Execute", "title": "Set Duration", "verb": "silence", "fallback": "Action.Submit", "data": { "summary": "${summary}" } } ] } }, { "type": "Action.ShowCard", "title": "Claim", "card": { "type": "AdaptiveCard", "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "text": "Please confirm whether to claim the alert", "wrap": true } ], "actions": [ { "type": "Action.Execute", "title": "Yes", "verb": "claim", "fallback": "Action.Submit", "data": { "title": "${title}", "text": "${text}", "summary": "${summary}", "sop": "${sop}", "query": "${query}", "dashboard": "${dashboard}" } } ] } }, { "type": "Action.ShowCard", "title": "Notice", "card": { "type": "AdaptiveCard", "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "text": "Please confirm whether to notice all alert receivers/claimant", "wrap": true } ], "actions": [ { "type": "Action.Execute", "title": "Yes", "verb": "notice", "fallback": "Action.Submit", "data": { "title": "${title}", "summary": "${summary}" } } ] } }, { "title": "Create Group", "type": "Action.ShowCard", "card": { "type": "AdaptiveCard", "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "text": "Please confirm whether to creat group chat", "wrap": true } ], "actions": [ { "type": "Action.Execute", "title": "Yes", "verb": "create group", "fallback": "Action.Submit", "data": { "title": "${title}", "text": "${text}", "summary": "${summary}", "sop": "${sop}", "query": "${query}", "dashboard": "${dashboard}" } } ] } } ] } ] }
The bot that can still be used normally on Android:
{ "id": "N2YzNTYxN2ItM2FhNC00MWViLWEyYmMtMDdhYzUyNjhmODY0IyNlNzEyMWE1ZC0xMWM5LTRmMGMtYjdmYS01ZWFmOTBhZTJmYmY=", "consentedPermissionSet": null, "teamsAppDefinition": { "id": "ZTcxMjFhNWQtMTFjOS00ZjBjLWI3ZmEtNWVhZjkwYWUyZmJmIyMxLjAuMCMjUHVibGlzaGVk", "teamsAppId": "e7121a5d-11c9-4f0c-b7fa-5eaf90ae2fbf", "displayName": "team-alert-tool-dev", "version": "1.0.0", "publishingState": "published", "shortDescription": "Short description of team-alert-tool-dev", "description": "Full description of team-alert-tool-dev", "lastModifiedDateTime": null, "createdBy": null, "authorization": { "clientAppId": null, "requiredPermissionSet": { "resourceSpecificPermissions": [] } } } }
The bot that cannot be used normally on Android:
{ "id": "N2YzNTYxN2ItM2FhNC00MWViLWEyYmMtMDdhYzUyNjhmODY0IyM0MjYzYmFlOC0wYmIwLTRiNTUtYWYzNC1jMTEyNTNiYmYwNzM=", "consentedPermissionSet": null, "teamsAppDefinition": { "id": "NDI2M2JhZTgtMGJiMC00YjU1LWFmMzQtYzExMjUzYmJmMDczIyMxLjAuMCMjUHVibGlzaGVk", "teamsAppId": "4263bae8-0bb0-4b55-af34-c11253bbf073", "displayName": "team-alert-tool-uatlocal", "version": "1.0.0", "publishingState": "published", "shortDescription": "Short description of team-alert-tool-uat", "description": "Full description of team-alert-tool-uat", "lastModifiedDateTime": null, "createdBy": null, "authorization": { "clientAppId": null, "requiredPermissionSet": { "resourceSpecificPermissions": [] } } } }

[sayali-MSFT]

Hello @JASON-C4 ,Thanks for sharing the information, we will check this and get back to you.

[sayali-MSFT]

Hello @JASON-C4 ,
We are checking this with the internal team.

meantime you can check the below points: -
Teams mobile—particularly Android—applies stricter checks when Adaptive Cards trigger Action.Execute, requiring the bot to be fully installed and correctly scoped in the exact chat where the card appears. As a result, cards that work in desktop Teams or the Copilot Studio test panel may fail on mobile if the bot’s app ID changed, the manifest didn’t propagate, or the bot isn’t recognized as installed in that conversation.
This mismatch leads to “Add bot” prompts or silent failures, making bot-installation consistency, manifest correctness, and mobile-friendly fallbacks essential for reliable execution.

[JASON-C4]

Hi, @sayali-MSFT . I checked the apps published under the app catalog and the app IDs are the same as those installed in the team.
The bot that can still be used normally on Android:
{
"id": "e7121a5d-11c9-4f0c-b7fa-5eaf90ae2fbf",
"externalId": "e8133f63-a6e0-41e4-bb24-5e180ebcd3df",
"displayName": "team-alert-tool-dev",
"distributionMethod": "organization"
}
The bot that can still be used normally on Android:
{
"id": "4263bae8-0bb0-4b55-af34-c11253bbf073",
"externalId": "4f9cc877-51af-43cc-abe5-9415e4886858",
"displayName": "team-alert-tool-uatlocal",
"distributionMethod": "organization"
}
And I would like to ask how to determine the completeness of application installation on Android. When I click to "add app" on Android and then search, the button displayed on the bot app is' open ', not' add '. And before that, I could operate the buttons. Can this indicate that I have installed the application on Android?

[sayali-MSFT]

Hello @JASON-C4 ,
Yes, when you see the “Open” button instead of “Add” in the Teams mobile app on Android, it generally means the app is already installed for your account or team.

The distributionMethod: "organization" in your JSON means these apps are published internally, so installation completeness depends on:

• The app being added to the team or personal scope.
• Permissions and policies allowing usage on mobile.

[JASON-C4]

Hi @sayali-MSFT . I can confirm that the app has been added to the team and personal scope. But where can the permissions and policies allowing usage on mobile be confirmed? And what are the permissions and policies involved?