Bot adaptive card push notification shows "The bot sent you a card" instead of activity.summary on Android after ~5 minutes of screen lock

[migrae]

Bot sends a proactive adaptive card with "summary" set on the Activity object (not inside the card attachment). Desktop Teams correctly shows the summary for the exact same card instance. On Android, the notification shows "The bot sent you a card" when the screen has been locked for ~5 minutes.

Unlocking the screen and immediately re-locking makes it work again — until the next ~5 min idle period.

[Nivedipa-MSFT]

Hello @migrae - Thanks for bringing this issue to our attention.
After ~5 min of idle/lock, Teams Android drops its live socket and notifications fall back to FCM push. In that path, Teams Android ignores Activity.Summary (desktop/web-only field) and shows the generic "The bot sent you a card."

Once you unlock, the socket is re-established → the next card renders live and Summary works again.

Fix

Also set Activity.Text (and optionally Speak). On Android's FCM path, Text is used for the lock-screen preview.

var activity = MessageFactory.Attachment(new Attachment
{
    ContentType = AdaptiveCard.ContentType,
    Content = adaptiveCard
});

activity.Text    = "New approval request from Jane Doe"; // Android lock-screen
activity.Speak   = "New approval request from Jane Doe";
activity.Summary = "New approval request from Jane Doe"; // Desktop

await turnContext.SendActivityAsync(activity, cancellationToken);

Please let us know if you have any further query here.

[migrae]

Hi!
We already tried that. Setting the activity.text will also send the text value as a regular message in addition to the card into the chat. We only need the card and its notification message.

I will try setting .speak and see if something changes

[migrae]

ok, that did not help either

[Nivedipa-MSFT]

Hello @migrae - We were able to reproduce the issue in the Android Teams version [2026.06.01.10] and on Android 16. We have logged this as a bug, and our engineering team will look into it.

While we cannot guarantee a fix at this stage, we will keep you updated with any progress or changes. Please note that in some cases, the bug may be by design or deprioritized due to platform updates, but we will continue to monitor the bug closely.

Thank you again for your cooperation!