Vivox login status is periodically blocked when the Android Internet environment is LTE

Unity Services
,
1

We are developing and working on a voice chat function using Vivox.

On IOS Phone, it works well in basic Internet (LTE) and Wi-Fi environments.

On Android phones, it works fine if I use wifi.

However, when using the basic Internet (LTE) of the mobile phone, the phenomenon of disconnection occurs after 30 to 40 second after logging in.

I would like to know how to solve this problem.

  • We have code logic to force re-login when connection is lost.

Vivox Version : 15.1.180001-pre.4

Unity Version: 2020.3.21f1

Vivox Socket Disconnection Log.

2022-08-24 11:51:09.141 21954 22114 Info Unity XMPP(0)xmpp DEBUG Closing socket connection.
2022-08-24 11:51:09.141 21954 22114 Info Unity VivoxUnity.VivoxDebug:smile:ebugMessage(Object, vx_log_level)
2022-08-24 11:51:09.141 21954 22114 Info Unity
2022-08-24 11:51:09.999 21954 22114 Info Unity XMPP(0)event DEBUG Stopping event loop.
2022-08-24 11:51:09.999 21954 22114 Info Unity VivoxUnity.VivoxDebug:smile:ebugMessage(Object, vx_log_level)
2022-08-24 11:51:09.999 21954 22114 Info Unity
2022-08-24 11:51:10.002 21954 22114 Info Unity void VivoxApi::CommandHandler::PostEvent(T *&, bool) [T = vx_evt_account_login_state_change](715)this=0xb400007019cc3800,ToXml(p, true)=<Event type="AccountLoginStateChangeEvent"><AccountHandle>sip:.14568-altav-35983-udash.BjSkcXfw9cSty5qOvDyEx6eusQxI.2827d84e-017c-4786-9402-25cf884663ca.@mtu1xp.vivox.com</AccountHandle><StatusCode>0</StatusCode><State>0</State></Event>
2022-08-24 11:51:10.002 21954 22114 Info Unity VivoxUnity.VivoxDebug:smile:ebugMessage(Object, vx_log_level)
2022-08-24 11:51:10.002 21954 22114 Info Unity
2022-08-24 11:51:10.005 21954 21996 Info Unity [Vivox] <color=#AC58FA>Login State : LoggedOut , ID : Dek </color>

The full log is attached to the file below.

8385303–1105983–Vivox LTE Disconnect Log.txt (129 KB)

2

Downgrading the Vivox version solved the problem.

Version : 15.1.180001-pre.1

3

I am sorry to hear you were experiencing issues, but I’m glad to hear downgrading fixed the problem.

Did you incrementally test versions pre.2 and pre.3 and saw issues on there as well? Or did you just test pre.1 first and that happened to work? We’re trying to determine which version saw a regression for this issue.

Secondly when you experienced the issue, you said this occurred periodically? How often did you find this issue occur, for example 1 in every 10 tests, 1 in 100, etc?

Thanks for your cooperation!

4

Test version is 15.1.180001-pre.4
It was an issue with the version,
It didn’t happen when I tested with the test version down to 15.1.180001-pre.1.

All of these issues occurred on my Android device.