Skip to main content

Vivox: What causes status code 5027 ("Connector Limit Exceeded")?

Updated

Symptoms:

The status code VxErrorConnectorLimitExceeded (5027) is caused by attempting to initiate the "first time" Vivox server connection more than once after the SDK is initialized.

Cause:

  • Vivox Unity and Unreal
    This status can occur when signing into Vivox, and results in a failure to sign in.
  • Vivox Core
    This status can occur in response to a vx_req_connector_create request. If another vx_req_connector_create request has already completed successfully since Vivox was last initialized, this status will be given in response to each subsequent request. This status code is not considered an error, and is informational only.

Resolution:

  • Vivox Unity and Unreal
    This status should never occur. If you see this status code, please contact Vivox Support.

  • Vivox Core
    In terms of handling this status code at runtime, it can either be logged and safely ignored, or treated as a success. It is simply an informational status.

    If you encounter this status however, it means that you're issuing a vx_req_connector_create request when you don't need to, and should review your implementation. A second request of this type is never required after the first has succeeded, until the SDK is uninitialized. This is true even after network loss or resuming from device sleep.

More information:

Related to

Related articles