ドキュメント

​
​

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 またはその関係会社の商標または登録商標です (詳しくはこちら)。その他の名称またはブランドは該当する所有者の商標です。

一部のページは利便性向上のため機械翻訳を使用しており、内容に不正確な表現が含まれる場合があります。内容に齟齬または不一致が生じた場合は、英語版を正本とします。


    このページの問題を報告する