Changelog
info

Information

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

03-05-2024

Core 4.0.0

  • Capacitor 6 support
  • Send SelfHandled InApp Callback when data is null
  • Android
    •  Support for catalog version 4.1.4. Refer to release notes.
    • Removed Support for PushAmpPlus due to MI Push service shutdown.
  • iOS
    • Support for iOS SDK version 9.17.0 and above. Refer to release notes for more details.

Geofence 3.3.0

  • Capacitor 6 support
  • Android
  • iOS
    • MoEngageGeofence SDK dependency updated to 5.16.0 and above. Refer to release notes for more details

 

08-04-2024

Core 3.3.0

  • iOS
    • Support for iOS SDK version 9.16.1 and above. Refer to release notes for more details.

Geofence 3.3.0

  • iOS
    • MoEngageGeofence SDK dependency updated to 5.15.0 and above.Refer to release notes for more details

30-01-2024

Core 3.2.0

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

Geofence 3.2.0

  • iOS
    • MoEngageGeofence SDK version updated to 5.14.0.

29-11-2023

Core 3.1.0

  • Android 
    • Support for android-dependency-catalog version 3.2.1, 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

Geofence 3.1.0

  • Android 
    • Support for android-dependency-catalog version 3.2.1, refer to the release notes for more details.
  • iOS
    • MoEngageGeofence SDK version updated to 5.12.0.

11-09-2023

Core 3.0.0

  • Migrated from Capacitor 4 to Capacitor 5
  • Android
    • Updated Target SDK version & Compile SDK version to 33
  • iOS
    • MoEngageGeofence dependency updated to 9.11.0.

Geofence 3.0.0

  • Migrated from Capacitor 4 to Capacitor 5
  • Android
    • Updated Target SDK version & Compile SDK version to 33
  • iOS
    • MoEngageGeofence dependency updated to 5.11.0.

16-05-2023

Core 2.2.1

  • Android
    • Bugfix
      • Self-handled callback not working for test InApp and event-triggered InApp.

Core v2.2.0 (28-02-2023)

  • Android 
    • Support for Android 13 push notification Opt-in with rationale via In-Apps.
    • Device Id enable/disable support

Geofence v2.2.0 (28-02-2023)

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

Core v2.1.0 (15-02-2023)

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

Geofence v2.1.0 (15-02-2023)

  • iOS
    • MoEngageGeofence dependency updated to 5.4.0

Core v2.0.0 (09-01-2023)

  • Support for Android SDK version 12.5.04 and above.

  • Support for iOS SDK version 9.2.0 and above.
  • Breaking Changes 
    • All exposed API will have appId as an additional trailing parameter.

    • Following are the renamed API
      Then Now

      optOutDataTracking({ shouldOptOut: true })) 

      enableDataTracking(options: { appId: string }): Promise<void>;   

      optOutDataTracking({ shouldOptOut: false })  |  

      disableDataTracking(options: { appId: string }): Promise<void>;  
    • The push token Model is renamed from MoEPushToken to MoEPushTokenData
    • Removed APIs
      Removed APIs
      selfHandledPrimaryClicked(campaignData: MoEInAppSelfHandledCampaignData): Promise<void>;
      enableSDKLogs(): Promise<void>;
      optOutInAppNotification(options: { shouldOptOut: boolean }): Promise<void>;
      optOutPushNotification(options: { shouldOptOut: boolean }): Promise<void>;
  • Android
    • Support for Android 13 notification permission
    • Support for Android Gradle Plugin version 7.3.1
    • Build Configuration Updates
      • Target SDK version - 31
      • Compile SDK Version - 31
    • Removed and replaced APIs
      Then Now
      MoEInitializer.initialize(context: Context, builder: MoEngage.Builder)
      MoEInitializer.initialiseDefaultInstance(context: Context, builder: MoEngage.Builder)
      MoEInitializer.initialize(context: Context, builder: MoEngage.Builder, isSdkEnabled: Boolean)
      MoEInitializer.initialiseDefaultInstance(context: Context, builder: MoEngage.Builder, sdkState: SdkState)
  • iOS
    • Removed and replaced APIs
      Then Now
      initializeWithSDKConfig(_ config: MOSDKConfig, andLaunchOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?)
      initializeDefaultInstance(_ config: MoEngageSDKConfig, andLaunchOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?)
      initializeWithSDKConfig(_ config: MOSDKConfig, withSDKState state:Bool, andLaunchOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?)
      initializeDefaultInstance(_ config: MoEngageSDKConfig, withSDKState state:MoEngageSDKState, andLaunchOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?)

Geofence v2.0.0 (09-01-2023)

  • Updated the dependency to MoEngageGeofence 5.2.0 and above

  • All exposed API will have appId as an additional trailing parameter

Core v1.1.1 (23-12-2022)

  • Bugfix
    • Peer dependency resolution error fix.

Geofence v1.1.1 (23-12-2022)

    • Bugfix
      • Peer dependency resolution error fix.

Core v1.1.0 (20-12-2022)

  • Migrated to Capacitor 4.

Geofence v1.1.0 (20-12-2022)

  • Migrated to Capacitor 4.

Core v1.0.3 (27-09-2022)

  • iOS
    • BugFix: Registered  logoutUser method to make it available for Javascript.

Core v1.0.2 (25-07-2022)

  • Android
    • 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.
  • iOS
    • Native dependencies updated to support MoEngage-iOS-SDK version 7.2.0.

Core v1.0.1 (09-02-2022)

  • Bugfix
    • Android Push click callback is not working when a notification is clicked in the app's killed state.

Core v1.0.0 (01-02-2022)

  • Initial Release

Geofence v1.0.0 (01-02-2022)

  • Initial Release

Previous

Next

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

How can we improve this article?