We have a connection for realtime and a connection for voice. If both are disconnected, the listener disconnectReturn callback is only triggered on the first disconnection. Is this a bug? SDK Version 220.127.116.11
Are you calling connect on two different LoadBalancing::Client instances? Otherwise you actually only have one connection and the second disconnect call won't do anything, as the client is already getting disconnected through the first call. Hence no disconnectReturn for the second call would be correct.
Note that in production you are required to use a Realtime appID for the Realtime and a Voice appID for Voice, so you need a separate Client instances for each and reusing the same for both would be a bug in your code.
With two separate Client instances I get the correct amount of disconnectReturn() calls, so if you are actually using two separate Client instances, then please provide us with a minimal self-contained repro-case so that we can reproduce the issue.
We are calling connect on two different LoadBalancing::Client instances, one for Voice and one for Realtime.
analyze performance and traffic on our website.
By clicking on the „Accept All“ button you consent to the use of non-functional cookies and the subsequent
processing of personal data to optimize our website and services as described in more detail in our
By clicking on the „Customize or Deny all“ button you can decide otherwise.
Clicking on the „Customize“ button will take you to a page where you can configure the usage of non-functional
cookies (and related technologies) or deny all of them. You can access these settings at any time and also
subsequently deselect cookies at any time in the footer area of our website.
We use the following categories of cookies and related technologies to enhance your experience,
show you personalized content, and analyze performance and traffic on our website.
We respect your right to privacy and accordingly you can chose to not allow some types of cookies (and related technologies).
Click on the different category sliders and change our default settings to manage your cookie settings.
For more information on the specific cookies/related technologies we use and on how we use these,
Authentication cookies we use are required to run our services … Cookies are required:
These cookies collect anonymous data and allow us to optimize our
website and user experience. These cookies are listed here:
Help us to understand how visitors interact with our services, enables us
to analyze and improve our services (also through third party analytics).