Documentation

​
​

Development

User Acquisition

Monetization

Industry

Vivox Core SDK

Vivox Core SDK

Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
    • Client SDK basics
    • Channels
    • Presence management
    • Messaging
    • Manage audio
    • Couch co-op
    • Android app development
    • iOS app development
      • Required Info.plist settings for iOS apps
      • Acoustic echo cancellation
      • Initialize the AVAudioSession on app startup
      • AVAudioSessionModeVoiceChat
      • Disable the Vivox SDK internal AEC
      • iOS known limitations
    • 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
  3. iOS app development

Initialize the AVAudioSession on app startup

Considerations around initializing AVAudioSession when your application starts.
Read time 1 minute
Last updated 8 months ago
We strongly recommend that you set the AVAudioSession to AVAudioSessionCategoryPlayback, AVAudioSessionCategoryAmbient, or to another non-recording category on app startup.
Caution: Configuring the AVAudioSession near to or during voice chat can lead to unexpected volume changes. Limit this activity to the early stages of the app’s life cycle, unless you are restoring the device audio volume.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

    Report a problem with this page