1. Developer Guide
  2. Release Notes
  3. React Native SDK
Changelog
info

Information

You can now get notified whenever MoEngage releases a new version of the React Native SDK. For more information, refer to Subscribe to MoEngage SDK Releases.

For privacy manifest support on iOS, please make sure that you are on React Native SDK Version 9.0.0 or above and iOS SDK Version 9.16.2 or above. Want to know more about privacy manifest ? Refer this link

25th November 2024

 

Plugins Android Dependencies

core: 11.1.1

cards:5.0.1

geofence:6.0.2

inbox:5.0.2

AGP: 8.4.0

Kotlin: 1.9.23

Compile SDK Version: 34

Gradle Version: 8.6

 

 

Core 11.1.0

What's New

  •  

 

30th September 2024

 

Plugins Android Dependencies

core: 11.1.0

cards:5.0.0

geofence:6.0.1

inbox:5.0.1

AGP: 8.4.0

Kotlin: 1.9.23

Compile SDK Version: 34

Gradle Version: 8.6

 

 

Core 11.1.0

What's New

  • Android
    • moe-android-sdk version updated to 13.05.01
    • inapp version updated to 8.7.0
  • iOS
    • Internal dependency version update.

Improvements

  • Fixed the lint issue for `getMoEInAppRules` with `noImplicitAny` as false in tsconfig file

Cards 5.0.1

What's New

  • Android
    • cards-core version updated to 2.3.1
  • iOS
    • Internal dependency version update.

Inbox 5.0.2

What's New

  • Android
    • inbox-core version updated to 3.2.1
  • iOS
    • Internal dependency version update.

Geofence 6.0.1

What's New

  • Android
    • geofence version updated to 4.2.1
  • iOS
    • Internal dependency version update.

 

07-08-2024

Core 11.0.0

  • iOS

    • Added support for tracking custom boolean attributes in two formats: 0/1 and TRUE/FALSE Refer to the documentation for more information.

      info

      Custom Boolean Attribute Tracking in iOS.

      Updating to this version of the SDK will cause MoEngage to start tracking custom user attributes in Boolean syntax as TRUE/FALSE instead of the current 1/0 for iOS devices. This may affect your segmentation and trigger conditions. 

      In this version,  you now have the flexibility to choose how to track custom user attributes with boolean data types. By default, iOS will align with the Android tracking method using TRUE/FALSE. However, you still have the option to continue using the existing 1/0 tracking method if it better suits your campaign requirements.

      We recommend migrating to the new TRUE/FALSE method for consistency across platforms. However, we understand that you may have specific use cases where the 1/0 tracking method is preferred. To set your preference, please refer to the custom attribute tracking section in our developer documentation.
    • MoEngage-iOS-SDK version updated to 9.18.1

Inbox 5.0.0

  • iOS
    • MoEngageInbox version updated to ~>2.17.0

Cards 4.0.0

  • iOS
    • MoEngageCards version updated to 4.17.1

Geofence 6.0.0

  • iOS
    • MoEngageGeofence SDK version updated to ~>5.17.0

31-07-2024

Core 10.3.0

warning

Warning

Updating to this version of the SDK will cause MoEngage to start tracking custom user attributes in Boolean syntax as TRUE/FALSE instead of the current 1/0 for iOS devices. This may have an effect to your segmentation and trigger conditions. If you wish to continue with the current 1/0 system, we recommend to skip upgrading this version, this will be configurable from 11.0.0 onwards.
  • Typescript configuration issue fixes.
  • Android
    • Added support for AGP 8.4.0 and above
    • Kotlin version updated to 1.9.23
    • Compile SDK version updated to 34
    • moe-android-sdk version updated to 13.04.00
    • inapp version updated to 8.5.0
  • iOS
    • MoEngage-iOS-SDK version updated to ~>9.18.0

Inbox 4.1.0

  • Typescript configuration issue fixes.
  • Android
    • Added support for AGP 8.4.0 and above
    • Kotlin version updated to 1.9.23
    • Compile SDK version updated to 34
    • inbox-core version updated to 3.1.0
  • iOS
    • MoEngageInbox version updated to ~>2.17.0

