Set up:
Bot Built via Bot Framework 4.x Sends 1:1 Chat Message-> Microsoft Teams -> Teams Client User (Desktop Teams client Windows).
BotX sends or replies to a 1:1 Chat message from Teams User. If the Teams user UI focus is not on the Teams client or if on the Teams client but not on that conversation, the Teams client shows a toast notification (the popup that appears in the system tray). So far so good.
There appears to have been a recent (mid 2021) breaking change in Bot Framework or Teams Client behavior, where clicking on the toast notification does not take the user into the chat pane of the BotX conversation. Instead, the Teams client focus is taken to the Feeds/Activity Tab and the user must again click on the Chat Navigation icon on the Teams client Navigation rail and then again on the specific Bot conversation to view the message. (The bot has been in use for 2+ years and this behaviour only recently broke)
This broken focus behaviour seems to be only happening with chat messages received from bots. Reproducible in Windows and Mac clients. User to user message notifications on the Teams clients work as expected which is clicking takes you immediately to the respective user chat pane.
See screen shots below showing desired vs. actual behavior of MS Teams client when interacting with Bot notifications.
Question: Any changes to the Bot Framework SDK that would require adding a new setting or flag to the 1-1 Chat Teams messages to let the client know that this is a chat message (and not an Activity Feed)?
One curious observation is that if the bot is loaded via a deeplink (i.e not installed via a Manifest file) then the Teams client behaviour is proper and as expected.
Notification Popup 1:1 Chat Message from Bot - This aspect is fine
Expected Focus When Clicking on Notification
Broken Behaviour
