Skip to content

LocalVideoStream auto switched from raw media source to camera device...large privacy concern #31280

Open

Description

  • Package Name: @azure/communication-calling
  • Package Version: 1.28.4
  • Operating system: Any
  • nodejs
    • version: 20.17.0
  • browser
    • name/version: Any
  • typescript
    • version:
  • Is the bug related to documentation in

Describe the bug
We are using raw media access (https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/voice-video-calling/get-started-raw-media-access) to stream images to remote participants in a call (using canvas.captureStream to create the mediaStream). We had an issue (on our side) where we stopped generating frames to the LocalVideoStream. Because of this, the communication-calling package thought there was a problem with the raw mediaStream source, and automatically switched to the default device camera. The LocalVideoStream should NEVER switch automatically to a device camera...that is a huge PRIVACY concern. Instead, the LocalVideoStream should raise an error and stop the video altogether.

To Reproduce
Steps to reproduce the behavior:

  1. Start a LocalVideoStream using raw media access from a canvas.
  2. Cause an issue with the raw media video source (like stop generating frames)
  3. Watch the video source switch automatically from raw video to a camera device.

Expected behavior
The LocalVideoStream should NEVER automatically switch to a camera device because the user is not expecting it. This is a privacy issue. If there is an problem with the raw media source, the LocalVideoStream should report an error and stop.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    ClientThis issue points to a problem in the data-plane of the library.CommunicationService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions