기술 자료

​
​

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
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.


    이 페이지의 문제 보고