info |
Information
|
29th January 2025
Compatible Android packages
com.moengage:moe-android-sdk:13.05.02
com.moengage:inapp:8.7.1
com.moengage:cards-core:2.3.2
com.moengage:geofence:4.2.1
com.moengage:inbox-core:3.2.1
Note: The above versions already bundled part of respective Flutter plugins, so you do not need to include them.
com.moengage:rich-notification:5.1.2
Compatible MoE Android version catalog - 4.5.3
Cards 5.1.0
-
Android
- cards-core version updated to 2.3.2.
-
iOS
- MoEngage-Cards version updated to 4.19.1.
Inbox 8.1.0
-
Android
- inbox-core version updated to 4.2.1
-
iOS
- Updated MoEngageGeofence to 5.19.0
Geofence 5.1.0
-
Android
- geofence version updated to 4.2.1
-
iOS
- Updated MoEngageGeofence to 5.19.0
Core 9.1.0
-
Android
- moe-android-sdk version updated to 13.05.02.
- inapp version updated to 8.7.1
-
iOS
- MoEngage-iOS-SDK version updated to 9.22.1
- Updated MoEngageInApp to 6.04.0
25th November 2024
Plugins | Android Dependencies |
cards:5.0.2 geofence:5.0.2 inbox: 8.0.2 core: 9.0.1 |
AGP: 8.4.0 Kotlin: 1.9.23 Compile SDK Version: 34 Gradle Version: 8.6 |
Compatible Android packages
com.moengage:moe-android-sdk:13.05.00
com.moengage:inapp:8.6.0
com.moengage:cards-core:2.3.0
com.moengage:geofence:4.2.0
com.moengage:inbox-core:3.2.0
Note: The above versions already bundled part of respective flutter plugins, so you no need to include them.
com.moengage:rich-notification:5.1.0
Compatible MoE Android version catalog - 4.5.0
Cards 5.0.2
- Internal Improvements
Inbox 8.0.2
- Internal Improvements
Geofence 5.0.2
- Internal Improvements
Core 9.0.1
- Internal Improvements
3rd October 2024
Plugins | Android Dependencies |
cards:5.0.1 geofence:5.0.1 inbox: 8.0.1 |
AGP: 8.4.0 Kotlin: 1.9.23 Compile SDK Version: 34 Gradle Version: 8.6 |
Cards 5.0.1
Fixes
- Fixed dependency incompatibility issue when upgrading to moengage_flutter version 9.0.0
Inbox 8.0.1
Fixes
- Fixed dependency incompatibility issue when upgrading to moengage_flutter version 9.0.0
Geofence 5.0.1
Fixes
-
Fixed dependency incompatibility issue when upgrading to moengage_flutter version 9.0.0
30th September 2024
Plugins | Android Dependencies |
core: 9.0.0 cards:5.0.0 geofence:5.0.0 inbox: 8.0.0 |
AGP: 8.4.0 Kotlin: 1.9.23 Compile SDK Version: 34 Gradle Version: 8.6 |
warning |
Warning An issue has been identified regarding compatibility between moengage_flutter version 9.0.0 and the dependent packages. Please note the affected packages and their incompatible versions: moengage_geofence version 5.0.0
moengage_geofence should be upgraded to version 5.0.1 or above |
Core 9.0.0
What's New
-
Support multiple self-handled InApps fetch using getSelfHandledInApps().
-
Android
- Bundling native moe-android-sdk & inapp dependencies with the plugin.
- moe-android-sdk version updated to 13.05.00.
- inapp version updated to 8.6.0.
-
Breaking change:
Developers should remove the com.moengage:moe-android-sdk and com.moengage:inapp dependencies from the build.gradle as it is now included with the plugin.
- Note: If using features like hms-pushkit, rich-push, push-amp, etc. please ensure you still need to manually add those dependencies.
-
iOS
- Added support for Provisional Push.
- MoEngage-iOS-SDK version updated to 9.20.0.
Cards 5.0.0
What's New
- Cards fetch on new user attribute unique ID set.
- Breaking changes in API
Then Now MoEngageCards.#setAppOpenSyncListener() MoEngageCards.#setSyncCompleteListener() -
Android
- Bundling native cards-core dependency with the plugin
- cards-core version updated to 2.3.0
-
Breaking change:
Developers should remove the cards-core dependency from the `build.gradle` as it is now included with the plugin.
-
iOS
- MoEngageCards version updated to 4.18.0
Inbox 8.0.0
What's New
-
Android
- Bundling native inbox-core dependency with the plugin
- inbox-core version updated to 3.2.0
-
Breaking change:
Developers should remove the inbox-core dependency from the `build.gradle` as it is now included with the plugin.
-
iOS
- MoEngageInbox version updated to 2.18.0
Geofence 5.0.0
What's New
-
Android
- Bundling native geofence dependency with the plugin
- geofence version updated to 4.2.0
-
Breaking change:
Developers should remove the geofence dependency from the `build.gradle` as it is now included with the plugin.
-
iOS
- MoEngageGeofence version updated to 5.18.0
Core 8.1.0
warning |
Warning This version might have unintentional breaking changes. We recommend not to use this version. Please upgrade to 9.0.0 and please ensure you review the documented changes and integrate these modifications as necessary. |
Geofence 4.1.0
warning |
Warning This version might have unintentional breaking changes. We recommend not to use this version. Please upgrade to 5.0.1 and please ensure you review the documented changes and integrate these modifications as necessary |
Inbox 7.1.0
warning |
Warning This version might have unintentional breaking changes. We recommend not to use this version. Please upgrade to 8.0.1 and please ensure you review the documented changes and integrate these modifications as necessary |
07-08-2024
Core 8.0.0
-
Exact version pinning for Core Module dependencies
- 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.
-
Cards 4.0.0
-
Exact version pinning for Cards Module dependencies
- iOS
-
Internal Improvements
-
Geofence 4.0.0
-
Exact version pinning for Geofence Module dependencies
- iOS
-
Internal Improvements
-
Inbox 7.0.0
- Exact version pinning for Inbox Module dependencies
- iOS
-
Internal Improvements
-
31-07-2024
Core 7.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 8.0.0 onwards. |
- Exact version pinning for Core Module dependencies
- iOS
- Updated MoEngage-iOS-SDK to 9.18.0
- Updated MoEngageInApp to 6.01.0
Cards 3.2.0
- Exact version pinning for Cards Module dependencies
- iOS
- Updated MoEngageCards to 4.17.0
Geofence 3.2.0
- Exact version pinning for Geofence Module dependencies
- iOS
- Updated MoEngageGeofence to 5.17.0
Inbox 6.2.0
- Exact version pinning for Inbox Module dependencies
- iOS
- Updated MoEngageInbox to 2.17.0
15-07-2024
7.1.1 compatible packages
com.moengage:moe-android-sdk:13.03.00
com.moengage:cards-core:2.1.0 //self handled cards
com.moengage:inbox-core:3.1.0
com.moengage:inapp:8.4.0
com.moengage:rich-notification:5.1.0
com.moengage:geofence:4.1.0
androidx.lifecycle:lifecycle-process:2.7.0
Core 7.1.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 8.0.0 onwards. |
- Android: Support for Android SDK version 13.03.00
Cards 3.1.1
- Android
- Support for Android SDK version 13.03.00
- cards-core version updated to 2.1.0
Geofence 3.1.1
- Android
- Support for Android SDK version 13.03.00
- geofence version updated to 4.1.0
Inbox 6.1.1
- Android
- Support for Android SDK version 13.03.00
- inbox-core updated to version 3.1.0
03-07-2024
7.1.0 compatible packages
com.moengage:moe-android-sdk:13.02.00
com.moengage:cards-core:2.0.2 //self handled cards
com.moengage:inapp:8.3.1
com.moengage:rich-notification:5.0.1
com.moengage:geofence:4.0.2
androidx.lifecycle:lifecycle-process:2.7.0
Core 7.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 8.0.0 onwards. |
- Added support for JSONObject values in user attributes
- Added Support for Enforcing SDK into Specific Environments
- Internal Improvements
- Android
-
BugFix
- Event attributes not getting tracked when using MoEngage Android SDK 13.02.00 or above
-
BugFix
Cards 3.1.0
- Internal Improvements
Geofence 3.1.0
- Internal Improvements
- IOS
- MoEngageGeofence version updated to 5.16.0
Inbox 6.1.0
- Internal Improvements
18-06-2024
Core 7.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 8.0.0 onwards. |
- Android
- ANR while accessing the Plugin version from assets in the Main Thread
Inbox 6.0.1
- Android
- ANR while accessing the Plugin version from assets in the Main Thread
21-03-2024
Release of moengage-flutter version 7.0.0
7.0.0 compatible packages
com.moengage:moe-android-sdk:13.00.03
androidx.lifecycle:lifecycle-process:2.7.0
com.moengage:cards-core:2.0.2 //self handled cards
com.moengage:inapp:8.2.0
com.moengage:rich-notification:5.0.1
com.moengage:geofence:4.0.1
Core 7.0.0
- Added support for Non-Intrusive Nudge InApps.
- Removed support for MI Push
- Send SelfHandled InApp Callback when data is null
Breaking Change:
SelfHandledCampaignData will be of type nullable.
Then Now setSelfHandledInAppHandler((SelfHandledCampaignData data){ });
setSelfHandledInAppHandler((SelfHandledCampaignData? data){ });
- Android
- Native SDK Updated to support version 13.00.00 and above. Refer to the Release Notes for behavior changes.
- Add support for AGP 8.2.2 and above
- Note: Use minimum Native Inapp version 8.1.1. There is a known issue regarding in-app rendering in Flutter in InApp versions 8.0.0 & 8.1.0.
- IOS
- MoEngage-iOS-SDK version updated to 9.16.0 and above
- MoEngageInApp version updated to 4.15.0 and above
Inbox 6.0.0
- Updated Minimum Supported moengage_flutter version to 7.0.0
- Android
- Native SDK Updated to support version 13.00.00 and above
- Add support for AGP 8.2.2 and above
- Support for native inbox-core version 3.0.0 and above
- IOS
- MoEngageInbox version updated to 2.15.0
Geofence 3.0.0
- Updated Minimum Supported moengage_flutter version to 7.0.0
- Android
- Native SDK Updated to support version 13.00.00 and above
- Add support for AGP 8.2.2 and above
- Support for native geofence version 4.0.0 and above
- IOS
- MoEngageGeofence version updated to 5.15.0
Cards 3.0.0
- Updated Minimum Supported moengage_flutter version to 7.0.0
- Android
- Native SDK Updated to support version 13.00.00 and above
- Add support for AGP 8.2.2 and above
- Support for native cards-core version 2.0.0 and above
- IOS
- MoEngageGeofence version updated to 4.15.0
24-1-2024
Core 6.1.1
- Fix MoEngage undefined error handling if web SDK not integrated
- Web
- Fix MoEngage undefined error handling if web SDK not integrated
07-12-2023
Core 6.1.0
- Added support for array in User attributes
- Android
- Native SDK Updated to support version 12.10.01 and above
- Google Policy - Delete User details API
- Add support for Android Gradle Plugin 8.0.2 and above
- Upgrade Kotlin Version to 1.7.10
- Handled cases where native to dart callbacks were not working with background isolate created by FirebaseMessaging.onBackgroundMessage or any other background message handlers
- IOS
- MoEngage-iOS-SDK version updated to 9.14.0
- MoEngageInApp version updated to 4.13.0
Inbox 5.1.0
- Android
- Support for native inbox-core version 2.6.0 and above
- Add support for Android Gradle Plugin 8.0.2 and above
- Upgrade Kotlin Version to 1.7.10
- IOS
- MoEngageInbox version updated to 2.13.0
Geofence 2.1.0
- Android
- Support for native geofence version 3.4.0 and above
- Add support for Android Gradle Plugin 8.0.2 and above
- Upgrade Kotlin Version to 1.7.10
- IOS
- MoEngageGeofence version updated to 5.13.0
Cards 2.1.0
- Android
- Support for native cards-core version 1.6.0 and above
- Add support for Android Gradle Plugin 8.0.2 and above
- Upgrade Kotlin Version to 1.7.10
- Handled cases where native to dart callbacks were not working with background isolate created by FirebaseMessaging.onBackgroundMessage or any other background message handlers
- IOS
- MoEngageCards version updated to 4.13.0
13-09-2023
Core 6.0.0
- Federated Plugin Implementation
- Breaking Change: Use import 'package:moengage_flutter/moengage_flutter.dart'; to import any files in the moengage_flutter package. Remove the existing import related to moengage_flutter
- Android
- Native SDK Updated to support version 12.9.00 and above
Inbox 5.0.0
- Federated Plugin Implementation
- Breaking Change: Use import 'package:moengage_inbox/moengage_inbox.dart'; to import any files in the moengage_inbox package. Remove the existing import related to moengage_inbox
- Android
- Native SDK updated to support version 12.9.00 and above.
Geofence 2.0.0
- Federated Plugin Implementation
- Breaking Change: Use import 'package:moengage_geofence/moengage_goefence.dart'; to import any files in the moengage_geofence package. Remove the existing import related to moengage_geofence
Cards 2.0.0
- Federated Plugin Implementation
26-07-2023
Core 5.5.1
- Android
- Bugfix
-
Self Handled InApp delivery controls not working.
-
- Bugfix
Inbox 4.5.1
- iOS
- Bugfix
-
Fixed parsing issue in fetchAllMessages API.
-
- Bugfix
19-07-2023
Core 5.5.0
- Android
- Plugin Base Version Updated to
~>3.3.2
- Plugin Base Version Updated to
- iOS
-
MoEngage-iOS-SDK version updated to
~>9.10.0
-
Inbox 4.5.0
- iOS
-
MoEngageInbox SDK version updated to
~>2.8.0
.
-
Geofence 1.6.0
- iOS
-
MoEngageGeofence SDK version Updated to
~>5.10.0
-
Cards 1.0.0
- Initial Release - Support For Self-Handled Cards
31-05-2023
Core 5.4.0
- Android
- Compile SDK Version Updated to 33.
- Support For SelfHandled Push Notification Clicks In Foreground State.
- Support for Android SDK version 12.8.00 and above
- iOS
-
MoEngage-iOS-SDK version updated to 9.8.0.
-
Inbox 4.4.0
- Android
- Target & Compile SDK Version Updated to 33.
- iOS
-
MoEngageInbox SDK version updated to
~>2.8.0
.
-
Geofence 1.5.0
- Android
- Target & Compile SDK Version Updated to 33.
- iOS
-
MoEngageInbox SDK version updated to
~>5.8.0
.
-
16-05-2023
Core 5.3.1
- Android
- Bugfix
- Self-handled callback not working for test InApp and event-triggered InApp.
- Bugfix
21-02-2023
Geofence 1.4.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.
-
08-02-2023
Core 5.3.0
- Security improvement: Controlled logging
- Android
- Support for Android 13 push notification Opt-in with rationale via In-Apps.
- Device Id enable/disable support
- iOS
- MoEngage-iOS-SDK version updated to ~>9.4.0
Inbox 4.3.0
- Security improvement: Controlled logging
- iOS
- MoEngageInbox SDK version updated to ~>2.4.0
Geofence 1.3.0
- Security improvement: Controlled logging
- iOS
- MoEngageInbox SDK version updated to ~>5.4.0
Core 5.2.0
- iOS
-
MoEngage-iOS-SDK version updated to 9.2.0
- Updated APIs
Then Now public func initializeDefaultInstance(config: MOSDKConfig, sdkState: MoEngageSDKState = .enabled, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil)
public func initializeDefaultInstance(config: MoEngageSDKConfig, sdkState: MoEngageSDKState = .enabled, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil)
public func initializeDefaultInstance(_ config: MOSDKConfig, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil)
public func initializeDefaultInstance(_ config: MoEngageSDKConfig, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil)
-
Inbox 4.2.0
- iOS
-
MoEngageInbox SDK version updated to 2.2.0.
-
Geofence 1.2.0
- iOS
-
MoEngageGeofence SDK version updated to 5.2.0.
-
04-11-2022
Core 5.1.1
- Bugfix
- Typo fixed in enableAdIdTracking()
27-10-2022
Core 5.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)
- Initialization APIs are updated to initialize SDK with the state.
Inbox 4.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
- Android Gradle Plugin version updated to
Geofence 1.1.0
- iOS
- MoEngageGeofence SDK version updated to
~>4.4.0
.
- MoEngageGeofence SDK version updated to
27-09-2022
Core 5.0.0
-
- Support for Android SDK version 12.2.05 and above.
- Support for iOS SDK version 8.3.1 and above.
- Breaking Changes in Dart
-
Then Now MoEngageFlutter() MoEngageFlutter("YOUR_APP_ID") optOutDataTracking(false) enableDataTracking() optOutDataTracking(true) disableDataTracking() - InApp Model InAppCampaign broken down from a single object to multiple objects
- InAppData
- ClickData
- SelfHandledCampaignData
- InApp setUpInAppCallbacks removed and callbacks are broken down into multiple listeners.
Callback Type Method InApp Shown setInAppShownCallbackHandler(InAppShownCallbackHandler) InApp Dismissed setInAppDismissedCallbackHandler(InAppDismissedCallbackHandler) InApp Clicked(Navigation, Custom Action) setInAppClickHandler(InAppClickCallbackHandler) InApp Self Handled setSelfHandledInAppHandler(SelfHandledInAppCallbackHandler)
- The push campaign Model is restructured and renamed from PushCampaign to PushCampaignData.
- Push callback APIs are renamed.
Then Now setUpPushCallbacks
(PushCallbackHandler)
setPushClickCallbackHandler(PushClickCallbackHandler)
setUpPushTokenCallback
(PushTokenCallbackHandler)
setPushTokenCallbackHandler(PushTokenCallbackHandler)
- Removed APIs
Removed APIs selfHandledPrimaryClicked() enableSDKLogs() optOutInAppNotification() optOutPushNotification() startGeofenceMonitoring()
-
- 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.
- Removed and replaced APIs
Then Now MoEInitializer.initialize(Context, MoEngage.Builder) MoEInitializer.initialiseDefaultInstance(Context, MoEngage.Builder) MoEInitializer.initialize(Context, MoEngage.Builder, Boolean) MoEInitializer.initialiseDefaultInstance(Context, MoEngage.Builder, SdkState)
- Build Configuration Updates
- iOS
- MOFlutterInitializer has been renamed to MoEngageInitialize
- Removed and replaced APIs
Then Now initializeWithSDKConfig(_ config: MOSDKConfig, andLaunchOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) initializeDefaultInstance(_ config: MOSDKConfig, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil) initializeWithSDKConfig(_ config: MOSDKConfig, withSDKState state:Bool, andLaunchOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) initializeDefaultInstance(_ config: MOSDKConfig, sdkState: Bool = true, launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil)
Inbox 4.0.0
-
- Support for Android SDK version 12.2.05 and above and Native Inbox SDK Version 2.1.1 and above.
- Support for iOS SDK version 8.3.1 and above Native Inbox SDK Version 1.3.0 and above.
- Breaking changes
Then Now MoEngageInbox() MoEngageInbox("YOUR_APP_ID")
- Android
- Build Configuration Updates
- Minimum SDK version - 21
- Target SDK version - 30
- Compile SDK Version - 30
- Build Configuration Updates
Geofence 1.0.0
-
- iOS
- Initial Release with MoEngageGeofence SDK version `~>4.3.0`.
- iOS
Core v4.2.0
Release Date: 29th July 2022
-
- Support for Flutter 3
-
Device identifier tracking update as per Google's User Data policy. Advertising Id is only tracked after user consent.
- Android
- Native SDK updated to support version
11.6.02
and above.
- Native SDK updated to support version
Inbox v3.2.0
Release Date: 29th July 2022
-
- Support for Flutter 3
Core v4.1.0
Release Date: 6th September 2021
-
- Support for HTML InApps
- Android
- Native SDK updated to support version
11.4.00
and above.
- Native SDK updated to support version
- iOS
- Native Dependencies updated to support MoEngage-iOS-SDK
7.1.0
and above
- Native Dependencies updated to support MoEngage-iOS-SDK
Inbox v3.1.0
Release Date: 6th September 2021
-
- Android
- Native SDK updated to support version
11.4.00
and above.
- Native SDK updated to support version
- Android
Core v4.0.2
Release Date: 21st August 2021
- Bugfix
- Calling SDK APIs when the application is in the background throws an error on Android.
Core v4.0.1
Release Date: 15th June 2021
- Fixes: Push click callback failing due to parsing error.
Core v4.0.0
Release Date: 12th May 2021
- Migrated the library to null safety.
- Require Dart 2.12 or greater.
- Bumped flutter dependency constraint to min version
1.17.0
- Android
- Native SDK updated to support version
11.2.00
and above.
- Native SDK updated to support version
Inbox v3.0.0
Release Date: 12th May 2021
- Migrated the library to null safety.
- Require Dart 2.12 or greater.
- Android
- Native SDK updated to support version
11.2.00
and above. - Migrated Native Inbox artifact from
addon-inbox
toinbox-core
.
- Native SDK updated to support version
Core v3.0.1
Release Date: 28th April 2021
- iOS
- Added ObjC support for
MOFlutterInitializer
class - PodSpec changes to set deployment target to iOS 10.0.
- Added ObjC support for
Inbox v2.0.0
Release Date: 26th February 2021
- Native Dependencies updated to support MoEngage-iOS-SDK
7.*
and above - Native SDK updated to support version
6.0.2
and above. Refer to the Release Notes for behavior changes. - Native Inbox SDK updated to support version
6.0.2
and above.
Core v3.0.0
Release Date: 26th February 2021
- Android Native SDK updated to support version
11.0.04
and above. Refer to the Release Notes for behavior changes. - Plugin now supports iOS 10.0 and above.
- iOS Native Dependencies updated to support MoEngage-iOS-SDK
7.*
and above - Added Dart APIs to enable and disable MoEngage SDK.
- Added Dart API to register a callback for push token-generated event.
Core v2.0.2
Release Date: 15th November 2021
- Android dependencies updated to use versions published on Maven Central.
Inbox v1.0.2
Release Date: 15th November 2021
- Android dependencies updated to use versions published on Maven Central.
Web v0.0.1
Release Date: 30th December 2020
- Support for Moengage Web SDK for Flutter.
v3.0.0-beta.1
Release Date: 30th December 2020
- Support for Moengage Web SDK for Flutter.
v Core v2.0.2
Release Date: 7th December 2020
- Support for extending Native Android Callbacks if required.
- Native Android SDK version required is
10.5.00
or above
Inbox v.1.0.0, v1.0.1
Release Date: 6th November 2020
- Initial release
- APIs
- Fetch All Messages
- Get unclicked count
- Track message clicked
- Delete message
Core v2.0.1
Release Date: 6th November 2020
- Fixes: Set AppStatus method was getting called internally with other plugin channel methods.
Core v2.0.0
Release Date: 23rd October 2020
- Support for In-App V3
- Support for Self-Handled In-App
- Support for Push Templates
- Support for Huawei Push Kit
- Android SDK updated to support
10.4.03
and above. - iOS SDK dependency changed to support versions greater than
6.0.0
. - Deprecated APIs
Then Now MoEProperties().addInteger(String, int) MoEProperties().addAttribute.(String, dynamic) MoEProperties().addString(String, String) MoEProperties().addAttribute(String, dynamic) MoEProperties().addBoolean(String, bool) MoEProperties().addAttribute(String, dynamic) MoEProperties().addDouble(String, double) MoEProperties().addAttribute(String, dynamic) MoEProperties().addLocation(String, MoEGeoLocation) MoEProperties().addAttribute(String, dynamic) - Removed APIs
Then Now onPushClick(Map<String, dynamic>) onPushClick(PushCampaign) onInAppClick(Map<String, dynamic>) onInAppClick(InAppCampaign) onInAppShown(Map<String, dynamic>) onInAppShown(InAppCampaign) passPushToken(String) passFCMPushToken(String) passPushPayload(Map<String, String>) passFCMPushPayload(Map<String, String>) - Removed APIs Android
Then Now MoEInitializer.initialize(MoEngage) MoEInitializer.initialize(Context, MoEngage.Builder)
Core v1.1.0
Release Date: 10th February 2020
- Add Dart APIs for passing FCM Push Token and FCM Push Payload from the Android Platform.
Core v1.0.1
Release Date: 17th December 2019
- Sample Updated
- ReadMe Updated
- Improved logging
Core v1.0.0
Release Date: 16th December 2019
- Initial Release