Cards 3.1.0

  • Typescript configuration issue fixes.
  • Android
    • Added support for AGP 8.4.0 and above
    • Kotlin version updated to 1.9.23
    • Compile SDK version updated to 34
    • cards-core version updated to 2.2.0
  • iOS
    • MoEngageCards version updated to ~>4.17.0

Geofence 5.1.0

  • Typescript configuration issue fixes.
  • Android
    • Added support for AGP 8.4.0 and above
    • Kotlin version updated to 1.9.23
    • Compile SDK version updated to 34
    • geofence version updated to 4.2.0
  • iOS
    • MoEngageGeofence SDK version updated to ~>5.17.0

03-07-2024

Core 10.2.0

warning

Warning

Updating to this version of the SDK will cause MoEngage to start tracking custom user attributes in Boolean syntax as TRUE/FALSE instead of the current 1/0 for iOS devices. This may have an effect to your segmentation and trigger conditions. If you wish to continue with the current 1/0 system, we recommend to skip upgrading this version, this will be configurable from 11.0.0 onwards.
  • JSON Object and JSON Array tracking support in user attributes.
  • Support for forcing SDK to a specific MoEngage Environment
  • Android
    •  moe-android-sdk version updated to 13.02.00
    •  inapp version updated to 8.3.1

Inbox 4.0.2

  • Android
    • inbox-core version updated to 3.0.2
  • iOS
    • MoEngageInbox version updated to ~>2.16.0

Cards 3.0.2

  • Android
    • cards-core version updated to 2.0.2
  • iOS
    • MoEngageCards version updated to ~>4.16.0

Geofence 5.0.2

  • Android
    • geofence version updated to 4.0.2
  • iOS
    • MoEngageGeofence version updated to ~>5.16.0

16-05-2024

Core 10.1.0

warning

Warning

Updating to this version of the SDK will cause MoEngage to start tracking custom user attributes in Boolean syntax as TRUE/FALSE instead of the current 1/0 for iOS devices. This may have an effect to your segmentation and trigger conditions. If you wish to continue with the current 1/0 system, we recommend to skip upgrading this version, this will be configurable from 11.0.0 onwards.
  • Adding support for Data Center 6
  • Android
    •  moe-android-sdk version updated to `13.01.00`
    •  inapp version updated to `8.3.0`

14-05-2024

Core 10.0.1

warning

Warning

Updating to this version of the SDK will cause MoEngage to start tracking custom user attributes in Boolean syntax as TRUE/FALSE instead of the current 1/0 for iOS devices. This may have an effect to your segmentation and trigger conditions. If you wish to continue with the current 1/0 system, we recommend to skip upgrading this version, this will be configurable from 11.0.0 onwards.
  • Bugfix

    • Adding backward compatibility support for react-native version with react-native-moengage 10.x.x

Inbox 4.0.1

  • Bugfix

    • Adding backward compatibility support for react-native version with react-native-moengage-inbox 4.x.x

Cards 3.0.1

  • Bugfix

    • Adding backward compatibility support for react-native version with react-native-moengage-cards 3.x.x

Geofence 5.0.1

  • Bugfix

    • Adding backward compatibility support for react-native version with react-native-moengage-geofence 5.x.x

07-05-2024

Release of react-native-moengage version 10.0.0

10.0.0 Compatible packages

androidx.lifecycle:lifecycle-process:2.7.0 (2.6.2 also can be used, but please test in apps and push)

com.moengage:rich-notification:5.0.1

react-native-moengage-cards - 3.0.0

react-native-moengage-inbox - 4.0.0

 

com.moengage:moe-android-sdk: - No need to add this dependency anymore, MoEngage automatically manages the compatibility between android core and react-native-moengage SDKs.

com.moengage:inapp: - No need to add this dependency anymore, MoEngage automatically manages InApp dependency.

com.moengage:cards-core - No need to add this dependency anymore, MoEngage automatically manages cards dependency.

com.moengage:inbox-core - No need to add this dependency anymore, MoEngage automatically manages inbox dependency.

Core 10.0.0

warning

Warning

