0.0.5
What's new
-
[Android Platform]
-
Supports Signed Call Android SDK v0.0.5 which is compatible with CleverTap Android SDK v5.2.2.
-
Introduces new properties
initiatorImage
andreceiverImage
in theMissedCallActionClickResult
instance provided through theSignedCall.addListener(SignedCall.SignedCallOnMissedCallActionClicked,(result:MissedCallActionClickResult) => {})
listener. -
Introduces a new public API:
SignedCallOnCallStatusListener.register(applicationContext)
. This API allows your application to receive VoIP call events through theSignedCall.SignedCallOnCallStatusChanged
listener even when the app is in a killed state.For detailed integration instructions, please refer to the documentation.
-
-
[iOS Platform]
- Supports Signed Call iOS SDK v0.0.6 which is compatible with CleverTap iOS SDK v5.2.2.
Breaking Changes
- [Android and iOS Platform]
- The
SignedCall.SignedCallOnCallStatusChanged
listener will now provide an instance of theCallEventResult
class instead of theCallEvent
class. Please refer to the integration documentation for details on usage.
- The
- [iOS Platform]
- iOS deployment target version is bumped to iOS 12.
Behaviour Changes
-
[Android Platform]
- Handles UX issues during network loss or switch by invalidating the socket reconnection and establishing an active connection to process the call related actions.
- Modifies the SDK's behavior when the Notifications Settings are disabled for the application. Previously, if the app's notifications were disabled, the device rang on incoming calls without displaying the call screen in the background and killed states. In this version, the SDK now declines incoming calls when the notifications are disabled. If the notification settings are later enabled, the SDK resumes processing calls instead of automatically declining them.
-
[Android and iOS Platform]
- The
SignedCall.addListener(SignedCall.SignedCallOnCallStatusChanged,(result:CallEventResult) => {})
listener will now provide updates in the call state to both the initiator and receiver of the call. Previously, it was exposed only to the initiator of the call.
- The
Bug Fixes
-
[Android Platform]
- Fixes multiple outgoing call requests initiated simultaneously through multiple calls of
SignedCall.call(receiverCuid, callContext, callProperties)
. The SDK now processes only one call at a time while rejecting other requests with a failure exception. - Addresses an IllegalStateException which occurs while prompting the user with the poor/bad network conditions on the call-screen.
- Fixes multiple outgoing call requests initiated simultaneously through multiple calls of
-
[Android and iOS Platform]
- Addresses an infinite Connecting state issue on the call screen which was triggered by using CUIDs longer than 15 characters. In this version, the SDK extends support to CUIDs ranging from 5 to 50 characters.