Project

General

Profile

Release Notes for Mobile SDK 5.2.66

User documentation
2024-03-05

Release Notes For Release 5.2.66

API Changes

  • Added optional sipStartFailed(String error) event. When implemented in the event listener, The Cloudonix Mobile SDK will send it instead of the old sipStartFailed and it will contain the reason for the failure.

Android

  • Due to permission issues and requirements for new applications, The minimum SDK version required was update to Android 7.0, dropping support for about 1.6% of Android devices that are still on Android 6.0 (according to APIlevels.com, as of 14-11-2023).
  • Added a new API to help Android developers figure out which missing permissions the SDK needs to operate: CloudonixSDKClient.checkForMissingPermissions(). This will return a list of all permissions that are needed - according to the device's Android version.
  • Added a new API to automate handling incoming Cloudonix Platform Registration-Free calls: CloudonixSDKClient.pickupRegistrationFreeCall(). Assuming the application has access to all the details of the Cloudonix Registration-Free Incoming Call Notification, this API handles the Ringing Notification requirements as well as all the call setup and tear down (in case of cancel). This API is experimental and is not yet available on the Cloudonix Mobile SDK for iOS.

Issues Fixed

General

  • Mitigate issue #2135: Prevent some cases where a new call fails before sending CALL_STATE_STARTING leaving the SDK in an invalid state where the existing call is not disconnected, the app cannot disconnect it without knowing the call key, and no other calls can be made. The SDK will not properly report and clear such calls by sending CALL_STATE_STARTING immediately followed by CALL_STATE_DISCONNECTED.

Android

  • Issue #2096: Initialize foreground service correctly on Android 14.
  • Issue #2104: Fixed an NPE during shutdown quickly after restart.
  • Issue #2130: A security issue due to missing POST_NOTIFICATIONS permissions in Android 33 is mishandled and cause a crash.
  • Issue #2133: Fixed an NPE during shutdown if the service did not complete starting properlty.

Files