[MPaaS-Issue] loganstaging.esna.com - unable to share screen

[sync-by-unito[bot]]

https://drive.google.com/file/d/1XQQoSOUH3o7ZUKy12MD6wKsiYQq0Sn3p/view https://drive.google.com/file/d/1AgMS4BvzjcHbfeOncwXehvEss3PFPQaM/view

• called another DM user

• in call, one user decides to share screen but is unable to

• clicking does not allow to choose which screen to share

• another time it happened on 'my meeting room' call

• not reproducible all the time, please view logs and video

┆Attachments: loganstaging.esna.com-1597952664314.log | loganstaging.esna.com-1597953201006.log

[sync-by-unito[bot]]

➤ Jaydeep Bhalerao commented:

@Vincent Yeung ( https://app.asana.com/0/1173010497426047/list ) yiu have mentioned it happens two times, does it happened on same machine or it was different machines for each time?

Can you list down all the chrome plug-ins that were installed/enabled while you tried to share screen?

[sync-by-unito[bot]]

➤ Jaydeep Bhalerao commented:

@Vincent Yeung ( https://app.asana.com/0/1173010497426047/list ) While this issue was happening console log level was not set to verbose so some of the logs were missing, can you please enable console logs with 'verbose' level? Can you enable network trace as well to capture .har files?

Based on logs it looks like connection is blocked from JSCSDK to WCS so scren share failed to start 5f2c378bad658a7304aa5139:1 Access to XMLHttpRequest at 'https://clab.mpaaservice.com/wcs/e46da5ae-26c3-41ce-a08b-bfa2a2e25b2f/viewer/rest/live_viewer/' from origin 'https://loganstaging.esna.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. clab.mpaaservice.com/wcs/e46da5ae-26c3-41ce-a08b-bfa2a2e25b2f/viewer/rest/live_viewer/:1 Failed to load resource: net::ERR_FAILED loggerHelper.js:86 [8/20/2020, 3:42:21 PM] NetworkProvider: WCSCollabProvider,Network error occurred. Status: 400001[ null ] Escalated to JSCSDK/MPaaS team.

[sync-by-unito[bot]]

➤ Jaydeep Bhalerao commented:

Updates from MPaaS team, The server which handles screen share has multiple instances. This issue happens when active server instance is in process of shutting down and switch to another available one. This issue will be fixed by MPaaS team.