Forum Discussion
Pradeep1090
Sep 16, 2024Copper Contributor
Share button on Meeting Side Panel is not sharing the CURRENT PAGE to the stage
I am using teams-js sdk version 2.9.0. I have a web app which can be added to meetings on teams. When a user adds my app to the meeting, the app will show a menu of items (landing page for meetin...
Sayali-MSFT
Microsoft
Sep 16, 2024Pradeep1090- Thanks for reporting your issue.
We will check this at our end and will get back to you.
We will check this at our end and will get back to you.
Pradeep1090
Sep 24, 2024Copper Contributor
Any update on this?
- Sayali-MSFTSep 26, 2024
Microsoft
Pradeep1090 -the share button you see in meetings broadcasts the contentURL set in the manifest, not the current page you are on within the side panel.
If you would like to share a specific url on clicking an item, use the share to stage APIs: https://learn.microsoft.com/en-us/microsoftteams/platform/apps-in-teams-meetings/build-apps-for-teams-meeting-stage?tabs=desktop%2Capp-content%2Cshare-app-content#advanced-share-to-stage-apis- PraveenPatelTQSep 27, 2024Copper ContributorHi Sayali-MSFT - Can you please suggest how can we get the currently displaying url to pass into the sahreToStage API?
Because., as we mentioned we don't know which url is currently displaying in sidePanel, also it will have some parameters to show item details.
Here we have 2 points to address:
1. We cannot store url (PageB) and parameter values.
2. I we try window.location.href for the side panel, it will simply return the content page url that we set to display (PageA). But this is not the current page url on the side panel.
We want to share the current state of the sidePanel to stage. Which was working fine previously with old teams version.
- Sayali-MSFTSep 25, 2024
Microsoft
Pradeep1090- When the share button is clicked, the landing page (PageA) is being shared on the stage instead of the current page (PageB), which is the item details page. The default behavior often shares the initially loaded content (PageA) because the SDK is likely reinitializing the shared view without keeping track of the current state.
We are checking with the engineering team if any workaround for this.