Updating to this version of the SDK will cause MoEngage to start tracking custom user attributes in Boolean syntax as TRUE/FALSE instead of the current 1/0 for iOS devices. This may have an effect to your segmentation and trigger conditions. If you wish to continue with the current 1/0 system, we recommend to skip upgrading this version, this will be configurable from 11.0.0 onwards.

  • Added support for Turbo Architecture

    • If you are using Turbo Architecture, you need to use React version 0.73. otherwise, you will face build issues. 
  • Breaking APIs in Javascript
    Then Now

    optOutDataTracking(false)

    enableDataTracking()

    optOutDataTracking(true)

    disableDataTracking()
  • iOS

    • Removed support for SDK initialization from Info.plist.

    • Removed APIs
      List of removed APIs

      - (void)initializeDefaultInstance:(NSDictionary*)launchOptions;

      - (void)initializeDefaultInstanceWithState:(MoEngageSDKState)sdkState andLaunchOptions:(NSDictionary*)launchOptions;

      - (void)initializeDefaultInstance:(BOOL)isSdkEnabled andLaunchOptions:(NSDictionary*)launchOptions;

      - (void)initializeDefaultSDKConfig:(MoEngageSDKConfig*)sdkConfig withSDKState:(BOOL)isSdkEnabled andLaunchOptions:(NSDictionary*)launchOptions
  • Android

    • Making moe-android-sdk and inapp artifact as a part of react-native-moengage plugin.

Inbox 4.0.0

  • Added support for Turbo Architecture

  • Android

    • Making inbox-core artifact as a part of react-native-moengage-inbox plugin.

Cards 3.0.0

  • Added support for Turbo Architecture
  •  Android

    • Making cards-core artifact as a part of react-native-moengage-cards plugin.

Geofence 5.0.0

  • Added support for Turbo Architecture 
  •  Android

    • Making geofence artifact as a part of react-native-moengage-geofence plugin.

08-04-2024

Release of react-native-moengage version 9.1.0

9.1.0 compatible packages

com.moengage:moe-android-sdk:13.00.03

androidx.lifecycle:lifecycle-process:2.7.0 (2.6.2 also can be used, but please test inapp and push)

com.moengage:cards-core:2.0.2   //self handled cards

com.moengage:inapp:8.2.0

com.moengage:rich-notification:5.0.1

Requirements

  1. AGP >= 7.4
  2. If you are upgrading to AGP 8 -> AGP upgrade breaking changes - https://developer.android.com/build/releases/past-releases/agp-8-0-0-release-notes

Core 9.1.0

warning

Warning

Updating to this version of the SDK will cause MoEngage to start tracking custom user attributes in Boolean syntax as TRUE/FALSE instead of the current 1/0 for iOS devices. This may have an effect to your segmentation and trigger conditions. If you wish to continue with the current 1/0 system, we recommend to skip upgrading this version, this will be configurable from 11.0.0 onwards.
  • Support for Intrusive InApp in TV Platform.
  • iOS
    • Updated the dependency to MoEngage-iOS-SDK 9.17.0, refer to release notes for more details.

Inbox 3.1.0

  • iOS
    • MoEngageInbox SDK version updated to 2.16.0.

Cards 2.1.0

  •  iOS
    • MoEngageCards dependency updated to 4.16.0 and above.

Geofence 4.1.0

  •  iOS
    • MoEngageGeofence SDK version updated to 5.16.0.

18-03-2024

Core 9.0.0

  • Added support for displaying non-intrusive nudge campaigns
  • Removed support for MI Push
  • Bugfix
    • Exception thrown `MoEInAppSelfHandledCampaign is an invalid object` while logging
  • Android
    • Support for Native Android SDK version 13.00.00 and above, refer to the release notes for more details. 
  • iOS
    • Updated the dependency to MoEngage-iOS-SDK 9.16.1, refer to release notes for more details.

Inbox 3.0.1

  • Android
    • Support for Native Android SDK version 13.00.00 and above, refer to the release notes for more details. 
  • iOS
    • MoEngageInbox SDK version updated to 2.15.0.

