Skip to content

1.2.0

Compare
Choose a tag to compare
@shivamsharma2710 shivamsharma2710 released this 18 Aug 12:21
· 87 commits to master since this release
8348417

What's new

  • [Android Platform]

    • Supports CleverTap Android SDK v5.2.0.
    • Note: RenderMax Push SDK functionality is now supported directly within the CleverTap Core SDK. Please remove the integrated RenderMax SDK before you upgrade to CleverTap React Native SDK for this version.
    • Adds support for developer defined default notification channel. Please refer to the Usage.md file to read more on how to setup default channel in your app. Also please note that this is only supported for CleverTap core notifications. Support for push templates will be released soon.
  • [iOS Platform]

  • [Android and iOS Platform]

    • Adds support for encryption of PII data wiz. Email, Identity, Name and Phone. Please refer to Usage.md file to read more on how to enable/disable encryption of PII data.
    • Adds support for custom KV pairs common to all inbox messages in App Inbox.

API Changes

  • [Android Platform]
    • Adds SCCampaignOptOut Event to Restricted Events Name List for internal use.
    • Adds custom sdk versions to af field for internal use.

Breaking API Changes

  • [Android Platform]
    • CTFlushPushImpressionsWork breaks custom WorkerFactory implementation of an App:
      • If you are using custom WorkFactory implementation of WorkManager for Android platform then make sure that you correctly handle workers defined by CleverTap SDK and other third party dependencies.
      • You must return null from createWorker() for any unknown workerClassName. Please check implementation provided in the blog here.

Bug Fixes

  • [Android Platform]
    • Fixes #393 - push permission flow crash when context in CoreMetadata is null.
    • Fixes #428 - Race-condition when detecting if an in-app message should show.
    • Fixes Push primer alert dialog freeze behavior, which became unresponsive when clicked outside the window.
    • Fixes a bug where addMultiValueForKey and addMultiValuesForKey were overwriting the current values of the user properties instead of appending it.