SIGN UP

Changelog

Voximplant iOS SDK changelog

2.22.0

2.21.4

  • Improvements for establishing the connection to the Voximplant Cloud
  • Fix: the connection to the Voximplant Cloud is not closed if a call was ended in the background
  • Bugfix and stability improvements

2.21.3

  • Dependency update: VoxImplantWebRTC is updated to 74.0.1
  • Improve VIQualityIssueTypePacketLoss issue detection
  • Bugfix and stability improvements

2.21.2

2.21.1

  • Bugfix and stability improvements

2.21.0

2.20.7

2.20.6

  • Fix for one-way media from iOS device after answering a video call via CallKit

2.20.5

  • Completion of the method [VIClient refreshTokenWithUser:token:result:] is not invoked if the connection to the Voximplant Cloud is not established
  • Fix for a rare crash that occurs while establishing the connection to the Voximplant Cloud

2.20.4

2.20.3

  • Bugfix and stability improvements

2.20.2

  • Improvement of multiple calls handling

2.20.1

2.20.0

2.19.1

2.19.0

2.18.0

2.17.0

2.16.1

2.16.0

2.15.0

2.14.4

2.14.3

  • Update of logging mechanism, allowing to separately capture Voximplant iOS SDK logs via CocoaLumberjack loggers

    [DDLog addLogger:logger
         withLevel:DDLogLevelInfo | VILogLevelWarning];

2.14.2

  • Introduce [VIClient initWithDelegateQueue:bundleId:] constructor. You need to use this only if you are going to send push notifications across several iOS apps using a single Voximplant application
  • Update of iOS SDK toolchain to 11.4

2.14.1

  • Fix for a rare crash that occurs when connection unexpectedly dropped

2.14.0

2.13.2

  • Dependency update: CocoaLumberjack is updated to 3.4
  • Fix for AVAudioSession behavior handling on iOS 10.0
  • Stability improvements

2.13.1

  • Improvements in handling audio route changes made via CallKit
  • Fix for crash on VIClient connect API call when the app enters foreground
  • Stability improvements

2.13.0

2.12.0

  • Dependency update: VoxImplantWebRTC is updated to 62.1.0, pods now contain i386 arch support
  • Dependency to AFNetworking is removed
  • Introduce VIRejectMode to manage reject call behavior
  • Speaker can now be activated before a call
  • Bugfix and stability improvements

2.11.0

  • Dependency update: VoxImplantWebRTC is updated to 62.0.0
  • Fix for camera pre-processing delegate not being called
  • Introduce AudioSession VIAudioManager callKitConfigureAudioSession to provide better CallKit support ( GitHub )
  • Changes in VoIP push notification payload structure. If you checking payload format before passing it onto Voximplant iOS SDK, you should check GitHub for reference.

2.10.0

2.9.0

  • Fix for no audio issue when the video call is answered via CallKit in lock mode
  • Fixed background connection handling to improve stability of incoming call processing in background mode
  • Fix for camera being freezed during the call, improvements for camera stuff
  • Default capture resolution is 640x480 now
  • Bugfix and stability improvements

2.8.0

  • Dependency update: VoxImplantWebRTC is updated to 60.0.0
  • Fix for ios 8.0 support
  • Fix for inability to set custom video source for a call (issue was introduced in 2.7.0)

2.7.0

  • It is now possible to explicitly specify if video send/receive is required while initiating an outgoing call or accepting incoiming call. You can find related changes in the VIClient callToUser:withSendVideo:receiveVideo:customData: and VICall answerWithSendVideo:receiveVideo:customData:headers:. VICall startWithVideo:headers: is changed to [VICall startWithHeaders:]
  • Introduce new API: VICall startReceiveVideoWithCompletion to start receive video, if video receive was not enabled before.
  • Dependency change: Cocoalumberjack/Swift 3.2.0 is changed to Cocoalumberjack 3.2.0 to simplify iOS SDK integration to Objective-C projects

2.6.0

  • Messaging API

2.5.0

2.4.1

  • Add new dependency - Cocoalumberjack/Swift 3.2.0, that adds ability to save logs to file

2.4.0

  • Introduce custom video source for alternative video frame source for a call

2.3.0

  • Experimental h.264 support can be enabled via the new API

2.2.2

  • Add ability to get call statistics

2.2.1

  • Bugfix for double connect call on push notification

2.2.0

  • New backward-compatible API. Please note, that you should not use old and new API simultaneously.