Cards 2.0.1

  • Android
    • Support for Native Android SDK version 13.00.00 and above, refer to the release notes for more details. 
  •  iOS
    • MoEngageCards dependency updated to 4.15.1 and above.

Geofence 4.0.1

  • Android
    • Support for Native Android SDK version 13.00.00 and above, refer to the release notes for more details. 
  •  iOS
    • MoEngageGeofence SDK version updated to 5.15.0.

24-02-2024

Core 8.7.1

  • Android 
    • Fixed the compile issue due to Java 17 in react-native 0.73.0

Inbox 2.6.1

  • Android 
    • Fixed the compile issue due to Java 17 in react-native 0.73.0

Cards 1.2.1

  • Android 
    • Fixed the compile issue due to Java 17 in react-native 0.73.0

Geofence 3.6.1

  • Android 
    • Fixed the compile issue due to Java 17 in react-native 0.73.0

29-01-2024

Core 8.7.0

  • Added TV OS support
  • iOS
    • Updated the dependency to MoEngage-iOS-SDK 9.15.0, refer to release notes for more details.

Inbox 2.6.0

  • iOS
    • MoEngageInbox SDK version updated to 2.14.0.

Cards 1.2.0

  • iOS
    • MoEngageCards dependency updated to 4.14.0 and above.

Geofence 3.6.0

  • iOS
    • MoEngageGeofence SDK version updated to 5.14.0.

29-11-2023

Core 8.6.0

  • Support for tracking an array of numbers and strings in user attributes
  • Android 
    • Support for Native Android SDK version 12.10.00, refer to the release notes for more details.
    • Google Policy - API to delete User details.
    • Android 14 policy updates.
  • iOS
    • Updated the dependency to MoEngage-iOS-SDK 9.13.0

Inbox 2.5.0

  • Android 
    • Support for Native Android SDK version 12.10.00, refer to the release notes for more details.
  • iOS
    • MoEngageInbox SDK version updated to 2.12.0.

Cards 1.1.0

  • Android
    • Support for Native Android SDK version 12.10.00, refer to the release notes for more details.
  • iOS
    • MoEngageCards dependency updated to 4.12.0 and above.

Geofence 3.5.0

  • Android
    • Support for Native Android SDK version 12.10.00, refer to the release notes for more details.
  • iOS
    • MoEngageGeofence SDK version updated to 5.12.0.

30-10-2023

Core 8.5.4

  • Android
    • Bugfix
      • MoEngage SDK throwing incompatible version error on app open

31-08-2023

Inbox 2.4.3

  • Bugfix
    • PeerDependency version mismatch for react-native-moengage

Geofence 3.4.3

  • Bugfix
    • PeerDependency version mismatch for react-native-moengage

Cards 1.0.1

  • Bugfix
    • PeerDependency version mismatch for react-native-moengage

31-08-2023

Core 8.5.3

  • iOS
    • Updated the dependency to MoEngage-iOS-SDK 9.11.0

Inbox 2.4.2

  • iOS
    • Updated the dependency to MoEngageInbox 2.11.0

Geofence 3.4.2

  • iOS
    • Updated the dependency to MoEngageGeofence 5.11.0

Cards 1.0.0

  • Added support for Self-Handled cards

17-08-2023

Core 8.5.2

  • Android
    • Bugfix
      • Self-handled InApp delivery controls not working.
      • Import error for MoEngageLogLevel.INFO in MoEConstant.ts.

18-07-2023

Core 8.5.1

  • Android
    • Adding type check config for TypeScript files
    • Support for configuring the plugin console logs

Inbox 2.4.1

  • Android
    • Adding type check config for TypeScript files
    • Support for configuring the plugin console logs
    • Adding the core module as a peer dependency

Geofence 3.4.1

  • Android
    • Adding type check config for TypeScript files
    • Support for configuring the React-Native Plugin console logs
    • Adding the core module as a peer dependency

25-05-2023

Core 8.5.0

  • Android
    • Target & Compile SDK Version Updated to 33.
    • Support For SelfHandled Push Notification Clicks In Foreground State.
    • Bugfix
      • Self-handled callback not working for test InApp and event-triggered InApp.
  • iOS

    • MoEngage-iOS-SDK version updated to 9.8.0.

