Skip to main content

​
Overview

The Mobile SDK has an offline mode to keep your application working during network problems. This ensures a session is not interrupted if the device loses its internet connection.
Network Buffer New:Instead of entering offline mode immediately when it detects a network issue, the mobile SDK now uses a 15-second buffer to handle temporary connection problems. This new mechanism gives you time to show a notification in your UI, like Connection unstable, before the session goes fully offline.

​
What Happens In The Offline Mode

When the SDK enters offline mode, it handles everything in the background so the user is not interrupted. The SDK will:
  • Continue to record and store audio securely on the device.
  • Save all session events that happen during the outage.
  • Automatically upload all saved audio and events when the connection returns.
The SDK notifies your app about these status changes using session delegate events.

​
Common Causes For The Offline Mode

A session can enter offline mode for several reasons:
  • Poor or lost Wi-Fi or cellular connectivity.
  • The device switches between networks (e.g., Wi-Fi to cellular).
  • A temporary problem with the backend service.
  • A dropped connection while streaming audio.
  • An issue with an authentication token.
Important notesKeep the following key features of offline mode in mind:
  • The SDK manages all transitions between offline and online modes automatically.
  • Audio quality and session integrity are always maintained.
  • The SDK can queue multiple offline sessions and will upload them in order once a connection is available.
  • All data stored locally on the device is encrypted and secure.
  • Offline recording is optimized to conserve battery life.
⌘I