Vivox Error 10012 - Undocumented

Hi!

I am seeing this issue on Firebase Crashlytics. Can someone from Unity let me know what should I do to troubleshoot since I can’t find any documentation on this particular issue?

Vivox SDK 5.15
Unity 2019.4.39

Non-fatal Exception: java.lang.Exception: VivoxApiException : (10012)
       at VivoxUnity.VxClient.EndIssueRequest(VivoxUnity.VxClient)
       at VivoxUnity.Client+<>c__DisplayClass12_0.<BeginGetConnectorHandle>b__0(VivoxUnity.Client+<>c__DisplayClass12_0)
       at System.AsyncCallback.Invoke(System.AsyncCallback)
       at VivoxUnity.AsyncResult`1[T].SetComplete(VivoxUnity.AsyncResult`1[T])
       at VivoxUnity.VxClient.InstanceOnMainLoopRun(VivoxUnity.VxClient)
       at RunLoop.Invoke(RunLoop)
       at MessagePump.RunOnce(MessagePump)
       at MessagePump.RunUntil(MessagePump)
       at VivoxUnity.VxUnityInterop+<VivoxUnityRun>d__7.MoveNext(VivoxUnity.VxUnityInterop+<VivoxUnityRun>d__7)
       at UnityEngine.SetupCoroutine.InvokeMoveNext(UnityEngine.SetupCoroutine)
       at System.AsyncCallback:Invoke(System)
       at VivoxUnity.AsyncNoResult:SetComplete(VivoxUnity)
       at VivoxUnity.Private.<>c__DisplayClass91_0:<BeginLogin>b__0(VivoxUnity.Private)
       at System.AsyncCallback:Invoke(System)
       at VivoxUnity.AsyncResult`1:SetComplete(VivoxUnity)
       at VivoxUnity.<>c__DisplayClass12_0:<BeginGetConnectorHandle>b__0(VivoxUnity)
       at System.AsyncCallback:Invoke(System)
       at VivoxUnity.AsyncResult`1:SetComplete(VivoxUnity)
       at VivoxUnity.VxClient:InstanceOnMainLoopRun(VivoxUnity)
       at VivoxUnity.<VivoxUnityRun>d__7:MoveNext(VivoxUnity)
       at UnityEngine.SetupCoroutine:InvokeMoveNext(UnityEngine)

Hello @y0rshl , based on Firebase Crashlytics and the call stack, I’m assuming this is on Android. Do you know what device and Android version you are experiencing this with? Are you receiving this report from multiple devices or just one?

From the call stack it looks like you are trying to login and failing for some reason. Do you know if the device is located somewhere that it is having network issues or being backgrounded during the login process?