Inbox 2.4.0

  • Android
    • Target & Compile SDK Version Updated to 33.
  •  iOS
    • MoEngageInbox SDK version updated to 2.8.0.

Geofence 3.4.0

  • Android
    • Target & Compile SDK Version Updated to 33.
  • iOS

    • MoEngageGeofence SDK version updated to 5.8.0.

16-02-2023

Core 8.4.0

  • iOS
    • MoEngage-iOS-SDK version updated to 9.4.0

Inbox 2.3.0

  • iOS
    • MoEngageInbox SDK version updated to 2.4.0

Geofence 3.3.0

  • Android
    • configureGeofence() is deprecated. Use startGeofenceMonitoring() and stopGeofenceMonitoring() in the Geofence module.
  • iOS

    • MoEngageGeofence SDK version updated to 5.4.0.

    • Support for stopGeofenceMonitoring() API.

09-02-2023

Core 8.3.0

  • Android
    • Android 13 push notification Opt-in with rationale via In-Apps.
    • Support for enabling/disabling Device Id tracking.
    • Bugfix
      • The push-click callback is delivered only after the activity is resumed.

17-01-2023

Core 8.2.0

  • iOS

    • MoEngage-iOS-SDK version updated to 9.2.0

    • Updated APIs
      Then Now

      - (void)initializeDefaultSDKConfig:(MOSDKConfig*)sdkConfig andLaunchOptions:(NSDictionary*)launchOptions;

      -(void)initializeDefaultSDKConfig:(MoEngageSDKConfig*)sdkConfig andLaunchOptions:(NSDictionary*)launchOptions;

      - (void)initializeDefaultSDKConfigWithState:(MOSDKConfig*)sdkConfig withSDKState:(MoEngageSDKState)sdkState andLaunchOptions:(NSDictionary*)launchOptions;

      - (void)initializeDefaultSDKConfigWithState:(MoEngageSDKConfig*)sdkConfig withSDKState:(MoEngageSDKState)sdkState andLaunchOptions:(NSDictionary*)launchOptions;

Inbox 2.2.0

  • iOS

    • MoEngageInbox SDK version updated to 2.2.0.

Geofence 3.2.0

  • iOS

    • MoEngageGeofence SDK version updated to 5.2.0.

21-11-2022

Core 8.1.2

  • Bugfix

    • Updated the import statement to make the plugin compatible with C++ codebase.

09-11-2022

Core 8.1.1

  • Bugfix
    • Added missing MoEngageRichNotification dependency to the plugin.

Inbox 2.1.1

  • Bugfix
    • The payload of fetchAllMessages() is not in sync with the defined model.
    • trackMessageClicked() and deleteMessage() not working on Android if the campaign has an image.

28-10-2022

Core 8.1.0

  • Android
    • Support for Android 13 notification permission
    • Support for Android Gradle Plugin version 7.3.1
    • Build Configuration Update
      • Compile SDK version - 31
      • Target SDK version - 31
    • Support for Android SDK version 12.4.00 and above
  • iOS
    • Initialization APIs are updated to initialize SDK with the state.
      Then Now
      initializeDefaultInstance(_ config: MOSDKConfig, sdkState: Bool = true, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil)
      initializeDefaultInstance(config: MOSDKConfig, sdkState: MoEngageSDKState = .enabled, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil)

Inbox 2.1.0

  • Android
    • Android Gradle Plugin version updated to 7.3.1
    • Gradle version updated to 7.4
    • Compile SDK Version - 31
    • Target SDK version - 31
    • Support for Android SDK version 12.4.00
    • Inbox Core 2.2.0

Geofence 3.1.0

  • iOS
    • MoEngageGeofence SDK version updated to ~>4.4.0.

27-09-2022

