Bug - iOS/Android - OnIsTranscriptionActiveChangedListener fires when users leave/join meeting during active Transcription
- Dominant language
- No language data
- Stars
- 340
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
While a meeting is active and transcription is active, a user will leave the meeting (not the user who starts the Transcription) and the `OnIsTranscriptionActiveChangedListener` will fire and `callTranscriptionFeature.isTranscriptionActive()` will be `false`
**To Reproduce**
Create a meeting with MS Teams Clients and Droid/iOS Calling client:
1. With all clients currently in meeting, MS Teams Client user starts recording transcription
2. Transcription active notification fires on all clients
3. User leaves meeting (not the user who started transcription)
4. On Droid/iOS Calling client: `OnIsTranscriptionActiveChangedListener` will fire and `callTranscriptionFeature.isTranscriptionActive()` will be `false`
5. Meeting continues and transcript is still active from the perspective of the MS Teams Clients and the meeting in progress
**Expected behavior**
Either `OnIsTranscriptionActiveChangedListener` does not fire at all when a user leaves a meeting, or it fires twice with the last `OnIsTranscriptionActiveChangedListener` indicating that the transcript is still active.
**Desktop :**
- OS: MacOS
- 1.4.00.29477
- Client that started the transcription
- OS: Windows 11
- Unknown Microsoft Teams version
- Client leaving meeting
**Smartphone :**
- Device: moto G Power
- OS: Android 11
- com.azure.android:azure-communication-calling:1.2.1-beta.1
- Device: iPhone SE
- OS: iOS 14.7
- AzureCommunicationCalling', '2.0.1-beta.1'
**Additional context**
This only happens when Transcript is Active. If meeting is being Recorded, the iOS/Droid clients do not experience the issue.
Used for the implementation
https://docs.microsoft.com/en-us/azure/communication-services/how-tos/calling-sdk/call-transcription
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.