Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teams V2 messaging extension started from commandbox has no context (URL placeholder are not replaced with values) #6775

Open
anne376 opened this issue Apr 16, 2024 · 4 comments
Labels
Area: Teams The issue is related to Teams support bug Indicates an unexpected problem or an unintended behavior. needs-triage The issue has just been created and it has not been reviewed by the team.

Comments

@anne376
Copy link

anne376 commented Apr 16, 2024

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.

Version

V4.22.3

Describe the bug

I have a problem with my existing Teams messaging extension in Teams V2. With the old teams everything runs perfectly.

I have a messaging extension using the Bot Framework. Actions are defined which can be triggered from message and command box. On my server I did override OnTeamsMessagingExtensionFetchTaskAsync and created a MessagingExtensionActionResponse with a URL that includes placeholders, like {groupId} and {channelId}.

The messaging extension works fine when I use the old teams client (web or windows app). But if I switch to Teams V2 the placeholders are only replaced with values when the messaging extension is triggered from the message. If it is triggered from commandbox the placeholders are not replaced.

Expected behavior

Placeholder should be replaced with values when the messaging extension is triggered from message AND commandbox

@anne376 anne376 added bug Indicates an unexpected problem or an unintended behavior. needs-triage The issue has just been created and it has not been reviewed by the team. labels Apr 16, 2024
@tracyboehrer
Copy link
Member

@anne376 Do you happen to have examples of the change? It does sound like Teams changed something, but it will make it easier to confer with them with examples.

@anne376
Copy link
Author

anne376 commented May 24, 2024

Hi @tracyboehrer, yes I think something has changed in Teams.

The original URL looks like this with placeholders:
https://Server/MyApp/Documents?TeamsGroupId={groupId}&TeamName={teamName}&Culture={locale}&theme={theme}&TeamsChannelId={channelId}

If I start an action commmand from command box in Teams V2 only theme and culture palceholders are replaced:
https://Server/MyApp/Documents?TeamsGroupId={groupId}&TeamName={teamName}&Culture=en-us&theme=default&TeamsChannelId={channelId}

If I start from the message in Teams V2 all placeholders are replaced (I just changed the IDs a bit ;) ):
https://Server/MyApp/Documents?TeamsGroupId=aaaaaaaa-6666-4444-9ca9-9c210a6599da&TeamName=Projekt-Team&Culture=en-us&theme=default&TeamsChannelId=19%3A11268b3aa666666c9eac093592b43fb6%40thread.skype

@tracyboehrer
Copy link
Member

@anne376 Is this still an issue?

@anne376
Copy link
Author

anne376 commented Nov 4, 2024

@tracyboehrer Yes, that is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Teams The issue is related to Teams support bug Indicates an unexpected problem or an unintended behavior. needs-triage The issue has just been created and it has not been reviewed by the team.
Projects
None yet
Development

No branches or pull requests

2 participants