Facing Issue while trying to cancel a screen share

[nainasyed03]

I am using CallWithChatComposite UI for my meeting application with Azure communication services. When i click on the present screen and then click cancel in the pop up, it is throwing error. Once this is done and then if I try switching on the camera, that also throws an error once immediately after the previous issue and then onwards camera is working fine. Also before previous issue occurs camera is working fine.

Steps to reproduce the issue

1. Click on present after entering a call.
2. From the popup that appears, click cancel which would throw error
   
3. Then on turning on camera even though camera is turned on correctly, it is throwing error only immediately after previous issue and not before or after previous issue I am facing this.
   

• OS & Device: Windows
• Browser: Google Chrome and Brave

[JamesBurnside]

Thanks @nainasyed03 for bringing this to our attention, we'll try and reproduce this error also and get back to you.

In the meantime, can you let us know the @azure/communication-react and @azure/communication-calling versions you are using as well as the Chrome version

[nainasyed03]

Thank @JamesBurnside for the response.

I am using the following versions:

"@azure/communication-calling": "^1.30.4",
"@azure/communication-react": "^1.20.0"
Chrome Version: 124.0.6367.207

[JamesBurnside]

@nainasyed03 thanks we can repro the issue on our side as well. The first, cancel screenshare, error is unfortunately "by design", the error is thrown by the browser screenshare API and the exception returned isn't unique enough for us to swallow and ignore. The second however should not be happening and we'll look into this - thanks for finding it!
Side note: when building your app in production you won't see these errors covering the screen, you'll only see them silently in the console so end users shouldn't be impacted by these errors (but we're still looking into how we can fix them to reduce engineering noise)

[nainasyed03]

@JamesBurnside Thank you for confirming the issue on your end! It’s good to know that these errors won’t affect the user experience in the production. Looking forward to hearing more about the fix for the second issue. Thanks again for your prompt response!

[JamesBurnside]

Issue here is coming from the underlying @azure/communication-calling package. I've filed a bug internally (ID=3957761) to route this to the appropriate team.