Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Communication - Calling] Raw Media Screen Sharing not working in Group Call from Android Chrome #29562

Open
1 task
lsbrettjewell opened this issue May 2, 2024 · 3 comments
Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@lsbrettjewell
Copy link

  • Package Name: @azure/communication-calling
  • Package Version: 1.23.2
  • Operating system: Android
  • browser
    • name/version: Chrome/124.0.6367.83

Describe the bug
Start screen sharing with a custom screen share stream is not working in a Group Call from Android Chrome.

To Reproduce

Use the add-1-on-1-video-calling sample, and do the bare minimum to add "Join a group call" and "Start screen sharing with a custom screen share stream" functionality.

Setup:

  1. Setup 1 client on Windows Desktop Chrome (124.0.6367.63)
  2. Setup 1 client on Android Chrome

Steps to reproduce the behavior:

  1. Have each client join a Group Call
  2. On Android Chrome client, start screen sharing a custom screen share stream

Expected behavior
Remote side (Windows Desktop Chrome) will render the custom screen share stream.

Actual behavior
Remote side (Windows Desktop Chrome) fails to render the custom screen share stream.

The error in console:
azure:ACS:error 2024-05-02T17:52:50.610Z VideoStreamRenderer:RemoteVideoStream:421:VideoStreamRendererView6:RemoteStreamRenderer4 op:Start failed, message=Failed to render stream, timeout, code=408, subCode=43203 in 12.306s

Additional context

  • With the exact same setup, but the call type is a 1:1 call, this works as expected.
  • With the exact same setup, but using package version 1.19.1, this works as expected. (Bug is reproducible starting in 1.20.1)
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. labels May 2, 2024
Copy link

github-actions bot commented May 2, 2024

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @acsdevx-msft.

@akania
Copy link
Member

akania commented May 7, 2024

@lsbrettjewell thank you for reporting, can you please provide ACS call id ?

@lsbrettjewell
Copy link
Author

@akania ACS call id: a1fb5a6f-7d9a-46e1-abc5-3f8680b7c186

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants