[Bug]: Sharing content to screen will error for unverified users if they are marked as presenter

[RichieMcCaff]

In a pre-orgranised meeting that includes external/unverified users.
If an app using liveshare presents content to the main stage and any of these unverified users are marked as presenters (The default role applied) they will see the following error:

Switching these users to attendee roles will allow content to present to their screens.

To Reproduce

Steps to reproduce the behavior:

1. Create a new meeting in teams
2. Invite external users to the meeting
3. Mark the external users as presenter roles
4. Use an liveshare app to present content to the screen
5. Error appears on External users screen

This is from using the meeting module function shareAppContentToStage
meeting.shareAppContentToStage((error) => { if (error) { logError(error) } },${window.location.origin}${route})

Screenshots
User marked as presenter error:

User marked as Attendee it works:

**Desktop(s)

• Seeing this behaviour on mobile/desktop
• Both versions (web/app) of teams has the same issue.

[Nivedipa-MSFT]

@RichieMcCaff - Thanks for reporting your issue. We will check this and update you soon.

[Meghana-MSFT]

@RichieMcCaff - We are checking this with engineering team, we will keep you posted.

[RichieMcCaff]

@Meghana-MSFT Any updates on this bug? Are users are still seeing this.

[Meghana-MSFT]

@RichieMcCaff - Apologies for delay in response. Engineering team is investigating this issue, would it be possible for you share the tenant id in which you are testing share to stage for anonymous users? Please share above details at microsoftteamsdev@microsoft.com.

[RichieMcCaff]

@Meghana-MSFT Sent the sandbox company we where using to re-produce the error.

[Meghana-MSFT]

@RichieMcCaff - We received the tenant id, we will share it with engineering team. Thank you for the additional information.

[Meghana-MSFT]

@RichieMcCaff - Engineering team has asked if you could repro the issue once more? They did some investigating yesterday but the logs for this issue are retained for 10 days only, so they cannot conclude the root cause of this issue. There was also no data to confirm if anonymous users accessed apps within this timeframe. If you can repro this once again, team can check the logs again. Thank you for your understanding.