Skip to main content
We have made quite a few changes in SDK version 6.0.0 and if you are someone who was using an older version of our SDK and planning to move to version 6.0.0 or above here are the changes to be made while migrating:

iOS 8.* Support Removed

From SDK version 6.0.0 we have set the deployment target as iOS 9.0 and hence have removed support for iOS 8.*. We have decided to do this since the user base in iOS 8.0 is very less and most of the developers are already setting their app’s deployment target to greater than iOS 9.0.

Initialization Method Deprecation

We have deprecated the previous initialization methods and have introduced new methods. This is to simplify initialization by reducing the number of arguments in the method: Deprecated methods
New methods
For more info on SDK Initialization, refer to the following doc.

Analytics Module Changes

Track Event:

We have Introduced MOProperties class to track all the event attributes. And hence we have deprecated the earlier methods and included trackEvent:withProperties: to track events. Refer to this link for more info. Deprecated Methods
New methods

User Attribute Tracking:

We have added a couple of additional methods to track date user attributes in the SDK, more info in this doc :

Messaging Module Changes

Notification Received Method Deprecation:

AppDelegate Swizzling :From SDK version 5.0.0, we have implemented Swizzling of AppDelegate inside the SDK, due to which SDK, by default, gets all the callbacks related to Notifications. Therefore, if AppDelegate Swizzling is enabled, then developers can skip calling the SDK methods on Notification Callbacks. For more info on the same, refer to the following link.
We have deprecated didReceieveNotificationinApplication:withInfo:openDeeplinkUrlAutomatically: instead, use didReceieveNotificationinApplication:withInfo:. Deprecated method
New methods

InApp Module Changes

  • The InApp module has been completely revamped and includes a lot of changes, the primary one being we have separated the module from the MoEngage-iOS-SDK. Therefore, now to use In-Apps in your app you will have to integrate MoEngageInApp module to your project. Refer to this link for integrating the inApp Module.
  • We have removed support for InApps in Landscape Orientation and iPads as the existing templates that we have are not made considering them, and therefore may end up breaking in the said scenarios.
  • We have added support for Context-based InApps wherein we can tag InApps and show InApps based on the current context set on the SDK. Refer to this link for more info.
  • We have removed support for most of the older methods and replaced them with new ones to have it consistent across platforms. To know the differences in the API to be used refer below links:
  • InApp APIs for SDK version 6.0.0 and above
  • InApp APIs for SDK version 5.2.6 and below