microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Unable to get Participant Info from Graph SDK
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Describe the issue
There is an intermittent issue observed where the Graph SDK returns null participants when the PSI bot joins a call with one or any x number of participants already present. It appears that the Graph SDK is intermittently failing to fetch participants, resulting in null values being returned. This behavior needs investigation and resolution to ensure consistent functionality.
Code Snippet
This code snippet is from CallHandler class which triggers on ParticipantUpdate:
if (participantDetails != null)
{
json = updateParticipant(this.BotMediaStream.participants, participant, added,participantDetails.DisplayName);
}
else if (participant.Resource.Info.Identity.AdditionalData?.Count > 0)
{
if (CheckParticipantIsUsable(participant))
{
json = updateParticipant(this.BotMediaStream.participants, participant, added);
}
}
Expected behavior
The expected behavior is consistent retrieval of accurate participant information by the Graph SDK. Currently, the SDK intermittently fails to provide accurate participant details, requiring investigation and resolution for consistent functionality.
Graph SDK Version:
Microsoft.Graph V 5.44
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.
Research direction
Start at the CallHandler ParticipantUpdate path shown in the issue and inspect how Graph SDK v5.44 participant data flows through participantDetails and participant.Resource.Info.Identity. Reproduce a PSI bot joining calls with existing participants, then trace intermittent null values. Done means participant information is retrieved consistently in these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100