[BUG] [iOS] Calling SDK 2.1.0-beta.1 - Re-joining a teams meeting shows displayName as "External"
@raosanat is already working on this.
Since Dec 8, 2021.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ios
- Domain
- mobile-dev
Research direction
Start with the iOS Composite demo app and reproduce the Teams meeting flow: join with a display name, remove yourself from the Teams client, then rejoin using the retained meeting details without toggling camera or microphone. Compare the participant display name across rejoin, camera, and mute actions; done means the name consistently appears as "UserName (External)".
Written by the indexing model from the issue text.
Description
Describe the bug
Re-joining teams meeting after getting removed by teams client user, occasionally produces an empty displayName. The displayName only shows "External", instead of "UserName (External)"
To Reproduce
Steps to reproduce the behavior:
- Join team's meeting from iOS Composite demo app with a display name
- Kick yourself out of meeting using the "Remove from meeting" (i.e. using a Teams client user)
- It takes you back to the home screen which has the same details (i.e. token, display name, meeting link)
- Rejoin meeting with same details (without toggling camera/ mic)
- In the Participants list on Teams it only displays "(External)"
Expected behavior
When you join a teams meeting, it should display "UserName (External)"
Screenshots

Setup (please complete the following information):
- OS: [e.g. iOS]
- IDE : [e.g. IntelliJ]
- Version of the Library used
Additional context
- After joined teams meeting, turning on your camera corrects the display name (i.e. "Name (External)")
- Toggling the mute button also produces the correct display name
- Joining the call with both camera on & mic unmuted produces the expected display name (This step doesn't seem to be constant, on some occasions the display name still appeared as "(External)")
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
- Bug Description Added
- Repro Steps Added
- Setup information Added
- 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
- 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
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
clerk/javascript#10033 ·
Maintainers usually reply within 1 day
-
React-Native Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-react-native#6822 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
ooni/probe-multiplatform#1614 · 1 comment ·
Maintainers usually reply within 1 day