CODEWITHSUNDEEP
microsoft-teams
vt.
vt.

Reputation: 1428

Deep links to custom Tab - thread.skype vs thread.tacv2

I have problems with executing deep links created in a custom tab of my application in MS Teams.

I generate the link as described here: https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/deep-links (the format of https://teams.microsoft.com/l/entity/<appId>/<entityId>?webUrl=<entityWebUrl>&label=<entityLabel>&context=<context>)

while it works fine in environment A: e.g https://teams.microsoft.com/l/entity/9263e4c8-.....-48293cfca89a/111-222?context={"channelId":"19:[email protected]"}

it's not working in environment B (same app, another tenant) - it opens the correct team channel, but not the tab. https://teams.microsoft.com/l/entity/9263e4c8-.....-48293cfca89a/555-666?context={"channelId":"19:[email protected]"}

I noticed the thread.skype vs thread.tacv2 in the channelId, could this make the difference? Am I missing some important query param? I double-checked the appId, entityID, they match.

Upvotes: 1

Views: 1670

Answers (1)

vt.
vt.

Reputation: 1428

it seems the upgrade manifest version fixed this issue (1.5 -> 1.7)

"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.7/MicrosoftTeams.schema.json",
"manifestVersion": "1.7",

with 1.7 links are working as expected

Upvotes: 1

Related Questions