Core 8.0.0

  • Support for Android SDK version 12.3.02 and above.
  • Support for iOS SDK version 8.3.1 and above.
  • TS Lint warnings resolved.
  • Breaking Changes
    • InApp Model MoEInAppCampaign broken down from a single object to multiple objects
      • MoEInAppData
      • MoEClickData
      • MoESelfHandledCampaignData
    • Push Model
      • MoEPushCampaign --> MoEPushPayload
    • Breaking APIs in Javascript
      Then Now
      initialize() initialize(appId)
    • Removed APIs
      List of removed APIs
      selfHandledPrimaryClicked()
      enableSDKLogs()
      optOutInAppNotification()
      optOutPushNotification()
  • Android
    • Build Configuration Updates
      • Minimum SDK Version - 21
      • Target SDK Version - 30
      • Compile SDK Version - 30
    • Mi SDK update to Version 5.x.x, refer to the Configuring Xiaomi Push and update the integration
    • Deprecated APIs
      Then Now
      MoEInitializer.initialize(Context, MoEngage.Builder) MoEInitializer.initializeDefaultInstance(Context, MoEngage.Builder)
      MoEInitializer.initialize(Context, MoEngage.Builder, SdkState) MoEInitializer.initializeDefaultInstance(Context, MoEngage.Builder, SdkState)
  • iOS
    • MOReactInitializer renamed to MoEngageInitializer
    • Deprecated APIs
      Then Now
      - (void)intializeSDKWithLaunchOptions:(NSDictionary*)launchOptions; - (void)initializeDefaultInstance:(NSDictionary*)launchOptions;
      - (void)intializeSDKWithState:(BOOL)isSdkEnabled andLaunchOptions:(NSDictionary*)launchOptions; - (void)initializeDefaultInstance:(BOOL)isSdkEnabled andLaunchOptions:(NSDictionary*)launchOptions;
      - (void)intializeSDKWithConfig:(MOSDKConfig*)sdkConfig andLaunchOptions:(NSDictionary*)launchOptions; - (void)initializeDefaultSDKConfig:(MOSDKConfig*)sdkConfig andLaunchOptions:(NSDictionary*)launchOptions;
      - (void)intializeSDKWithConfig:(MOSDKConfig*)sdkConfig withSDKState:(BOOL)isSdkEnabled andLaunchOptions:(NSDictionary*)launchOptions; - (void)initializeDefaultSDKConfig:(MOSDKConfig*)sdkConfig withSDKState:(BOOL)isSdkEnabled andLaunchOptions:(NSDictionary*)launchOptions;

Inbox 2.0.0

  • Support for Android SDK version 12.3.02 and above.
  • Support for iOS SDK version 8.3.1 and above.
  • TS Lint warnings resolved.
  • Breaking Changes
    • MoEReactInbox.initialize("YOUR_APP_ID"); should be called before calling any other method.
  • Android
    • Build Configuration Updates
      • Minimum SDK Version - 21
      • Target SDK Version - 30
      • Compile SDK Version - 30

Geofence 3.0.0

  • Support for iOS SDK version 8.3.1 and above, Geofence version 4.3.0 and above.

Core v7.4.1

Release Date: 15th July 2022

  • Device identifier tracking update as per Google's User Data policy. Advertising Id is only tracked after user consent. Along with the plugin update the Native Android dependency to 11.6.02.

Core v7.4.0

Release Date: 12th May 2022

  • Bugfix iOS:

    • Fixed the PushClick callback issue in terminated state, which appeared when the react-native version was above 0.65.

Inbox v1.2.0

Release Date: 12th May 2022

  • iOS
    • Native SDK version updated to  ~> 7.2.0.
    • Base plugin version dependency updated to  ~> 2.3.0.

Geofence v2.2.0

Release Date: 16th May 2022

  • iOS
    • Native SDK version updated to  ~> 7.2.0.
    • Base plugin version dependency updated to  ~> 2.3.0.

Core v7.3.0

Release Date: 16th September 2021

  • HTML InApp Support Added.
  • Bugfix:
    • Handled trackEvent() with null properties.
  • iOS:
    • Native SDK version updated to  ~> 7.1.0.
    • Base plugin version dependency updated to  ~> 2.1.0.
  • Android:
    • Native SDK updated to support version  11.4.00  and above.
    • Bugfix:
      • enableSDKLogs() was not working

Inbox v1.1.0

