Content Share is no longer working

[wolfmanjacko]

Browser: Chrome Version 97.0.4692.99 (Official Build) (64-bit)
Node: version 14.12.0

Downloaded the demos, attempted the meeting demo (v1 and v2)
Deployed properly without issue, went to the link for v2
https://xxxxxxx.execute-api.us-east-1.amazonaws.com/Prod/v2?m=mymeet
Logged on multiple "people"
When I select the share dropdown and then Test Video
I can hear the video playing but no video component. In the console I see messages like:
"stopped pinging (WebSocketClosed)"
"release media stream called" and "connection failed with status code: TaskFailed" and sometimes "should resubscribe: false (downlink: false uplink: false)"

[ltrung]

This is documented in #1059 as a known issue with chrome. Have you tried to disable hardware acceleration?

[wolfmanjacko]

Yes I tried disabling hardware acceleration in the Chrome settings. Is that where you meant? It still doesn't seem to work.

[ltrung]

Sorry maybe irrelevant but i noticed that your URL has V2 in it which seems to be very old (The current demo code no longer uses that). How old is the code or is the URL incorrect?
https://xxxxxxx.execute-api.us-east-1.amazonaws.com/Prod/?m=mymeet <- URL should just be like this using the current code.

[wolfmanjacko]

The URL is correct, it is using an older zip of demo code as it was first built in July 2020 but it was working perfectly (in production use) until a few weeks ago by client reports.

[wolfmanjacko]

Is there a demo you can point to where content sharing is currently working in Chrome 97? It would be a lot of work to port the code but if necessary we can do it.

[ltrung]

I just did a serverless demo from the main branch and content share a test video worked for me in Chrome 97 no issue.

[wolfmanjacko]

I downloaded that one, went into demos/serverless ran npm install and then ran npm run deploy -- -r us-east-1 -b chime-main-b1 -s chime-main-s1 -a meeting.

It crashes out with a error about ruby is not recognized. Is there more installation instructions than what the read me has?

[ltrung]

You just have to have ruby installed and export it in PATH. We have some ruby script when running npm run build.

[ltrung]

@wolfmanjacko Any luck?

[wolfmanjacko]

I was able to use the current version...unfortunately I built an entire video conferencing tool based on a previous version which is not longer working. So I am trying to figure out if I can retrofit the current methods into this older version.

[ltrung]

Sorry but there should be no work to be done from your side to update to a new version since it is supposed to be backward compatible.

[jing-chen1]

Closing this issue due to inactivity, please feel free to reopen it if you still have problems.