Mobile streams may get corrupted
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, ios
- Domain
- audio-video-rtc, mobile-dev
Research direction
Start by reproducing the corrupted webcam streams in the UI library sample app and the Communication Services web-calling sample using the listed Android and iOS devices and browsers. Done means the affected streams no longer show tearing, monochrome output, or a black screen in the Teams call.
Written by the indexing model from the issue text.
Description
Describe the bug
From various mobile devices, certain webcam streams end up corrupted on the Teams side. To be specific:
- Device A (Android) has two cameras, both cameras show heavy tearing when seen in the Teams call that it's connected to.
- Device B (Android) has two cameras, which are both shown monochromous in Teams
- Device C (iOS) shows a black screen (just one of two cameras I believe) in Teams
A few other tested devices have no issues with their streams. All of these streams display as expected locally.
To Reproduce
These issues happen in both the UI library sample app as well as this sample.
I've tried this with various devices and browsers, of which at least the following:
- Android/Chrome
- Android/Edge
- iOS/Safari
Screenshots
This is the monochromous stream. On my last attempt it showed some red dots over it too, as seen here
Phones used (please complete the following information):
- Google Pixel 2A / Android 11 / Chrome 88
- Alcatel mini tablet / Android 8.1.0 / Chrome 91
- Samsung Galaxy A3 / Android / Edge 46
- Not sure / Android 8 / Chrome 90
- Dominant language
- No language data
- Stars
- 340
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/Communication
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#600 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#599 · 4 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#598 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/Communication#543 ·
-
Needs: triage :mag:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#447 ·
All issues in Azure/Communication
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
bug tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 92/100
anchapin/planar-nexus#2052 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
QwenLM/Qwen-MM-Plugins#70 ·
-
area: tools priority: p3 status: needs review type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
use-agent-os/agent-os#3162 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
home-assistant/core#182762 · 1 comment ·