Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Android][Calling] Host video stream is unavailable after host joins the conference first time. Repeats when rejoining in the same conference

Open
#406 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
android
Domain
mobile

Research direction

Start by reproducing the conference flow on the listed Android device and Calling SDK versions, focusing on the host stream after three to five exits and rejoins. Compare the remote stream and renderer state at each join; done means the host video remains visible on every rejoin.

Written by the indexing model from the issue text.

Description

Bug Needs: triage :mag:

Describe the bug
When I enter from an Android device using the Calling SDK 1.2.1-beta1 , the host will admit me and after a couple of exits and rejoins (usually 3-5) , I cannot see the host's video stream even if he confirms the camera is enabled

To Reproduce
Steps to reproduce the behavior:
1.Host a teams video call
2.Join using the calling SDK
3.Exit and re-join ( you or remote participant)
4.Notice that you cannot see the host's videostream anymore (the remoteStream si available and the renderer is intialized)

Expected behavior
I can see the host's video stream each time I join the conference.

Smartphone (please complete the following information):

  • Device: Samsung S9+
  • OS: Android 10
  • Browser [e.g. stock browser, safari]
  • Version : Calling SDK 1.2.1-beta1 , 1.3.0-beta1 , 2.0.0-beta1
Dominant language
No language data
Stars
339
Forks
113
Avg merge
36m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/Communication

All issues in Azure/Communication

Similar issues

More Mobile Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.