Teams - Share app content to stage 501 error

[pheidler]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• SPFx version 1.21
• Node.js version 18.18.0

Describe the bug / error

I'm working on an in-meeting app for Teams and cannot share app content to the stage. The default share to stage functionality works (i.e share button in bottom of side panel), but a custom share button that invokes context.sdks.microsoftTeams.teamsJs.meeting.shareAppContentToStage() results in the following error:

{ "errorCode": 501, "message": "API is not supported in current context-Provided URL is invalid" }

The URL I am passing in is the tenant URL. I am following this example.

My manifest file has the following domains listed: ["{teamSiteDomain}", "<<domain-name>>", "${{TAB_DOMAIN}}"]. I've tried various combinations of other domains as well, including just using ["*"]. The error doesn't appear to be coming from a network request, so I'm guessing there's an issue with how the validDomains property is being checked (or possibly with the domains I've listed).

I have the following permissions listed:

"permissions": {
      "resourceSpecific": [
        {
          "name": "LiveShareSession.ReadWrite.Chat",
          "type": "Delegated"
        },
        {
          "name": "LiveShareSession.ReadWrite.Group",
          "type": "Delegated"
        },
        {
          "name": "MeetingStage.Write.Chat",
          "type": "Delegated"
        },
        {
          "name": "OnlineMeeting.ReadBasic.Chat",
          "type": "Application"
        },
        {
          "name": "ChannelMeeting.ReadBasic.Group",
          "type": "Application"
        }
      ]
    }

and the following contexts:

"context": [
        "channelTab",
        "privateChatTab",
        "meetingSidePanel",
        "meetingDetailsTab",
        "meetingChatTab",
        "meetingStage"
      ]

I wasn't sure if this is an SPFx issue or a TeamsJS issue. I've opened a ticket there as well. Thank you!

Steps to reproduce

1. Create an SPFx Teams in meeting app
2. Enable custom share to stage in the manifest.json file "supportsCustomShareToStage": true
3. Invoke `shareAppContentToStage(() => {}, {tenantUrl})

Expected behavior

In meeting app opens for each user in the stage context.

[Ashlesha-MSFT]

Hello @pheidler
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@pheidler,
Can you please help me by sharing the code to reproduce the issue, because even if I added

"context": [
          "meetingSidePanel",
          "meetingStage"
          
        ]

getting below error Error: This call is only allowed in following contexts: ["sidePanel","meetingStage"]. Current context: "content".

[pheidler]

@Ashlesha-MSFT It looks like you have the app open in the wrong context- if you join the meeting, you can open the app in the side panel. Let me know if that works. If not, I can work on a reproducible example.

Just another bit of context- I'm adding the app programmatically to the chat from a Teams tab app using the following:

const teamsApp = await client
          .api(`/appCatalogs/teamsApps?$filter=externalId eq '${externalId}'`)
          .get();
        const teamsAppId = teamsApp.value[0].id;

        // Adds app to the meeting
        await client.api(`/chats/${threadId}/installedApps`).post({
          "teamsApp@odata.bind": `https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/${teamsAppId}`,
          consentedPermissionSet: {
            resourceSpecificPermissions: [
              {
                permissionValue: "OnlineMeeting.ReadBasic.Chat",
                permissionType: "Application",
              },
              {
                permissionValue: "ChannelMeeting.ReadBasic.Group",
                permissionType: "Application",
              },
              {
                permissionValue: "LiveShareSession.ReadWrite.Chat",
                permissionType: "Delegated",
              },
              {
                permissionValue: "LiveShareSession.ReadWrite.Group",
                permissionType: "Delegated",
              },
              {
                permissionValue: "MeetingStage.Write.Chat",
                permissionType: "Delegated",
              },
            ],
          },
        });

        // Adds tab to the meeting
        await client.api(`/chats/${threadId}/tabs`).post({
          displayName: appName,
          "teamsApp@odata.bind": `https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/${teamsAppId}`,
          configuration: {
            entityId: extension,
            contentUrl: tabContentUrl,
            websiteUrl: websiteUrl,
            removeUrl: null,
          },
        });

[Ashlesha-MSFT]

@pheidler,
Thanks for suggestion!
We were able to reproduce the issue, and we are investigating it. We have logged this as a bug, and our engineering team will look into it.
Thank you for your patience!

[pheidler]

@Ashlesha-MSFT Great, thank you!

[pheidler]

@Ashlesha-MSFT Any idea what the timeline is for this fix?