Release Date: 16th September 2021

  • iOS
    • Native SDK version updated to  ~> 7.1.0.
    • Base plugin version dependency updated to  ~> 2.1.0.
  • Android
    • Base plugin version dependency updated to 2.2.0.

Inbox v1.0.0

Release Date: 31st August

  • Initial Release
  • APIs
    • Fetch All Messages
    • Get unclicked count
    • Track message clicked
    • Delete message

Core v7.2.0

Release Date: 11th May 2021

  • Android SDK updated to support 11.2.00 and above.

Core v7.1.0

Release Date: 17th March 2021

  • Added support to pass Array(String/Number) as event attributes in addAttribute method of MoEProperties.

Core v7.0.0

Release Date: 25th February 2021

  • Plugin now supports iOS 10.0 and above
  • iOS Native Dependencies updated to support MoEngage-iOS-SDK 7.* and above
  • Android Native SDK updated to support 11.0.04 and above. Refer to the Release Notes for behaviour changes.
  • API to pass PushKit Token JS
  • Added APIs to enable and disable MoEngage SDK.
  • Added API to register a callback for push token-generated event.

Core v6.1.7

Release Date: 15th February 2021

  • Android dependencies updated to use versions published on Maven Central.

Core v6.1.6

Release Date: 21st January 2021

  • BugFix iOS: Token registered event produced an error as it's currently not supported in React Native.

Core v6.1.5

Release Date: 18th January 2021

  • Updated iOS MoEPluginBase dependency to support version 1.2 and above.

Core v6.1.4

Release Date: 8th December 2020

  • Support for extending Native Android Callbacks if required.
  • iOS Base Plugin Updated to version 1.1.1 to ensure SDK sets the UNUserNotification Center delegate only in cases where it's nil.

Core v6.1.3

Release Date: 25th November 2020

  • APIs exposed customizing the Push notification in Android.

Core v6.1.1

Release Date: 22nd October 2020

  • Bugfix
    • Events not being marked as non-interactive on Android

Core v6.1.0

Release Date: 23rd September 2020

  • Support for Push Templates
  • Android moved to androidx namespace.

Core v6.0.0

Release Date: 7th August 2020

  • Breaking change in Initialization of iOS platform, refer to the developer docs to know more about the changes.
  • Support for Self-Handled In-App
  • Support for In-App V3
  • Event listeners now return a model Object instead of JSON
  • setUserBirthday() only accepts ISO-8601 String
  • Breaking changes in APIs
  • Android Native SDK dependency changed to support versions greater than 10.2.02 and above.
  • iOS Native SDK dependency changed to support versions greater than 6.0.0.

 

Then

 Now
ReactMoE.isExistingUser(boolean) ReactMoE.setAppStatus(MoEAppStatus)
ReactMoE.trackEvent(string, JSONObject) ReactMoE.trackEvent(string, MoEProperties
ReactMoE.setUserLocation(number, number) ReactMoE.setUserLocation(MoEGeoLocation)
ReactMoE.setUserAttributeLocation(string, number, number) ReactMoE.setUserAttributeLocation(string, MoEGeoLocation)
ReactMoE.setLogLevel(number) ReactMoE.enableSDKLogs()
  • Android Specific Changes
    • APIs to pass push token and payload has changed
      Then Now
      ReactMoE.passPushToken(string) ReactMoE.passFcmPushToken(string)
      ReactMoE.passPushPayload(JSONObject) ReactMoE.passFcmPushPayload(JSONObject)

Core v5.0.0

Release Date: 18th Feb 2020

  • New Event Listeners added for both iOS and Android platforms i.e, pushClicked, inAppCampaignShown and inAppCampaignShown.
  • Earlier iOS Push and InApp Events deprecated to have it common for both Android and iOS platfroms. (notificationClicked, inAppShown and inAppClicked)
  • APIs to pass push token and payload from React-Native Component/Javascript (Android Only API)

Core v4.1.0

Release Date: 23rd Dec 2019

  • Android SDK version updated to 9.8.01

Previous

Next

Was this article helpful?
0 out of 1 found this helpful

How can we improve this article?