> ## Documentation Index
> Fetch the complete documentation index at: https://moengage-sdk-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Changelog
* You can now get notified whenever MoEngage releases a new version of the Unity SDK. For more information, refer to [Subscribe to MoEngage SDK Releases](developer-guide/release-notes/subscribe-to-mo-engage-sdk-releases/subscribe-to-mo-engage-sdk-releases).
* For privacy manifest support on iOS, please make sure that you are on Unity SDK Version 3.2.0 or above and iOS SDK Version 9.17.0 or above. Want to know more about privacy manifest? Refer this [link](https://help.moengage.com/hc/en-us/articles/23893067070996-Apple-Privacy-Manifest-Update).
# 09-09-2025
## Core 5.0.0
* Added support for Unity 6.1
# 07-08-2024
## Core 4.0.0
* iOS
* Added support for tracking custom boolean attributes in two formats: ***0/1*** and ***TRUE/FALSE*** Refer to the [documentation](/developer-guide/react-native-sdk/data-tracking/Tracking-User-Attributes#Custom-Boolean-User-Attribute) for more information.
**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](/developer-guide/react-native-sdk/data-tracking/Tracking-User-Attributes#Custom-Boolean-User-Attribute) in our developer documentation.
* Updated MoEngage-iOS-SDK to dependency to ***9.18.1 .***
* Added DC-06 support
## Geofence 2.0.0
* iOS
* Updated the MoEngageGeofence dependency to ***5.17.1*** .
# 26-04-2024
## Core 3.2.0
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 4.0.0 onwards.
* Internal improvements.
* iOS
* Updated the MoEngage-iOS-SDK dependency to **9.17.0** and above. Refer [here](/developer-guide/release-notes/ios-sdk/2024#26-04-2024) for more information.
## Geofence 1.2.0
* iOS
* Updated the MoEngageGeofence dependency to **5.16.0** and above.
# 20-12-2023
## Core 3.1.0
* Android
* Support for SDK version **12.10.02**and above.
* Google Policy Compliance: API to **DeleteUser()** to delete User details.
* iOS
* Updated the MoEngage-iOS-SDK dependency to `9.14.0` and above.
## Geofence 1.1.0
* Android
* Support for native Geofence SDK version **3.4.0** and above.
* iOS
* Updated the MoEngageGeofence dependency to **5.13.0** and above.
# 11-09-2023
* Android
* Bugfix
* New [release assets](https://github.com/moengage/MoEngage-Unity-SDK/releases/tag/rich-notification-v4.5.1) with RichNotification native SDK version update to `4.5.1`.
# 3.0.0 (17-08-2023)
* Support for Android SDK version **12.8.02**.
* Support for iOS SDK version **9.10.0**.
* The MoEngage unity package requires the application to use Unity Version 2023.1.7f1. Version 2023.1.7f1 is required for the target SDK and Gradle version compatibility.
* Breaking Changes
| Then | Now |
| ------------------------- | --------------------- |
| InvalidateInAppContexts() | ResetInAppContexts() |
| OptOutDataTracking(true) | EnableDataTracking() |
| OptOutDataTracking(false) | DisableDataTracking() |
* Removed API
* EnableSDKLogs()
* OptOutPushTracking()
* OptOutInAppTracking()
* SelfHandledPrimaryClicked()
* StartGeofenceMonitoring()
* Android
* Support for Android 13 notification permission.
* Android Gradle Plugin version updated to 7.3.1
* Gradle version updated to 7.4
* Build Configuration Updates
* Compile SDK Version 33
* Target SDK version 33
* Support for Android SDK version **12.8.02**
* InApp **6.7.2**
* Removed and Updated APIs
| Then | Now |
| --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| initialize(Context context, MoEngage.Builder builder) | initialiseDefaultInstance(Context context, MoEngage.Builder builder) |
| initialize(Context context, MoEngage.Builder builder, boolean isSdkEnabled) | initialiseDefaultInstance(Context context, MoEngage.Builder builder, SdkState sdkState) |
* iOS
* Removed and Updated APIs
| Then | Now |
| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| - (void)intializeSDKWithLaunchOptions:(NSDictionary\**)launchOptions andSDKState:(BOOL)isSDKEnabled;* | - (void)initializeSDKWithLaunchOptions:(NSDictionary\*)launchOptions withSDKState:(MoEngageSDKState)sdkState; |
# Geofence 1.0.0(17-08-2023)
* Support for Android Geofence SDK version **3.3.0**
* Support for iOS MoEngageGeofence SDK version **5.10.0** and above.
* Added support for ***StopGeofenceMonitoring*** API.
* iOS
* Removed and Updated APIs
| Then | Now |
| ----------------------------------------- | ------------------------------------------------- |
| MoEngageClient.StartGeofenceMonitoring(); | MoEngageGeofenceClient.StartGeofenceMonitoring(); |
# 2.3.0(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`.
# 2.2.0(02-09-2021)
* Android
* Native SDK updated to support `11.4.00` and above. Refer to [Release Notes](/developer-guide/release-notes/ios-sdk/2023-and-older#11-4-00-31-08-2021--0-5) for more details.
* iOS
* Native dependencies updated to support `MoEngage-iOS-SDK` version `7.1.0` and above.
# 2.1.0 (11-05-2021)
* Android SDK updated to `11.2.00`
# 2.0.0 (01-03-2021)
* iOS
* Dropped support for iOS 9.\*, plugin now supports iOS version `10.0` and above.
* Native dependencies updated to support `MoEngage-iOS-SDK` version `7.0.0` and above.
* Android
* Android Native SDK updated to support version `11.0.04`.
* Removed APIs
| Then | Now |
| ---------------------------------------------- | ------------------------------------------------- |
| MoEngageClient#Pass PushPayload(IDictionary) | MoEngageClient#PassFcm PushPayload(IDictionary) |
| MoEngageClient#PassPushToken(string) | MoEngageClient#PassFcmPushToken(string) |
# 1.3.1 (16-02-2021)
* Android artifacts use maven central instead of Jcenter.
# 1.3.0 (11-01-2021)
* iOS: UnityAppController Swizzling implementation added since UnityAppController subclass Implementation was not working in case of multiple subclasses.
# 1.2.1 (29-12-2020)
* iOS: Weak linked AppTrackingTransparency framework.
# 1.2.0 (18-12-2020)
* Disable/Enable Methods added to block/unblock the SDK features.
* Push Token Callback added
# 1.1.1 (23-10-2020)
* Bugfix: Events were not marked as non-interactive in iOS in `version 1.1.0`.
# 1.1.0 (30-09-2020)
* Added support for Push Templates
* Provided GDPR OptOut APIs
* iOS Native SDK Dependency set to MoEPluginBase 1.0.0
* Android SDK moved to `androidx` namespace
# 1.0.1 (07-07-2020)
* Android SDK Version update
# 1.0.0 (05-07-2020)
* Initial Release