Error Access Token Service Unavailable (20127) after upgrade to v16.0.1

Multiplayer & Networking
,
1

Hi,

We recently upgraded our Vivox package to v16.0.1(from
15.1.210000-pre.1) but when we call VivoxService.Instance.LoginAsync, we received error 20127

[Vivox]: <Login>b__0: vx_req_account_anonymous_login_t failed: Unity.Services.Vivox.VivoxApiException: Access Token Service Unavailable (20127)
  at Unity.Services.Vivox.VxClient.EndIssueRequest (System.IAsyncResult result) [0x00056] in /Users/macmini/code/wwv_gitlab/Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/VxClient.cs:233
  at Unity.Services.Vivox.LoginSession+<>c__DisplayClass114_0.<Login>b__0 (System.IAsyncResult result) [0x00000] in /Users/macmini/code/wwv_gitlab/Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/Private/LoginSession.cs:703
UnityEngine.Logger: LogError (string, object)
Unity.Services.Vivox.VivoxLogger:LogError (object) (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/SDK/Utils/VivoxLogger.cs:15)
Unity.Services.Vivox.VivoxLogger:LogVxException (object) (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/SDK/Utils/VivoxLogger.cs:24)
Unity.Services.Vivox.LoginSession/<>c__DisplayClass114_0:<Login>b__0 (System.IAsyncResult) (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/Private/LoginSession.cs:708)
Unity.Services.Vivox.AsyncResult`1<Unity.Services.Vivox.vx_resp_base_t>:SetComplete (Unity.Services.Vivox.vx_resp_base_t) (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/AsyncResult.cs:124)
Unity.Services.Vivox.VxClient:InstanceOnMainLoopRun (bool&) (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/VxClient.cs:166)
Unity.Services.Vivox.MessagePump:RunOnce () (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/MessagePump.cs:51)
Unity.Services.Vivox.MessagePump:RunUntil (System.Func`1<bool>) (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/MessagePump.cs:34)
Unity.Services.Vivox.Client:RunOnce () (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/Client.cs:305)
Unity.Services.Vivox.VxUnityInterop/<VivoxUnityRun>d__6:MoveNext () (at Library/PackageCache/com.unity.services.vivox@16.0.1/Runtime/VivoxUnity/VxUnityInterop.cs:66)
UnityEngine.SetupCoroutine:InvokeMoveNext (System.Collections.IEnumerator,intptr) (at /Users/bokken/build/output/unity/unity/Runtime/Export/Scripting/Coroutines.cs:17)

If we enable isTestMode then it will work.
Below is the code we use for initialization, our access token is generated by our server.

                VivoxConfigurationOptions options = new VivoxConfigurationOptions();
#if UNITY_IOS && !UNITY_EDITOR
                options.SkipPrepareForVivox = true;
#endif
                InitializationOptions initializationOptions = new InitializationOptions();
                // _key can be excluded from SetVivoxCredentials if an implementation of IVivoxTokenProvider has been provided to the SDK.

                await UnityServices.InitializeAsync();
                VivoxService.Instance.SetTokenProvider(new VivoxVoiceTokenProvider());
                await VivoxService.Instance.InitializeAsync(options);
2

Hey heliosmini!

Were there any other changes along the way when upgrading to v16.0.1 of the Vivox package?
Did anything about which credentials you are using change? Which Vivox server are you generating tokens for?
If it’s not mtu1xp (the default provided when creating a project on the Unity Dashboard), can you try placing them inside of initializationOptions.SetVivoxCredentials() like so
initializationOptions.SetVivoxCredentials(_server, _domain, _issuer);
and passing the initializationOptions object into await UnityServices.InitializeAsync(); like
await UnityServices.InitializeAsync(initializationOptions);

The reason why isTestMode may be working is likely because, when it’s toggled, the SDK will generate client-side tokens for you and use those for login and join channel requests.

3

We also migrate to Unity Dashboard when upgrading. So the credentials changed (the domain is still mtu1xp). Sorry for forgetting to mention that.
We already updated the new credentials on our server.
We also tried initializationOptions.SetVivoxCredentials like you suggested but still receive error code 20127

4

Hi heliosmini. This is Kevin from Unity Support. I wanted to follow up on your situation.

Could you please confirm if this login issue starting with your upgrade to v16.0.1 is still occurring: are you still getting 20127 errors in response to every Vivox login request? In other words, no logins succeed at all, and each one fails with 20127?

This next part is going to sound dumb—and is probably a moot point now that it’s a week later—but did you try closing and reopening the Unity Editor after upgrading the package and swapping the credentials? I’ve seen bad behaviour like this occasionally when making big changes to the local Vivox setup (package upgrade, linking new uDash project) when trying to hit the Play button without first closing and reopening the Editor window. You’ve probably done that by now.

If this is still happening, please let us know if it’s consistent with every login call.

5

Hi,

Sorry for not getting back to you sooner. We were on a Luna New Year break.

The 20127 error is gone after we delete the Library folder and let Unity regenerate the folder.

6

Hello!!

Thank you for following up; no problem about the break. It’s great to hear you were able to resolve the issue by regenerating the Library folder! When updating packages, sometimes regenerating the auto-generated files like this can be necessary if some of the old package data is still cached locally, in order to prevent unexplained or unpredictable behaviour.

I will let the Vivox SDK team know what happened so they can determine if there’s anything we can do to defend against this, or provide a clearer error message. Thank you again for the report!