Open huyhoangk50 opened 2 months ago
Also having this issue, starting from v2.8.0. The issue is not reproducible on v2.7.0. The stack trace from v2.8.0 is
java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: com.azure.android.communication.calling.CallingCommunicationException: Invalid Token Provider
at java9.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:399)
at java9.util.concurrent.CompletableFuture.get(CompletableFuture.java:2079)
at com.example.msteams.call.data.AzureCallAgentProvider$getOrCreateAgent$2.invokeSuspend(AzureCallAgentProvider.kt:52)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:585)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:802)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:706)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:693)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@c7f3c75, Dispatchers.Main.immediate]
Caused by: java.util.concurrent.ExecutionException: com.azure.android.communication.calling.CallingCommunicationException: Invalid Token Provider
at java9.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:399)
at java9.util.concurrent.CompletableFuture.get(CompletableFuture.java:2079)
at com.azure.android.communication.calling.CallClient$5.get(CallClient.java:275)
at com.azure.android.communication.calling.CallClient$5.get(CallClient.java:254)
at java9.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1774)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Caused by: com.azure.android.communication.calling.CallingCommunicationException: Invalid Token Provider
at com.azure.android.communication.calling.NativeLibraryHelpers.checkStatus(NativeLibraryHelpers.java:390)
at com.azure.android.communication.calling.CallClient$1.get(CallClient.java:155)
at com.azure.android.communication.calling.CallClient$1.get(CallClient.java:148)
at java9.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1774)
It fails when calling callClient.createCallAgent(applicationContext, CommunicationTokenCredential(token))
, and on v2.7.0 it works just fine.
@huyhoangk50 I think I figured it out - they now have a separate createTeamsCallAgent
method for custom Microsoft Teams clients. Yeah, they don't provide a nice error message, or any tutorial on migrating from v2.7.0, and the documentation at https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/voice-video-calling/get-started-call-to-teams-user?pivots=platform-android is also outdated, using the old createCallAgent
method 😞
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Versions