January 2025

We are excited to share the January SDK changelog for our product!

πŸ“˜

Note

Click each SDK header to view the corresponding GitHub repository for release details.

January 7

What's New

🚧

Downgrade Advisory

After upgrading to Android SDK v7.2.0, avoid downgrading in subsequent app releases. If you face any issue after upgrading to this version, contact the CleverTap Support team for assistance.

What's New

  • Supports Android 15. For more information, refer to Android 15.
  • Updates the minimum supported Android SDK version to API level 21 (Android 5.0).

What's New

  • Supports Android 15. For more information, refer to Android 15.
  • Updates the minimum supported Android SDK version to API level 21 (Android 5.0).

What's New

  • Supports Android 15. For more information, refer to Android 15.
  • Updates the minimum supported Android SDK version to API level 21 (Android 5.0).

January 2

What's New

  • Enhanced Call Disconnection Details
    • The callStatus(SCCallStatusDetails callDetails) callback now provides detailed reasons for call disconnection through the following new events:
      • VoIPCallStatus.CALL_OVER_DUE_TO_LOCAL_NETWORK_LOSS: Triggered when the call disconnects due to network loss at the initiator's end.
      • VoIPCallStatus.CALL_OVER_DUE_TO_REMOTE_NETWORK_LOSS: Triggered when the call disconnects due to network loss at the receiver's end.

        πŸ“˜

        Note

        The above events are reported alongside the existing VoIPCallStatus.CALL_OVER event for seamless integration with older implementation.

  • Customized Branding
    • Local and remote branding settings are now interoperable. Use the SignedCallScreenBranding.builder class to customize specific branding properties locally while leveraging remote branding settings configured on the CleverTap dashboard. For more information on setting the local branding, refer to Set Local Branding for Call Screen.

Enhancements

  • SCEnd System Event Updates
    • Adds a new boolean property hangup_initiator to indicate which party initiated the hangup.
    • Captures the cause of disconnection for over call-status events through the reason property, with the following possible values:
      • network_lost: Indicates that the hangup occurred due to the network loss on the call initiator's end (corresponds to VoIPCallStatus.CALL_OVER_DUE_TO_LOCAL_NETWORK_LOSS).
      • network_dropped: Indicates that the hangup occurred due to the network loss on the receiver's end (corresponds to VoIPCallStatus.CALL_OVER_DUE_TO_REMOTE_NETWORK_LOSS).
      • user_initiated: Indicates that the hangup was initiated by the user (corresponds to VoIPCallStatus.CALL_OVER).

Bug Fixes

  • Resolves an issue where the channel property in SCEnd system events was incorrectly recorded as socket at the initiator end instead of fcm.