--- schema_version: "1" id: 5ffa35cb8a11f9a8896260ff23ebcee5235d44ce87ba8c1ad10b02a4f9ca3adc title: Change Log collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud-mobilepush/engagement_sdk/guides/mc_engagement/mc_engagement_changelog.md canonical_url: https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_changelog.html source_site: developer.salesforce.com content_type: documentation content_hash: 5b80e30bf2a14e29e46e76b1e9e2a765f2abd9bab2ab96bbfe1bad6a0d734949 products: - Salesforce Engagement SDK --- # Change Log This changelog contains information about these Engagement SDK products: - [SDK for Android](#android) - [SDK for iOS](#ios) - [Cordova Plugin](#cordova) - [Flutter Plugin](#flutter) - [React Plugin](#react) Change history for previous major releases of each product is combined in a collapsible section. For example, to view the history for version 9 of the Android SDK, click **Version 9 Releases** in the SDK for Android section to expand the list of changes. ## Android This section contains information about releases of the MobilePush SDK for Android, including version numbers, release dates, compatibility details, and key changes. ### Latest Release - Version 11.0.1 _Released June 10, 2026_ Version 11.0.1 of the Android SDK has been tested with Firebase Cloud Messaging version 25.0.1, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 26. The SDK is compiled with Android API version 36 and depends on Java version 17 and Kotlin version 2.2.21. - Performance improvements and bug fixes. - Hardening against an ART verifier exception (VerifyError) that could crash apps running JaCoCo-instrumented builds. See [Google Issue Tracker](https://issuetracker.google.com/issues/247932119) and [Jacoco Issue](https://github.com/jacoco/jacoco/issues/1381). ### Version 11.0.0 _Released March 30, 2026_ Version 11.0.0 of the Android SDK has been tested with Firebase Cloud Messaging version 25.0.1, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 26. The SDK is compiled with Android API version 36 and depends on Java version 17 and Kotlin version 2.2.21. Version 11.0.0 of the SDK is a major release that introduces changes to the In-App Messaging configuration and how the `InAppMessageManager` is accessed, minor changes to Push configuration consolidating `UrlHandlers`. This release also includes performance improvements and bug fixes. For information about migrating Android apps to version 11 of the SDK, see [Migrate to Version 11](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_upgrade/mc_engagement_upgrade_android_v11.md).
Version 10 Releases ### Version 10.0.0 _Released November 6, 2025_ Version 10.0.0 of the Android SDK has been tested with Firebase Cloud Messaging version 24.0.2, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 26. The SDK is compiled with Android API version 36 and depends on Java version 17 and Kotlin version 1.9.22. Version 10.0.0 of the SDK is a major release that introduces a new unified SDK architecture. For information about migrating Android apps to version 10 of the SDK, see [Migrate to the SDK for Android Version 10](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_upgrade/mc_engagement_upgrade_android_v10.md).
Version 9 Releases ### Version 9.0.5 _Released April 22, 2026_ Version 9.0.5 of the Android SDK has been tested with Firebase Cloud Messaging version 24.0.2, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 23. Compiled with Android API version 36. The SDK depends on Java version 17. - Fix for bundle size issue with DeviceStatistics. ### Version 9.0.4 _Released December 18, 2025_ Version 9.0.4 of the Android SDK has been tested with Firebase Cloud Messaging version 24.0.2, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 23. Compiled with Android API version 36. The SDK depends on Java version 17. - Improved UI for the push notification carousel navigation buttons. - Fix for SDK crash issues due to uncaught exceptions from Broadcast receiver on devices running Android versions 11 and 12. ### Version 9.0.3 _Released August 5, 2025_ Version 9.0.3 of the Android SDK has been tested with Firebase Cloud Messaging version 24.0.2, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 23. Compiled with Android API version 36. The SDK depends on Java version 17. - Resolved the issue of not showing more than 2 lines of message text in standard push notifications with no media. - Bug fixes and performance improvements. ### Version 9.0.2 _Released June 26, 2025_ Version 9.0.2 of the Android SDK has been tested with Firebase Cloud Messaging version 24.0.2, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 23. Compiled with Android API version 36. The SDK depends on Java version 17. - Android 16 Support - Bug fixes and performance improvements. ### Version 9.0.1 _Released May 27, 2025_ Version 9.0.1 of the Android SDK has been tested with Firebase Cloud Messaging version 24.0.2, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 23. Compiled with Android API version 35. The SDK depends on Java version 17. - Resolved `ANR` issues on app start. - Resolved `NPE` during device statistics sending. - Resolved known keys issue in `NotificationMessage` customKeys. - Bug fixes and performance improvements. ### Version 9.0.0 _Released March 14, 2025, correlating with the Marketing Cloud Engagement March 2025 release._ Version 9.0.0 of the Android SDK has been tested with Firebase Cloud Messaging version 24.0.2, Google Play Location Services version 21.3.0, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 21. Compiled with Android API version 35. The SDK depends on Java version 17. - Push notifications – Send interactive carousel push notifications to your app users. Customize buttons, small icons, large icons, and sound. - Push Delivery event – Get a delivered ENS event when a push message successfully reaches a user’s device. - Inbox 2.0 Support – Send enhanced inbox messages with additional fields like subtitles and messages, plus new CTA options (App/Web URL, None) beyond only CloudPage. - Bug fixes and performance improvements.
Version 8 Releases ### Version 8.2.2 _Released February 27, 2025_ Version 8.2.2 of the Android SDK has been tested with Firebase Cloud Messaging version 23.2.1, Google Play Location Services version 21.0.1, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 21. Compiled with Android API version 35. The SDK depends on Java version 17. - Resolved an issue with HTTP header transmission to ensure reliable delivery of engagement events from the SDK - Addressed a `NullPointerException` that occurred when the Android Bundle system returned unexpected `null` values - Optimized the batch size for event and analytics API calls to enhance performance. ### Version 8.2.1 _Released November 11, 2024, correlating with the Marketing Cloud Engagement November 2024 release._ Version 8.2.1 of the Android SDK has been tested with Firebase Cloud Messaging version 23.2.1, Google Play Location Services version 21.0.1, and AltBeacon Library version 2.20.7. The minimum compatible Android API version is 21. Compiled with Android API version 35. The SDK depends on Java version 17. - Android 15 support - Fix for `null` attribute applied through SFMCSdk Identity causing ClassCastException - This release includes bug fixes and SDK improvements ### Version 8.2.0 _Released July 30, 2024, correlating with the Marketing Cloud Engagement July 2024 release._ Version 8.2.0 of the Android SDK has been tested with Firebase Cloud Messaging version 23.2.1, Google Play Location Services version 21.0.1, and AltBeacon Library version 2.20. The minimum compatible Android API version is 21. Compiled with Android API version 34. The SDK depends on Java version 17. - The SDK now automatically switches its encryption method to use the Android Keystore. - Moved MD5 hashing to a new, isolated library for optional use, with an added option to forcibly remove MD5 in `MarketingCloudConfig`. - Removed the deprecated Android `LocalBroadcastManager` dependency. - Bug fixes and performance improvements. ### Version 8.1.5 _Released February 27, 2024, correlating with the Marketing Cloud Engagement February 2024 release._ Version 8.1.5 of the Android SDK has been tested with Google Play Services version 21.0.1 and AltBeacon Library version 2.20. The minimum compatible Android API version is 21. Compiled with Android API version 34. - Fix for `NoClassDefFoundError` – Resolved an issue where the SDK crashes while reconfiguring a running SDK if the location dependency is not present. - Bug fixes and performance improvements. ### Version 8.1.4 _Released January 30, 2024, correlating with the Marketing Cloud Engagement January 2024 release._ Version 8.1.4 of the Android SDK has been tested with Google Play Services version 21.0.1 and AltBeacon Library version 2.20. The minimum compatible Android API version is 21. Compiled with Android API version 34. - Fix for Receiver Not Registered – Android 14’s notification trampolining fix resulted in a rare occurence of an issue unregistering a local receiver. ### Version 8.1.3 _Released November 9, 2023, correlating with the Marketing Cloud Engagement October 2023 release._ Version 8.1.3 of the MobilePush Android SDK has been tested with Google Play Services version 21.0.1 and AltBeacon Library version 2.20-beta1. The minimum compatible Android API version is 21. Compiled with Android API version 34. - Fix for Proguard obfuscating classes without package name ### Version 8.1.2 _Released October 19, 2023, correlating with the Marketing Cloud Engagement October 2023 release._ Version 8.1.2 of the MobilePush Android SDK has been tested with Google Play Services version 21.0.1 and AltBeacon Library version 2.20-beta1. The minimum compatible Android API version is 21. Compiled with Android API version 34. - Fix for NPE when parsing URI scheme ### Version 8.1.1 _Released October 10, 2023, correlating with the Marketing Cloud Engagement October 2023 release._ Version 8.1.1 of the MobilePush Android SDK has been tested with Google Play Services version 21.0.1 and AltBeacon Library version 2.20-beta1. The minimum compatible Android API version is 21. Compiled with Android API version 34. - Fix for missing `requestId` property in `NotificationMessage` ### Version 8.1.0 _Released October 9, 2023, correlating with the Marketing Cloud Engagement October 2023 release._ Version 8.1.0 of the Android SDK has been tested with Google Play Services version 21.0.1 and AltBeacon Library version 2.20-beta1. The minimum compatible Android API version is 21. Compiled with Android API version 34. - Android 14 support - Resolved NPE in `DevStats` - Resolved in-app message delay not being honored - Introduced Runtime Toggles for Analytics, Inbox, Geofence Messaging, and Proximity Messaging ### Version 8.0.9 _Released May 9, 2023, correlating with the Marketing Cloud Engagement May 2023 release._ Version 8.0.9 of the Android SDK has been tested with Google Play Services version 21.0.1 and AltBeacon Library version 2.19.3. The minimum compatible Android API version is 21. Compiled with Android API version 33. - Bug fixes and performance improvements - Play Services Location – Added support for Play Services Location versions 21 and newer - Firebase Messaging – Added support for Firebase Messaging versions 23 and newer - Better Foreground and Background Detection – Replaced Google’s annotation-based detection of application foreground and background - Resolved `JSONObject` Verifier Error – A fix for the `onInit` crash has been implemented. For more information, see the [Google Issue Tracker](https://issuetracker.google.com/issues/37012699#comment13). ### Version 8.0.8 _Released January 5, 2022, correlating with the Marketing Cloud Engagement October 2022 release._ Version 8.0.8 of the Android SDK has been tested with Google Play Services version 19.0.1 and AltBeacon Library version 2.19.3. The minimum compatible Android API version is 21. Compiled with Android API version 33. - `requestId` fix for analytics reporting issues - Bug fixes and performance improvements ### Version 8.0.7 _Released September 29, 2022, correlating with the Marketing Cloud Engagement October 2022 release._ Version 8.0.7 of the Android SDK has been tested with Google Play Services version 19.0.1 and AltBeacon Library version 2.19.3. The minimum compatible Android API version is 21. Compiled with Android API version 33. - Support for Android 13 - Support for ENS - Support for latest Firebase Messaging - Support for latest Beacon Messaging - Added `redirectForAnalytics` support for `RemoteNotification` - Bug fixes and performance improvements ### Version 8.0.6 _Released May 4, 2022, correlating with the Marketing Cloud Engagement May 2022 release._ Version 8.0.6 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Bug fixes and performance improvements ### Version 8.0.5 _Released March 22, 2022, correlating with the Marketing Cloud Engagement March 2022 release._ Version 8.0.5 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Bug fixes and performance improvements ### Version 8.0.4 _Released November 22, 2021, correlating with the Marketing Cloud Engagement October 2021 release._ Version 8.0.4 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Bug fixes and performance improvements ### Version 8.0.3 _Released November 12, 2021, correlating with the Marketing Cloud Engagement October 2021 release._ Version 8.0.3 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Bug fixes and performance improvements ### Version 8.0.2 _Released November 2, 2021, correlating with the Marketing Cloud Engagement October 2021 release._ Version 8.0.2 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Bug fixes and performance improvements ### Version 8.0.1 _Released October 11, 2021, correlating with the Marketing Cloud Engagement October 2021 release._ Version 8.0.1 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Bug fixes and performance improvements - Support for Android 12 - Support for latest Firebase Messaging - Support for latest Beacon Messaging ### Version 8.0.0 _Released October 4, 2021, correlating with the Marketing Cloud Engagement October 2021 release._ Version 8.0.0 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. **important:** This version is deprecated. Use version 8.0.1 or newer.
Version 7 Releases ### Version 7.4.4 _Released December 12, 2021, correlating with the Marketing Cloud Engagement June 2021 release._ Version 7.4.4 of the Android SDK has been tested with Google Play Services version 22.0.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Backport of version 8’s `RejectedExecutionException` Fix ### Version 7.4.3 _Released September 3, 2021, correlating with the Marketing Cloud Engagement June 2021 release._ Version 7.4.3 of the Android SDK has been tested with Google Play Services version 22.0.0 and AltBeacon Library version 2.19. The minimum compatible Android API version is 21. Compiled with Android API version 31. - Android 12 Support - Backported Android 12 support from the 8.x version of the SDK ### Version 7.4.2 _Released September 2, 2021, correlating with the Marketing Cloud Engagement June 2021 release._ Version 7.4.2 of the Android SDK has been tested with Google Play Services version 20.3.0 and AltBeacon Library version 2.17.1. The minimum compatible Android API version is 21. Compiled with Android API version 29. - Bug fixes and performance improvements ### Version 7.4.1 _Released June 11, 2021, correlating with the Marketing Cloud Engagement June 2021 release._ Version 7.4.1 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.17.1. The minimum compatible Android API version is 21. Compiled with Android API version 29. - Bug fixes and performance improvements ### Version 7.4.0 _Released June 2, 2021, correlating with the Marketing Cloud Engagement June 2021 release._ Version 7.4.0 of the Android SDK has been tested with Google Play Services version 17.1.0 and AltBeacon Library version 2.17.1. The minimum compatible Android API version is 21. Compiled with Android API version 29. - Bug fixes and performance improvements ### Version 7.3.1 _Released November 25, 2020, correlating with the Marketing Cloud Engagement November 2020 release._ Version 7.3.1 of the Android SDK has been tested with Google Play Services version 21.0.0 and AltBeacon Library version 2.17.1. The minimum compatible Android API version is 21. Compiled with Android API version 29. - Bug fixes and performance improvements - Fixed a rare issue where the SDK crashed silently during initialization when upgrading from an old version of the SDK - Fixed an issue where clicking a Geofence or Beacon message didn’t open the provided OpenDirect URL - Fixed an issue where the SDK crashed when reobfuscated by the consuming mobile application - Corrected an SDK debug log incorrectly logging as error - Updated third-party dependencies for Google Play Services, Kotlin support, and the AltBeacon library ### Version 7.3.0 _Released October 12, 2020, correlating with the Marketing Cloud Engagement October 2020 release._ Version 7.3.0 of the Android SDK has been tested with Google Play Services version 17.0.0 and AltBeacon Library version 2.16.4. The minimum compatible Android API version is 21. Compiled with Android API version 29. - This release fixes the following issues. - Crashes on Android 21 (Lollipop) - Issues related to the FullImageFill In-App Message type on Android 23 (Marshmallow) - Fixes a rare `IllegalAccessError` on network failure. ### Version 7.2.0 _Released June 1, 2020, correlating with the Marketing Cloud Engagement June 2020 release._ Version 7.2.0 of the Android SDK has been tested with Google Play Services version 17.0.0 and AltBeacon Library version 2.16.4. The minimum compatible Android API version is 21. Compiled with Android API version 29. - Bug fixes and performance improvements ### Version 7.1.0 _Released March 23, 2020, correlating with the Marketing Cloud Engagement March 2020 release._ Version 7.1.0 of the Android SDK has been tested with Google Play Services version 17.0.0 and AltBeacon Library version 2.16.4. The minimum compatible Android API version is 21. Compiled with Android API version 29. - Image fills for full-page in-app messages: Currently, the full-page in-app message template crops images to a 16:9 aspect ratio. With this update, images can fill a larger portion of the screen and drive engagement with your app. To support image fill for full-page in-app messages, update to the March release of the MobilePush SDK. Image fill is available to customers with MobilePush and Journey Builder. - Bug fixes and performance improvements ### Version 7.0.0 _Released February 24, 2020, correlating with the Marketing Cloud Engagement February 2020 release._ Version 7.0.0 of the Android SDK has been tested with Google Play Services version 17.0.0 and AltBeacon Library version 2.16.4. The minimum compatible Android API version is 21. Compiled with Android API version 29. - Bug fixes and performance improvements
Version 6 Releases ### Version 6.4.0 _Released October 28, 2019, correlating with the Marketing Cloud Engagement October 2019 release._ Version 6.4.0 of the Android SDK has been tested with Google Play Services version 17.0.0 and AltBeacon Library version 2.16.3. The minimum compatible Android API version is 16. Compiled with Android API version 29. - Bug fixes and performance improvements ### Version 6.3.5 _Released September 25, 2019, correlating with the Marketing Cloud Engagement June 2019 release._ Version 6.3.5 of the Android SDK has been tested with Google Play Services version 16.0.0 and AltBeacon Library version 2.16.2. The minimum compatible Android API version is 16. Compiled with Android API version 29. - Bug fixes and performance improvements ### Version 6.3.4 _Released July 25, 2019 correlating with the Marketing Cloud Engagement June 2019 release._ Version 6.3.4 of the Android SDK has been tested with Google Play Services version 16.0.0 and AltBeacon Library version 2.16.2. The minimum compatible Android API version is 16. Compiled with Android API version 29. - Android Q Support: This release of the SDK adds support for the new `ACCESS_BACKGROUND_LOCATION` permission. The changes in Android Q require that you request this permission from your users when on an Android Q device for Geofence and Beacon messaging. For more information, see [Implement Location Messaging on Android](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_location_messages/mc_engagement_location_messages_android.md). - `JobIntentService` bug fix: Added code to prevent an unhandled exception thrown by Google’s `JobIntentService`. - Inbox message status: This release better reflects the read or deleted state of an inbox message in Engagement. - New LearningApp: This release includes an updated, simplified, and modern sample app using the MobilePush SDK. For more information, see [MobilePush SDK Android LearningApp](https://github.com/salesforce-marketingcloud/MarketingCloudSDK-Android/tree/master). ### Version 6.3.3 _Released June 25, 2019, correlating with the Marketing Cloud Engagement June 2019 release._ Version 6.3.3 of the Android SDK has been tested with Google Play Services version 16.0.0 and AltBeacon Library version 2.16.1. The minimum compatible Android API version is 16. Compiled with Android API version 28. - Deliver in-app messages: Deliver relevant, personalized messages to your app’s users. Send messages without relying on users having enabled push notifications. Engaging full-screen, modal, or banner messages are presented while your users are interacting with your app. For more information, see [Implement In-App Messaging on Android](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_in-app_messages/mc_engagement_in-app_messages_android.md). - Improved database recovery: In rare instances, the database used by the SDK becomes corrupt. To resolve any issues before initialization is complete, we added code to validate the database and its structure during initialization. - Fixed rare system bug: Certain Android devices and versions can cause issues when modifying the message data associated with a notification’s `PendingIntent`. To avoid these issues, we changed the structure of the data stored in the `PendingIntent`. ### Version 6.2.2 _Released May 21, 2019, correlating with the Marketing Cloud Engagement April 2019 release._ Version 6.2.2 of the Android SDK has been tested with Google Play Services version 16.0.0 and AltBeacon Library version 2.16.1. The minimum compatible Android API version is 16. Compiled with Android API version 28. - Prevent crash on Android O or newer: Some devices running Android O or newer can exhibit a bug where the SDK attempts to create a job using Android’s `JobScheduler` when there are already 100 scheduled jobs, resulting in Android throwing an `IllegalStateException`. We added code to prevent this crash and improve logging when the issue occurs. ### Version 6.2.1 _Released April 23, 2019, correlating with the Marketing Cloud Engagement April 2019 release._ Version 6.2.1 of the Android SDK has been tested with Google Play Services version 16.0.0 and AltBeacon Library version 2.16.1. The minimum compatible Android API version is 16. Compiled with Android API version 28. - Required app endpoint (tenant-specific endpoint): To pass the SDK’s configuration, an app endpoint is now required. Find the app endpoint for your app under Administration in MobilePush. Review Configuration Requirements for details. - Enforced critical update to Firebase Cloud Messaging for Android SDK: For your app to continue receiving messages, update your SDK to version 6.0.1 or later and configure your app with Firebase initialized. - Added ability to delay registration until the contact key is set: Use a new SDK configuration value to delay registrations to Engagement until a contact key is set via setDelayRegistrationUntilContactKeyIsSet(). Review Delay Registration for details. - Inbox messages support sendDateUtc for sorting: Inbox messages delivered to your app now include the date that the message was sent. App users can sort their inbox based on this value. For more information, see [Implement Inbox Messaging on Android](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_inbox_messages/mc_engagement_inbox_messages_android.md). - Added ability to set read or deleted by inbox message ID only: Added convenience methods to set the status of an inbox message to read or deleted with only the message’s ID as an argument. ### Version 6.1.0 _Released February 11, 2019, correlating with the Marketing Cloud Engagement January 2019 release._ Version 6.1.0 of the Android SDK has been tested with Google Play Services version 16.0.0 and AltBeacon Library version 2.15.2. The minimum compatible Android API version is 16. Compiled with Android API version 28. - Implemented message segmentation: The Android SDK now supports app control over which push notifications, geofence messages, and beacon messages are displayed. Use the region information provided for geofence and beacon messages in your notification presentation logic. Review Notification Segmentation. - Implemented predictive intelligence identifier (PIID) configuration options and APIs: Configure the identifier for Predictive Intelligence analytics according to how you use Personalization Builder. Configure your applications to use either existing contact key data or a PI-specific identifier. For more information, see [Enable and Use Analytics on Android](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_analytics/mc_engagement_analytics_android_implement.md). - Added ability to unregister a `WhenReadyListener` passed to `requestSdk`: For more information, see the reference documentation for [`unregisterWhenReadyListener()`](https://salesforce-marketingcloud.github.io/MarketingCloudSDK-Android/javadocs/MarketingCloudSdk/8.0/-marketing%20-cloud%20-s-d-k/com.salesforce.marketingcloud/-marketing-cloud-sdk/unregister-when-ready-listener.html). ### Version 6.0.2 (Revised) _Released December 5, 2018._ Version 6.0.2 of the Android SDK has been tested with Google Play Services version 15.0.1 and AltBeacon Library version 2.14. The minimum compatible Android API version is 16. Compiled with Android API version 27. - Corrected a registration frequency issue in the SDK that allows for multiple registration requests to be sent to Engagement within a small amount of time. Now, registration edits are properly batched and sent one time per minute. - Improved `SdkState` logging output to support you during debugging sessions. ### Version 6.0.2 _Released October 22, 2018, correlating with the Marketing Cloud Engagement 215 release._ Version 6.0.2 of the Android SDK has been tested with Google Play Services version 15.0.1 and AltBeacon Library version 2.14. The minimum compatible Android API version is 16. Compiled with Android API version 27. - Replaced GCM with FCM: We removed the deprecated Google Cloud Messaging library and replaced it with Firebase Cloud Messaging. Configure your application so that Firebase is initialized. For more information, see [Integrate the MobilePush Android SDK](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_integrate_android/engagement_sdk_guide_integrate_android.md). - Simplified notification customization and handling: We've simplified the `MarketingCloudConfig.Builder` by consolidating all of the notification customization options into a single `NotificationCustomizationOptions` class. For more information, see [Customize Push Notification Functionality for Android Apps](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_push_notifications/mc_engagement_push_notifications_android_customize.md). - Fewer required dependencies: The Google Play Services Location and AltBeacon dependencies are no longer declared in the SDK’s `pom.xml` file as required dependencies. If your application requires these features, follow the instructions provided in [Implement Location Messaging on Android](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_location_messages/mc_engagement_location_messages_android.md). - Improved initialization verification: To make sure that the necessary information is provided before the SDK is initialized, we've added additional checks to `MarketingCloudConfig.Builder`. These checks make sure that an icon resource for notifications is provided and that notification channels are handled. To allow for this change, update your call to `MarketingCloudConfig.Builder#build(Context)` to pass in an `Android` context. - Default notification channel: The SDK now creates a default notification channel named “Marketing”. For information on how to modify this channel, see [Implement Default and Custom Notification Channels](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_push_notifications/mc_engagement_push_notifications_android_custom_notification.md). - Removed `Attribute` class: We removed the previously deprecated `Attribute` class, along with any associated methods. Registration attributes are now provided in a key-value `Map`. - Removed `DefaultUrlPresenter`: To address potential security concerns, we removed the SDK’s default URL presenter. Consequently, if your message involves redirection to a web URL, resource, file, or other custom application schema driven by business logic, override notification handling. For more information, see [Handling URLs and Custom Keys](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_handle_urls.md). - Tenant-Specific Endpoint: Two new methods were added to `MarketingCloudConfig.Builder` to facilitate Tenant-Specific Endpoints: `setMarketingCloudServerUrl()` and `setMid()`. These methods configure the SDK to communicate with the specific server for your application. For guidance on where to find your Tenant-Specific Endpoint and MID, see [Updating Engagement Endpoints to Tenant-Specific Endpoints: FAQ](https://help.salesforce.com/s/articleView?id=000392227&type=1). - Improved Kotlin interoperability: Addressed issues reported by the Kotlin interoperability Android lint check. - Added nullability annotations to all public APIs. - Reversed parameter order of MarketingCloudSdk’s `whenReady` method to make the interface eligible for SAM conversion. - Fixed region message URL locale bug: For locales that don’t use `.` as the decimal separator, the SDK requests region messages in a format that Engagement doesn’t support. We corrected this issue to enforce that `.` is used, regardless of device locale.
## iOS This section contains information about releases of the MobilePush SDK for iOS, including version numbers, release dates, compatibility details, and key changes. ### Latest Release: Version 11.0.2 _Released July 23, 2026_ Resolved a race condition that crashed the SDK when accessing event configuration data. ### Version 11.0.1 _Released June 26, 2026_ Fixed the In-App DisplayCompleted event analytics to accurately capture buttonId for button dismissals. ### Version 11.0.0 _Released March 31, 2026_ Version 11.0.0 of the SDK is a major release that introduces a new improved In-App Messaging feature module. For information about migrating iOS apps to version 11 of the SDK, see [Migrate to Version 11](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_upgrade/mc_engagement_upgrade_ios_v11.md). The minimum compatible iOS API version is 12. - Performance improvements and bug fixes. - SFMC module version 4.0.0 (compatible with this module version 11.0.0 and above) - Extension SDK version 3.0.0 (compatible with this module version 11.0.0 and above) - Push Feature module version 2.0.0 (compatible with this module version 11.0.0 and above) - InAppMessaging Feature module version 1.0.0 (compatible with this module version 11.0.0 and above)
Version 10 Releases ### Version 10.0.0 _Released November 6, 2025_ Version 10.0.0 of the SDK is a major release that introduces a new unified SDK architecture. For information about migrating iOS apps to version 10 of the SDK, see [Migrate to the SDK for iOS Version 10](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_upgrade/mc_engagement_upgrade_ios_v10.md). The minimum compatible iOS API version is 12. - Bug fixes and performance improvements. - SFMCSDK version 3.0.0 (compatible with Marketing Cloud SDK versions 10.0.0 and above). - Extension SDK version 2.0.0 (compatible with Marketing Cloud SDK versions 10.0.0 and above). - Push Feature SDK version 1.0.0 (compatible with Marketing Cloud SDK versions 10.0.0 and above).
Version 9 Releases ### Version 9.0.3 _Released July 2, 2025_ - Performance improvements and bug fixes for the In-App Messaging functionality. - Extension SDK version 1.0.3 released on December 16, 2025 (compatible with MobilePush versions 9.0.3 and later). Update to this version to get improved UI for the push notification carousel navigation buttons. ### Version 9.0.2 _Released June 11, 2025_ - Resolved Apple digital certificate signing issue found in versions 9.0.0 and 9.0.1. - SFMCSDK version 2.0.1 (compatible with Push Module versions 9.0.2 and later). - Extension SDK version 1.0.2 (compatible with Push Module versions 9.0.2 and later). ### Version 9.0.1 _Released May 26, 2025_ - Thumbnail support: Enable or disable the first image of the Carousel template as a thumbnail. For implementation details, see [Configure Thumbnail](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_integrate_ios_extension/mc_engagement_integrate_ios_extension_configure_service.md#configure-thumbnail). - Extension SDK version 1.0.1 (compatible with Push Module versions 9.0.1 and later). - Bug fixes and performance improvements. - Update to version 9.0.2 to resolve the Apple digital certificate signing issue found in this version. ### Version 9.0.0 _Released March 14, 2025, correlating with the Marketing Cloud Engagement March 2025 release._ - Carousel push notifications – Send interactive carousel push notifications to your app users. For implementation details, see [Integrate the MobilePush Extension SDK](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_integrate_ios_extension/mc_engagement_integrate_ios_extension.md). - Push Delivery event – Get a delivered ENS event when a push message successfully reaches a user’s device. For more details, see [Integrate the MobilePush Extension SDK](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_integrate_ios_extension/mc_engagement_integrate_ios_extension.md). - Inbox 2.0 Support – Send enhanced inbox messages with additional fields like subtitles and messages, plus new CTA options (App/Web URL, None) beyond only CloudPage. For implementation details, see [Implement Inbox Messaging on iOS](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_inbox_messages/mc_engagement_inbox_messages_ios.md). - Bug fixes and performance improvements. - Extension SDK version 1.0.0 (compatible with Push Module versions 9.0.0 and later). - SFMCSDK version 2.0.0 (compatible with Push Module versions 9.0.0 and later). - Update to version 9.0.2 to resolve the Apple digital certificate signing issue found in this version.
Version 8 Releases ### Version 8.1.4 _Released June 11, 2025_ - Resolved Apple digital certificate signing issue that occurs with versions 8.1.1, 8.1.2, and 8.1.3. - SFMCSDK version 1.1.4 (compatible with Push Module versions 8.1.4 and later). ### Version 8.1.3 _Released July 23, 2024, correlating with the Marketing Cloud Engagement July 2024 release._ - Resolved hang issues occurring during the first launch and app upgrades, resulting in improved SDK performance. - Fixed an issue affecting Inbox Open Analytics when the Inbox Replace feature is enabled. - Bug fixes and performance improvements. - SFMCSDK version 1.1.3 (compatible with Push Module versions 8.1.2 and later). - Update to version 8.1.4 to resolve the Apple digital certificate signing issue found in this version. ### Version 8.1.2 _Released February 27, 2024, correlating with the Marketing Cloud Engagement February 2024 release._ - Privacy Manifest – Adds a privacy manifest that declares the default data collected by the SDK as per [Apple’s privacy requirements for third-party SDKs](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files). For more information, see [Apple Privacy Manifest Guide](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/mc_engagement/mc_engagement_integrate_ios/engagement_sdk_guide_integrate_ios_privacy_manifest.md). - SFMCSDK version 1.1.2 (compatible with Push Module versions 8.1.2 and later). - Update to version 8.1.4 to resolve the Apple digital certificate signing issue found in this version. ### Version 8.1.1 _Released January 18, 2024, correlating with the Marketing Cloud Engagement January 2024 release._ Version 8.1.1 of the iOS SDK requires SFMC SDK v1.0.8. The minimum compatible iOS API version is 12. - Bug fixes and performance improvements - Framework code signatures: Code signatures have been added to all frameworks. - Alert + Inbox “Tap To Read”: Configure the SDK to mark an inbox message as “read” when a user taps the push notification for an Alert + Inbox message. For more information, see [Implement Inbox Messaging on iOS](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/mc_engagement/mc_engagement_inbox_messages/mc_engagement_inbox_messages_ios.md). - Discontinued support for iOS 11. - Update to version 8.1.4 to resolve the Apple digital certificate signing issue found in this version. ### Version 8.1.0 _Released October 30, 2023, correlating with the Marketing Cloud Engagement October 2023 release._ Version 8.1.0 of the iOS SDK requires SFMC SDK v1.0.8. The minimum compatible iOS API version is 11. - Bug fixes and performance improvements - Runtime Toggles: Enable or disable Analytics, Inbox, Geofence Messaging, and Proximity Messaging at runtime. For more information, see [Runtime Toggles](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_runtime_toggles.md). - `MarketingCloudSDK.bundle` Integration: We've eliminated the need for manual addition of `MarketingCloudSDK.bundle` as an application resource, streamlining the integration process. - New API – Added an API, `requestPushSdk`, which guarantees access to the Push module when it becomes available. - MarketingCloudSDK integration via Swift Package Manager (SPM): Integration via SPM now automatically includes SFMCSDK, simplifying integration efforts. - Improved logging for multiple push providers: Introduced enhanced log messages to warn users about multiple push providers, aiding in proactive implementation decisions. - Initialization issues on locked devices: Fixed an issue where the SDK failed to initialize when the device was locked and no keychain or data protection was available. - Compatibility fix for iOS 11: Addressed initialization issues specific to iOS 11, ensuring seamless integration and functionality on this platform. - Enhanced diagnostic tooling: The MobilePush iOS SDK now detects and logs SDK implementation issues, providing guidance in the log output for smoother implementations. ### Version 8.0.13 _Released May 3, 2023, correlating with the Marketing Cloud Engagement May 2023 release._ Version 8.0.13 of the iOS SDK requires SFMC SDK v1.0.8. The minimum compatible iOS API version is 11. - Bug fixes and performance improvements. ### Version 8.0.12 _Released March 27, 2023, correlating with the Marketing Cloud Engagement March 2023 release._ Version 8.0.12 of the iOS SDK requires SFMC SDK v1.0.8. The minimum compatible iOS API version is 11. - Bug fixes and performance improvements. - Adds registration callbacks: Added the ability to pass a single callback to listen to registration events. - Adds configurable filesystem protection types: Added the ability to configure the SDK’s [protection values](https://developer.apple.com/documentation/foundation/fileprotectiontype). For an example implementation, see the [MobilePush iOS LearningApp](https://github.com/salesforce-marketingcloud/MarketingCloudSDK-iOS/tree/master/LearningApp). - Fixes crashes due to Xcode archive overriding the default `CFBundleShortVersionString` within the framework. - Addresses crashes caused by back-to-back initializations of the SDK. - Deprecates `tearDown` methods: The SDK now handles tear-downs internally. - Improved data merge tool performance. ### Version 8.0.10 _Released January 24, 2023, correlating with the Marketing Cloud Engagement January 2023 release._ Version 8.0.10 of the iOS SDK requires SFMC SDK v1.0.8. The minimum compatible iOS API version is 11. - This release includes bug fixes and SDK improvements. **important:** This version deprecates support for iOS versions 10.0 and older, and Xcode versions 13.x and older. ### Version 8.0.9 _Released December 7, 2022, correlating with the Marketing Cloud Engagement December 2022 release._ Version 8.0.9 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - Bug fix for push open reporting and Inbox message retrieval. ### Version 8.0.8 _Released September 29, 2022, correlating with the Marketing Cloud Engagement October 2022 release._ Version 8.0.8 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - Support for ENS. - This release includes bug fixes, SDK, and performance improvements. ### Version 8.0.7 _Released August 18, 2022, correlating with the Marketing Cloud Engagement August 2022 release._ Version 8.0.7 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - This release includes fixes for Objective-C compatibility - SDK data merge: This release includes a tool that facilitates the reconciliation of the dataset associated with the v7.x SDK and the current dataset for v8.x SDK users. For information, see [Troubleshoot Data Merge](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_troubleshooting/mc_engagement_troubleshooting_ios_data_merge.md). ### Version 8.0.6 _Released April 14, 2022, correlating with the Marketing Cloud Engagement March 2022 release._ Version 8.0.6 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - Bug fixes and performance improvements. ### Version 8.0.5 _Released March 31, 2022, correlating with the Marketing Cloud Engagement January 2022 release._ Version 8.0.5 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - This release fixes the following issues. - Swizzling ViewDidAppear - Keychain crashes in iOS 15 - Adds namespacing to encryption files in SFMCSDK. - Library evolution with Xcode 12.5 as minimum Xcode compatibility. ### Version 8.0.4 _Released February 4, 2022, correlating with the Marketing Cloud Engagement January 2022 release._ Version 8.0.4 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - This release fixes the following issues. - Open Direct URL - Swizzling `ViewDidAppear` - Version conflict when uploaded to TestF light and similar apps - Support for CocoaPods along with Swift Package Manager. ### Version 8.0.3 _Released January 3, 2022, correlating with the Marketing Cloud Engagement January 2022 release._ Version 8.0.3 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - This release includes fixes for the validation process (bundle collision and structure). ### Version 8.0.2 _Released December 14, 2021, correlating with the Marketing Cloud Engagement December 2021 release._ Version 8.0.2 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - This release includes a fix for the profile attributes API. ### Version 8.0.1 _Released October 28, 2021, correlating with the Marketing Cloud Engagement October 2021 release._ Version 8.0.1 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - This release includes open attributes API and `InboxMessage` UI support fixes. ### Version 8.0.0 _Released October 14, 2021, correlating with the Marketing Cloud Engagement October 2021 release._ Version 8.0.0 of the iOS SDK requires SFMC SDK v1.0.6. The minimum compatible iOS API version is 10. - Bug fixes and performance improvements. - Introducing Swift Packages. - Discontinuation of CocoaPods support in favor of Swift Package Manager. For guidance on migrating to SDK version 8.x, see [Migrate to the MobilePush SDK for iOS Version 8](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_upgrade/mc_engagement_upgrade_ios_v8.md).
Version 7 Releases ### Version 7.6.0 _Released June 2, 2021, correlating with the Marketing Cloud Engagement June 2021 release._ The minimum compatible iOS API version is 10. - Bug fixes and performance improvements. ### Version 7.5.1 _Released May 25, 2021, correlating with the Marketing Cloud Engagement May 2021 release._ The minimum compatible iOS API version is 10. - In App banner message bug fix: Fixes an issue where banner In-App messages crash on iOS 14. ### Version 7.5.0 _Released March 17, 2021, correlating with the Marketing Cloud Engagement March 2021 release._ The minimum compatible iOS API version is 10. - Packaged SDK as an XCFramework: The SDK is now packaged as an XCFramework, supporting arm64 simulators on Macs with M1 Chipsets. ### Version 7.4.0 _Released February 11, 2021, correlating with the Marketing Cloud Engagement February 2021 release._ The minimum compatible iOS API version is 10. - Improve Inbox Messages sync when force closing app: Improved chances of syncing inbox message status with the server for end users who force close the app. - Bug fixes and performance improvements. ### Version 7.3.1 _Released December 22, 2020, correlating with the Marketing Cloud Engagement November 2020 release._ The minimum compatible iOS API version is 10. - Added Support for arm64e: Explicitly added arm64e architecture to enable reading debug symbols on arm64e devices. ### Version 7.3.0 _Released November 11, 2020, correlating with the Marketing Cloud Engagement November 2020 release._ The minimum compatible iOS API version is 10. - Fixes for rare race conditions linked to customer reported crash reports showing crash during SDK tear down following the successful deletion of data prompted by a GDPR request. - Fix possible naming collisions with Objective-C Classes: Renamed `Event` class to minimize potential naming collisions for customers using Objective-C. ### Version 7.2.2 _Released August 31, 2020, correlating with the Marketing Cloud Engagement June 2020 release._ The minimum compatible iOS API version is 10. - Bug fixes and performance improvements. ### Version 7.2.1 _Released July 6, 2020, correlating with the Marketing Cloud Engagement June 2020 release._ The minimum compatible iOS API version is 10. - Bug fixes and performance improvements. - Fixes an issue where the custom data field wasn’t present in inbox messages. ### Version 7.2.0 _Released June 1, 2020, correlating with the Marketing Cloud Engagement June 2020 release._ The minimum compatible iOS API version is 10. - Bug fixes and performance improvements. ### Version 7.1.1 _Released May 18, 2020, correlating with the Marketing Cloud Engagement March 2020 release._ The minimum compatible iOS API version is 10. - Added armv7 support: We had previously removed armv7 support, restricting support to armv7s and arm64 architectures. This release provides armv7, armv7s, and arm64 support. ### Version 7.1.0 _Released March 23, 2020, correlating with the Marketing Cloud Engagement March 2020 release._ The minimum compatible iOS API version is 10. - Image Fill for full-page in-app messages: Currently, the full-page in-app message template crops images to a 16:9 aspect ratio. With this update, images can fill a larger portion of the screen and drive engagement with your app. To support image fill for full-page in-app messages, update to the March release of the MobilePush SDK. Image fill is available to customers with MobilePush and Journey Builder. ### Version 7.0.1 _Released January 25, 2020, correlating with the Marketing Cloud Engagement January 2020 release._ The minimum compatible iOS API version is 10. - JSON configuration method removal: The `sfmc_configure` and `sfmc_configureWithURL` SDK configuration methods, using the `MarketingCloudSDKConfiguration.json` file, have been removed. If you’re upgrading to this version of the SDK, see [Integrate the MobilePush iOS SDK](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_integrate_ios/mc_engagement_integrate_ios.md) for an example of using our `ConfigBuilder` for simple, code-based SDK configuration. - Required minimum deployment target of iOS 10.0: Existing mobile applications continue to function, without change. Mobile applications can continue to reference older SDK versions, without change. Applications that adopt the January 2020 MobilePush SDK release require a project change, if your application build still supports iOS 9.
Version 6 Releases ### Version 6.4.2 _Released December 27, 2019, correlating with the Marketing Cloud Engagement October 2019 release._ - Bug fixes and performance improvements for devices running iOS 13. ### Version 6.4.1 _Released November 22, 2019, correlating with the Marketing Cloud Engagement October 2019 release._ - Bug fixes and performance improvements. - Updated LearningApp for iOS data protection: This release includes an updated, simplified, and modern sample app using the MobilePush SDK. For more information, see the [MobilePush iOS LearningApp](https://github.com/salesforce-marketingcloud/MarketingCloudSDK-iOS/tree/master/LearningApp). ### Version 6.4.0 _Released October 28, 2019, correlating with the Marketing Cloud Engagement October 2019 release._ - JSON configuration method deprecation: The `sfmc_configure` and `sfmc_configureWithURL` SDK configuration methods, using the `MarketingCloudSDKConfiguration.json` file, have been deprecated. These methods will be removed in the next SDK release. If you’re upgrading to this version of the SDK, see [Configure the MobilePush iOS SDK](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_integrate_ios/mc_engagement_integrate_ios_configure.md) for an example of using our `ConfigBuilder`. - Immediate registration after install: To more effectively establish an Engagement contact, a MobilePush registration is sent immediately following the first SDK configuration after a new app install. Subsequent registrations are deferred for up to 60 seconds, as described in [Contact and Device Registration](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_register_contacts_devices/mc_engagement_register_contacts_devices.md). ### Version 6.3.6 _Released September 26, 2019, correlating with the Marketing Cloud Engagement June 2019 release._ - Bug fixes and performance improvements. - In-App message layout improvements: On iOS 13 devices, when in-app messages are displayed on an iPad in Split View modes, messages are sized appropriately. ### Version 6.3.4 _Released July 25, 2019, correlating with the Marketing Cloud Engagement June 2019 release._ - New LearningApp for iOS: This release includes an updated, simplified, and modern sample app using the MobilePush SDK. For more information, see the [MobilePush iOS LearningApp](https://github.com/salesforce-marketingcloud/MarketingCloudSDK-iOS/tree/master/LearningApp). - Inbox message status: This release better reflects the `read` or `deleted` state of an inbox message in Engagement. ### Version 6.3.3 _Released June 17, 2019 correlating with the Marketing Cloud Engagement June 2019 release._ - Deliver in-app messages: Deliver relevant, personalized messages to your app’s users. Send messages without relying on users having enabled push notifications. Engaging full-screen, modal, or banner messages are presented while your users are interacting with your app. For more information and implementation guidance, see [Implement In-App Messaging on iOS](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_in-app_messages/mc_engagement_in-app_messages_ios.md). ### Version 6.2.3 _Released May 21, 2019, correlating with the Marketing Cloud Engagement April 2019 release._ - Fixed issue with inbox start date: Inbox messages now respect `startDateUtc` payload values in all cases. ### Version 6.2.2 _Released May 2, 2019, correlating with the Marketing Cloud Engagement April 2019 release._ - Removed SDK test code from the library: Test code associated with SDK development was removed from the public release. - Fixed location messaging date calculation: Fixed an issue in calculating the "next show date" for location messages, where previously there was a discrepancy of one day. ### Version 6.2.0 _Released April 23, 2019, correlating with the Marketing Cloud Engagement April 2019 release._ - Required app endpoint (Tenant-Specific Endpoint): Passing the SDK’s configuration now mandates an app endpoint. Locate your app’s endpoint under **Administration** in the MobilePush UI. For guidance on where to find your Tenant-Specific Endpoint, see [Updating Engagement Endpoints to Tenant-Specific Endpoints: FAQ](https://help.salesforce.com/s/articleView?id=000392227&type=1). - Added application badging override: A new SDK configuration value gives you full control of your app’s badge value. - Added ability to delay registration until the contact key is set: Use a new SDK configuration value to delay registrations to Engagement until a contact key is set via `sfmc_setContactKey:`. For more information, see [Delay Registrations Until Contact Key is Set](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_register_contacts_devices/mc_engagement_register_contacts_devices_contact_dissociation.md#delay-registrations-until-contact-key-is-set). - Inbox messages support `sendDateUtc` for sorting: Inbox messages delivered to your app now include the date that the message was sent. App users can sort their inbox based on this value. For more information, see [Implement Inbox Messaging on iOS](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_inbox_messages/mc_engagement_inbox_messages_ios.md). - Better tracking of "open from push" analytics: The SDK now captures "open from push" analytics more effectively when the application isn’t running, especially when configured asynchronously. - Fixed an issue with the `ConfigurationBuilder`: Fixed an issue with using the `ConfigurationBuilder` method to configure the SDK that caused an authorization error when contacting Engagement. ### Version 6.1.4 _Released February 28, 2019, correlating with the Marketing Cloud Engagement January 2019 release._ Corrected an issue that prevented a location or proximity `CloudPage+Alert` message from displaying. ### Version 6.1.3 _Released February 11, 2019, correlating with the Marketing Cloud Engagement January 2019 release._ - Implemented location message segmentation: The SDK now supports app control over which geofence and beacon messages are displayed. Use the region information provided for geofence and beacon messages in your notification presentation logic. For details, see [Location Message Segmentation](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_location_messages/mc_engagement_location_messages_ios_segment.md). - Implemented Predictive Intelligence Identifier (PIID) configuration options and APIs: Configure the identifier for Predictive Intelligence analytics according to how you use Personalization Builder. Configure your applications to use either existing contact key data or a PI-specific identifier. For details, see [Enable and Use Analytics on iOS](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_analytics/mc_engagement_analytics_ios_implement.md). - Added time for iOS file protection transitions: Added a guarding mechanism that makes sure iOS file protection transitions are complete before the SDK completes configuration. To accommodate these transitions, the SDK waits up to 5 seconds, without blocking other functions. If the UIApplication’s `isProtectedDataAvailable` returns `NO`, then configuration fails. - Fixed Predictive Intelligence analytics issues: Fixed issues related to sending Predictive Intelligence analytics when using the MID configuration value. - Fixed location messaging issue: Resolved an issue where reloading location messages from the server displayed a message limited by the display settings again, contrary to the intended message setting. ### Version 6.0.1 _Released December 5, 2018._ - Analytics: Addressed an issue sending analytics to Predictive Intelligence when using the MID configuration value. - Networking: Reduced the number of network calls made to Engagement servers during the lifecycle of the SDK. ### Version 6.0.0 _Released October 22, 2018, correlating with the Marketing Cloud Engagement October 2018 release._ - Implemented Tenant Specific Endpoint support for Engagement Accounts: Configure new MobilePush applications to use account-specific settings. For information on configuring the SDK, see [Integrate the MobilePush iOS SDK](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_integrate_ios/mc_engagement_integrate_ios.md). - Removed SDK-provided web view for URLs: To address potential security concerns, we removed the SDK’s default URL presenter. Consequently, if your message involves redirection to a web URL, resource, file, or other custom application schema driven by business logic, provide the SDK with a delegate and implementation of the `MarketingCloudSDKURLHandlingDelegate` protocol. For more information, see [Handling URLs and Custom Keys](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_handle_urls.md). - Removed the following SDK protocols and protocol methods: - `MarketingCloudSDKCloudPageMessagesNotificationHandlerDelegate` - `MarketingCloudSDKOpenDirectMessagesNotificationHandlerDelegate` - `MarketingCloudSDKInboxMessagesNotificationHandlerDelegate` **important:** Update your code to implement the `MarketingCloudSDKURLHandlingDelegate` protocol. - Inbox functionality improvements: - When an Alert+Inbox push notification arrives with the app in the foreground, inbox messages are reloaded from the server automatically. - Inbox message handling better tracks active messages in the inbox based on their start and end date values. - SDK Configuration: Added the `sfmc_configureWithDictionary:` method to configure the SDK via runtime values passed to SDK.
Version 5 Releases ### Version 5.2.1 _Released August 27, 2018, correlating with the Marketing Cloud Engagement July 2018 release._ Addressed issues related to multithreading and core data concurrency. ### Version 5.1.1 _Released July 31, 2018._ - Addressed issues related to multi-threading in the SDK - Updated the build process to include the i386 architecture, which allows you to run 32-bit simulators - Corrected an issue related to loading resources on armv7s devices ### Version 5.1.0 _Released July 23rd, 2018, correlating with the Marketing Cloud Engagement April 2018 release._ - Added iOS 9 support: The iOS MarketingCloudSDK framework now supports iOS 9. Use conditional coding via Apple’s available attributes. For notes on using conditional coding for push registration and handling push notifications, see the iOS 9 documentation. - Added synchronous configuration calls: To prevent developers from trying to set a contact key, tag, or attribute before configuration is complete, we added synchronous configuration calls to the API as the default. - Added data privacy compliance: This version of the iOS MarketingCloudSDK supports three privacy modes that can affect your application’s use of MobilePush: Right to be Forgotten, Restriction of Processing, and Don’t Track. These changes assist you in preparing for data compliance regulations, such as the European Union’s General Data Protection Regulation (GDPR). For more information, see [Data Protection and Privacy](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_data_protection_privacy.md). - Throttled inbox message calls: To match the Android SDK, we now prevent the iOS MarketingCloudSDK from calling `sfmc_refreshMessages` too often. Reference the headers for more information. - Allowed Predictive Intelligence to be set separately: When you configure the iOS MarketingCloudSDK, enable or disable Predictive Intelligence separately from Analytics. If your app uses the iOS MarketingCloudSDK version 5.0.0 framework with analytics enabled, then Predictive Intelligence is also enabled. To control Predictive Intelligence separately, add the `config` flag. - Improved registration: We improved registration to prevent duplicate tags and attributes. - Fixed `isPushEnabled` override issue: Previously, disabling push notifications in the Notification Center overrode the `setPushEnable` property. We fixed this issue so that the SDK uses `setPushEnable`. ### Version 5.2.0 _Released July 11, 2018, correlating with the Marketing Cloud Engagement July 2018 release._ - Added checks to prevent exceptions: Added `nil` checks to prevent potential exceptions that occur when users swipe to close an app. - Improved log string initializers: To help prevent Xcode Address Sanitizer warnings, we improved the SDK’s use of log string initializers. - Device ID migration: The SDK attempts to migrate the `deviceId` from versions of JB4ASDK 4.x.x, if possible. ### Version 5.0.0 _Released January 22, 2018, correlating with the Marketing Cloud Engagement January 2018 release._ - We redesigned the SDK to make it easier to integrate than ever before. This release includes a slimmer API that makes it easier to add Engagement features to your app. Existing users can upgrade their version to take advantage of the improved SDK. New users can follow the existing Getting Started directions to get the SDK up and running. - We updated the SDK for full support of iOS 11.
## Cordova This section contains information about releases of the Salesforce Marketing Cloud Cordova Plugin, including version numbers, compatibility details, and key changes. ### Latest Release - Version 8.1.1 - Fix for Open Direct link not working when app is in killed state for iOS.
View changelog for earlier releases ### Version 8.1.0 - Runtime Toggles – Enable and disable Analytics and Predictive Intelligence (PI) analytics at runtime. For more information, see the [Cordova Plugin API Reference](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_development_frameworks/mc_engagement_development_frameworks_cordova_ref.md). - Android 14 support - Bug fixes and performance improvements ### Version 8.0.0 - Android 13 support - Integrated with the Engagement SDK, which includes support for mobile app events - Bug fixes and performance improvements ### Version 7.5.0 - Uses 7.4+ versions of the Android and iOS MobilePush SDK - Adds Behavioral Triggers for InApp messaging functionality. For more information, see `track()`. ### Version 7.4.3 - Uses 7.x versions of the Android and iOS MobilePush SDK - Fix Insecure Maven URL for downloading MobilePush SDK in Android ### Version 7.4.2 - Uses 7.x versions of the Android and iOS MobilePush SDK. - This plugin version requires Cordova Android 9.0.0 as the minimum version to build, which makes the minimum supported Android version as 5.1. - Added support to enable or disable Google Play Services Plugin and change its version change in the `config.xml` file. - Added `AndroidXEnabled` preference as `true`, since the MobilePush SDK for Android depends on these support libraries. ### Version 7.4.1 - Updated to the 7.4.x versions of the Android and iOS MobilePush SDK. - Fix for removing unnecessary Logcat statements on `newIntent()` flow in Android ### Version 7.4.0 - Updated to the 7.4.x version of the iOS MobilePush SDK. ### Version 7.3.0 - Updated to the 7.3.x versions of the Android and iOS MobilePush SDK. ### Version 7.2.0 - Updated to the 7.2.x versions of the Android and iOS MobilePush SDK. ### Version 7.1.0 - Updated to the 7.1.x versions of the Android and iOS MobilePush SDK. ### Version 7.0.0 - Updated to the 7.0.x versions of the Android and iOS MobilePush SDK. ### Version 6.4.0 - Updated to the 6.4.x versions of the Android and iOS MobilePush SDK. ### Version 6.3.1 - Added support for logging the SDK state to the native platform logging system. Uses Logcat in Android, and Console in iOS. - Added documentation for setting up push for iOS. ### Version 6.3.0 - Updated to the 6.3.x versions of the Android and iOS MobilePush SDK. - The plugin now uses CocoaPods for the iOS SDK integration. - Support In-App Messaging functionality of the MobilePush SDK. ### Version 6.2.1 - Updated to the 6.2.x versions of the Android and iOS MobilePush SDK. - Added support to delay registration until the contact key has been set. For more information, see the [Installation documentation](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_development_frameworks/mc_engagement_development_frameworks_cordova.md). - Require Tenant Specific Endpoint in the `config.xml` file. If a Tenant-Specific Endpoint isn’t specified, an exception is thrown. ### Version 6.1.0 - Updated to the 6.1.x versions of the Android and iOS MobilePush SDK. - Added support for listening to notification opened events, enabling you to act when a user clicks a notification, such as loading the url from an OpenDirect or CloudPages message. ### Version 6.0.0 In this release, we have greatly simplified the Cordova plugin for our MobilePush SDK. For successful implementations, if you’re upgrading from a prior release, we suggest following the integration instructions as if you were integrating a new plugin. All functionality of this plugin remains the same as the preceding versions. - The plugin version number now matches with the `major`.`minor` version of the SDK release. - The plugin is now published to npm for easier installation - The JavaScript API has been updated to allow for optional parameters where applicable. For more information, see [API Reference](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_development_frameworks/mc_engagement_development_frameworks_cordova_ref.md). - Moved SDK configuration values from command-line arguments passed in while installing the SDK into the `config.xml` file. ### Version 1.1.0 _Released July 11, 2018_ For Android: Depends on Android Cordova platform 6.4.0. - Updated Android SDK to 5.6.x - Updated iOS SDK to 5.2.x ### Version 1.0.3 _Released April 23, 2018_ - For iOS: Depends on the MobilePush iOS SDK v5.1.x - For Android: Depends on the MobilePush Android SDK v5.5.x, the latest version of Cordova, and Android Cordova platform 6.4.0. - Added support for Cordova iOS cross-platform (CLI) workflow ### Version 1.0.2 _Released January 22, 2018_ - For iOS: Depends on the MobilePush iOS SDK v4.9.x - For Android: Depends on the MobilePush Android SDK v5.3.x, the latest version of Cordova, and Android Cordova platform 6.4.0. - Updated Android SDK to v5.3.+ ### Version 1.0.1 _Released November 29, 2017_ - Depends on the MobilePush iOS SDK v4.9.x - Depends on the MobilePush Android SDK v5.2.x - Updated Android SDK to v5.2.+ ### Version 1.0.0 _Released October 27, 2017_ - Depends on the MobilePush iOS SDK v4.9.x - Depends on the MobilePush Android SDK v5.0.x
## Flutter This section contains information about releases of the Salesforce Marketing Cloud Flutter plugin, including version numbers, compatibility details, and key changes. ### Latest Release - Version 9.0.1 - Fixed issue with the parsing of Inbox CustomKeys: Custom key values sent from Marketing Cloud are now correctly parsed and available in the Inbox message object. - Bug fixes and improvements.
View changelog for earlier releases ### Version 9.0.0 - Support for the 9.0.x versions of the Android and iOS MobilePush SDK. ### Version 8.2.0 - Added APIs that support persistent Inbox and combined Alert + Inbox messaging functionality - Bug fixes and improvements ### Version 8.1.0 - Depends on the 8.1.x versions of the Android and iOS MobilePush SDKs - Initial release
## React This section contains information about releases of the Salesforce Marketing Cloud React Native module, including version numbers, compatibility details, and key changes. ### Latest Release - Version 9.0.0 - Support for the 9.0.x versions of the Android and iOS MobilePush SDK.
View changelog for earlier releases ### Version 8.1.0 - Runtime Toggles – Enable and disable Analytics and PI analytics at runtime. For more information, refer to the [React Plugin API Reference](https://developer.salesforce.com/docs/marketing/mobile-unified-sdk/guide/mc_engagement_development_frameworks/mc_engagement_development_frameworks_react_native_ref.md). - Android 14 support - Bug fixes and performance improvements ### Version 8.0.0 - Android 13 support - Integrated with the Engagement SDK, which includes support for mobile app events - Bug fixes and performance improvements ### Version 7.5.2 - Removed unit tests from released artifact. ### Version 7.5.1 - Android 12 support. Requires v7.4.3 of the Android SDK or higher. ### Version 7.5.0 - Using the 7.4.x versions of the Android MobilePush SDK. ### Version 7.4.3 - Using the 7.4.x versions of the Android MobilePush SDK. ### Version 7.4.2 - Using the 7.4.x versions of the Android MobilePush SDK. ### Version 7.4.0 - Using the 7.4.x versions of the iOS MobilePush SDK. ### Version 7.3.0 - Using the 7.3.x versions of the Android and iOS MobilePush SDK. ### Version 7.2.0 - Using the 7.2.x versions of the Android and iOS MobilePush SDK. ### Version 7.1.0 - Using the 7.1.x versions of the Android and iOS MobilePush SDK. ### Version 7.0.0 - Using the 7.0.x versions of the Android and iOS MobilePush SDK. ### Version 6.4.0 - Using the 6.4.x versions of the Android and iOS MobilePush SDK. ### Version 6.3.x - Initial release - Using the 6.3.x versions of the Android and iOS MobilePush SDK.