Hi, could you publish a new @chat-adapter/teams version that includes #403?
We are hitting the Teams DM history issue fixed in #403: fetchMessages() uses the Bot Framework DM conversation id (a:...) as the Microsoft Graph /chats/{chat-id}/messages id, which fails because Graph expects the resolved Teams chat id (19:...).
The fix was merged in #403 on April 20, 2026, but the latest published @chat-adapter/teams version appears to still be 4.26.0 from April 14, 2026, so npm does not include it yet.
This currently breaks Teams DM history for apps using the published package, even with the correct Graph permissions configured.
Hi, could you publish a new
@chat-adapter/teamsversion that includes #403?We are hitting the Teams DM history issue fixed in #403:
fetchMessages()uses the Bot Framework DM conversation id (a:...) as the Microsoft Graph/chats/{chat-id}/messagesid, which fails because Graph expects the resolved Teams chat id (19:...).The fix was merged in #403 on April 20, 2026, but the latest published
@chat-adapter/teamsversion appears to still be4.26.0from April 14, 2026, so npm does not include it yet.This currently breaks Teams DM history for apps using the published package, even with the correct Graph permissions configured.