文档

​
​

Development

User Acquisition

Monetization

工业

Vivox Core SDK

Vivox Core SDK

此页面不支持所选语言。
Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
    • Client SDK basics
    • Channels
      • Channel name criteria
      • Channel types
      • Echo channels
      • Positional channels
      • Volume differences
      • Channel identifiers for large scale games
      • Participant events
      • Channel webhooks
      • Join a channel
      • Leave a channel
      • Kick a user from a channel
      • Manage session groups
      • Audio injection
      • Methods for setting audio levels
      • Derumbler
      • Automatic connection recovery
        • Network connection state events
        • Network reconnect failure
        • Partial connection failure
    • Presence management
    • Messaging
    • Manage audio
    • Couch co-op
    • Android app development
    • iOS app development
    • macOS app development
    • Windows app development
    • Real-time recording
    • Speech-to-text audio transcription
    • Text-to-speech
    • Troubleshooting
  • Reference
  • Privacy overview
  1. Vivox Core SDK documentation

Automatic connection recovery

Learn how Vivox automatically recovers dropped connections.
阅读时间1 分钟
最后更新于 8 个月前

The Vivox SDK provides automatic connection recovery to accommodate brief periods of network interruption. This connection recovery occurs without intervention from the application. If network connectivity is lost, the Vivox SDK attempts for up to 30 seconds to restore connectivity.
For example, a disconnection could occur when a user is roaming between cellular networks, when a device switches between a mobile data connection and a home wireless network, or when a user turns on airplane mode.
The Vivox SDK fires events to indicate the connection recovery status. You can monitor these events to provide users with a display of their Vivox connection health.
In the scenario where attempts at recovery have ultimately failed, you can use a minimal integration to alert the user of the reconnect failure, because user action is likely required to address any issues with their network connection health. A more in-depth integration might help with recovery from a partial disconnection from Vivox.
注意
If an additional system exists to reconnect users, you must allow the default Vivox system to finish attempting to recover before another system tries to recover the connection. If the Vivox attempts aren't completed it can result in a connection recovery loop.

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题