Did you know you can be notified automatically about new releases, updates and outages? Register to get updates.
Check out what’s new in each SDK for mobile app messaging in the following sections. For information about supported platforms and sample app compatibility, see Supported platforms and sample apps. For the SDKs, APIs, documentation, and tutorials, go to the IBM Mobile App Messaging feature page.
Note: Native SDK 3.7.1.4 adds support for encryption to the underlying database used by WCA. Because of this, we strongly discourage publishing a release which includes encrypted databases and then rolling back to a previous release which does not include encrypted databases. This is likely to result in data loss. |
Existing Android customers on versions before 3.7.1.0.2 should read the tutorial on Migrating to Android SDK version 3.7.1.0.2 or later.
February 2020 improvements – Compatible with 20.1 Acoustic Campaign Automation
On February 7, Acoustic and IBM Mobile Messaging introduce the following improvements. This release is recommended for all React Native users.
Improvement | Description |
---|---|
React Native SDK 3.8.0 |
Bug Fixes:
Improvements:
Note: To upgrade, you will need to remove the old packages and add new packages. Because the package names in the underlying native SDKs have changed, some manual updates are also required. See the SDK 3.0.1 to 3.8.0 migration guide for React Native for more details. Note: Due to issues building with the latest version of Node.js, Facebook recommends using an earlier version to build on Windows, although users have suggested other solutions. Our environment for this release:
|
January 2020 improvements – Compatible with 20.1 Acoustic Campaign Automation
On January 27th, Acoustic and IBM Mobile Messaging introduce the following improvements. This release is recommended for all Xamarin users.
Improvement | Description |
---|---|
Xamarin SDK 3.8.0 |
Bug Fixes:
Improvements:
Note: With this release, the SDK namespaces have been renamed. All references to “using IBMMobilePush.” should be changed to “using AcousticMobilePush.” instead. In addition, on Android you will need to update your AndroidManifest.mf if you are building for Android. See the migration guide for more details. Note: iOS 13 changes location permission requests so that users cannot grant “always” permission from within your application. See the Prerequisites section of Configuring the iOS SDK for geofence and beacon integration for more details. Note: Due to Apple defect FB7017088, multiple window support for push message actions may not function on iOS 13.0 when the app is not running. Our testing shows that this issue appears to have been fixed in iOS 13.1. Our environment for this release:
Note: The latest versions of Xamarin do not build correctly for 32-bit iOS 10 devices. Builds on earlier versions of Xamarin may work. |
January 2020 improvements – Compatible with 20.1 Acoustic Campaign Automation
On January 14th, Acoustic and IBM Mobile Messaging introduce the following improvements. This release is recommended for all Cordova users. Note that due to Cordova plugin compatibility issues, this release requires Cordova 9.x.
Improvement | Description |
---|---|
Cordova SDK 3.8.0 |
Bug Fixes:
Improvements:
Note: With this release, the SDK namespaces have been renamed. All references to the namespaces in your code will need to be modified. See the Cordova Migration Guide for more details. Note: iOS 13 changes location permission requests so that users cannot grant “always” permission from within your application. See the Prerequisites section of Configuring the iOS SDK for geofence and beacon integration for more details. Our environment for this release:
|
December 2019 improvements – Compatible with 19.4 Acoustic Campaign Automation
On December 6, Acoustic and IBM Mobile Messaging introduce the following improvements. This release is recommended for React Native users who are developing on Windows.
Improvement | Description |
---|---|
React Native SDK 3.0.1 |
Bug Fixes:
Improvements:
Note: Due to issues building with the latest version of Node.js, Facebook recommends using an earlier version to build on Windows. Our tests used 10.15.1. Our environment for this release:
|
November 2019 improvements – Compatible with 19.4 Acoustic Campaign Automation
On November 7th, Acoustic and IBM Mobile Messaging introduce the following improvements. This release is recommended for all Android native users.
Improvement | Description |
---|---|
Android SDK 3.8.0 |
A migration guide from 3.7.1.4 to 3.8.0 is available at Upgrading from Android 3.7.1.4 to Android 3.8.0. Note: We have had at least one report of issues upgrading from previous releases to 3.8.0 when there are old items in the queue. A workaround is available here. This does not affect new installs, only upgrades. Bug Fixes:
Improvements:
Note: This release contains only the DemoAar sample app. Most customers now use AAR format, and this allows us to focus our sample app testing. If you need instructions for migrating to the AAR format, see Migrating a project from jar to aar in Android. Note: If you use location services, you will need to update AndroidManifest.xml and MceConfig.json. See Configuring the Android SDK for geofence and beacon integration. Our environment for this release:
Note: Testing and support for GCM has been removed in anticipation of Google disabling the service. GCM classes still exist in the SDK, and it may continue to work, but have not been tested. We strongly recommend you move to FCM as soon as possible. |
October 2019 improvements – Compatible with 19.4 Acoustic Campaign Automation
On October 9, Acoustic and IBM Mobile Messaging introduce the following improvements. This release is recommended for all iOS native users who wish to use iOS 13 features (including dark mode) or take advantage of the SDK improvements.
Improvement | Description |
---|---|
iOS SDK 3.8.0 |
Bug Fixes:
Improvements:
Note: With this release, the SDK namespaces have been renamed. All references to the namespaces in your code will need to be modified. IBMMobilePushWatch should change to AcousticMobilePushWatch, IBMMobilePushNotificationService should change to AcousticMobilePushNotification (without the “Service” suffix) and any other references to IBMMobilePush should change to AcousticMobilePush. Note: iOS 13 changes location permission requests so that users cannot grant “always” permission from within your application. See the Prerequisites section of Configuring the iOS SDK for geofence and beacon integration for more details. Note: Due to Apple defect FB7017088, multiple window support for push message actions may not function on iOS 13.0 when the app is not running. Our testing shows that this issue appears to have been fixed in iOS 13.1. Our environment for this release:
|
September 2019 improvements – Compatible with 19.4 Acoustic Campaign Automation
On September 24, Acoustic and IBM Mobile Messaging introduce the following improvements. This release is recommended for all React Native users.
Improvement | Description |
---|---|
React Native SDK 3.0.0 |
Bug Fixes:
Improvements:
Our environment for this release:
|
August 2019 improvements – Compatible with 19.3 IBM WCA
On August 16th, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Android native users.
Improvement | Description |
---|---|
Android SDK 3.7.1.4 |
Bug Fixes:
Improvements:
Our environment for this release:
Note: Testing and support for GCM has been removed in anticipation of Google disabling the service. GCM classes still exist in the SDK, and it may continue to work, but have not been tested. We strongly recommend you move to FCM as soon as possible. |
July 2019 improvements – Compatible with 19.3 IBM WCA
On July 1st, IBM Mobile Messaging introduces the following improvements. This release is recommended only for iOS native users who are affected by the issue (or are new users).
Improvement | Description |
---|---|
iOS SDK 3.7.1.4.1 |
Bug Fixes:
Note: This release has corrected a problem with how foreground / background is detected. Because of this, session tracking statistics from previous versions of the SDK may not coincide. Statistics will, however, now be closer to Android statistics for session tracking. Improvements:
Our environment for this release:
|
July 2019 improvements – Compatible with 19.3 IBM WCA Release
On July 1st, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Xamarin users, and strongly recommended for Xamarin Android users supporting Android 5.x or Android 6.x who are seeing null pointer errors in Job-related classes.
Improvement | Description |
---|---|
Xamarin SDK 3.3.2.5 |
Bug Fixes:
Improvements:
Note: Due to a change in Apple binary format and the inclusion of optional libraries, the Apple SDK binary is larger than the previous one on disk. There is no significant change to memory usage on the device. Our environment for this release:
Note: The latest version of Xamarin does not build correctly for 32-bit iOS 10 devices. Builds on earlier versions of Xamarin may work. |
June 2019 improvements – Compatible with 19.3 WCA Release
On June 10th, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Cordova users, and strongly recommended for Cordova users who are experiencing Job-related crashes on Android 5.x and Android 6.x. Note that due to Cordova plugin compatibility issues, this release requires Cordova 9.x.
Improvement | Description |
---|---|
Cordova SDK 3.6.5 |
Bug Fixes:
Improvements:
Our environment for this release:
|
May 2019 improvements – Compatible with 19.2 IBM WCA
On May 22nd, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Android native users who are affected by the issues resolved.
Improvement | Description |
---|---|
Android SDK 3.7.1.3.1 |
Bug Fixes:
Improvements:
Our environment for this release:
Note: Testing and support for GCM has been removed in anticipation of Google disabling the service. GCM classes still exist in the SDK, and it may continue to work, but have not been tested. We strongly recommend you move to FCM as soon as possible. |
April 2019 improvements – Compatible with 19.2 IBM WCA
On April 29th, IBM Mobile Messaging introduces the following improvements. This release is recommended for iOS native users who use location or want the new features.
Improvement | Description |
---|---|
iOS SDK 3.7.1.4 |
Bug Fixes:
Improvements:
Note: Due to a change in Apple binary format, this release is roughly three times as large as the last one on disk. There is no significant change to memory usage on the device. Our environment for this release:
|
April 2019 improvements – Compatible with 19.2 IBM WCA
On April 15th, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Android native users.
Improvement | Description |
---|---|
Android SDK 3.7.1.3 |
Bug Fixes:
Improvements:
Our environment for this release:
Note: Testing and support for GCM has been removed in anticipation of Google disabling the service. GCM classes still exist in the SDK, and it may continue to work, but have not been tested. We strongly recommend you move to FCM as soon as possible. |
March 2019 improvements – Compatible with 19.1 IBM WCA Release
On March 19th, IBM Mobile Messaging introduces the following improvements.
This release is recommended only for iOS users experiencing these issues. Other users do not need to upgrade to this release.
Improvement | Description |
---|---|
iOS SDK 3.7.1.3.3 |
Bug Fixes:
Improvements:
Our build environment for this release:
|
March 2019 improvements – Compatible with 19.1 WCA Release
On March 8th, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Cordova users, and strongly recommended for Cordova users who defer starting the Android SDK to sometime later than app start.
Improvement | Description |
---|---|
Cordova SDK 3.6.4 |
Bug Fixes:
Improvements:
Our build environment:
|
February 2019 improvements – Compatible with 19.1 IBM WCA Release
On February 27th, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Xamarin users, and strongly recommended for Xamarin users who defer starting the Android SDK to sometime later than app start.
Improvement | Description |
---|---|
Xamarin SDK 3.3.2.4 |
Bug Fixes:
Improvements:
Note: If you use the video functions of inbox and in-app plugins on Android P, you must set an additional attribute on the <application> node in AndroidManifest.xml. See Implementing inbox notifications in mobile apps developed using Xamarin or Implementing in-app messages in mobile apps developed using Xamarin for more details. Our build environment:
Note: The latest version of Xamarin does not build correctly for 32-bit iOS 10 devices. Builds on earlier versions of Xamarin may work. |
February 2019 improvements – Compatible with 19.1 IBM WCA
On February 12th, IBM Mobile Messaging introduces the following improvements. This release is recommended only for users affected by the issues listed.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.14 |
Bug Fixes:
Improvements:
|
January 2019 improvements – Compatible with 19.1 IBM WCA Release
On January 7th, IBM Mobile Messaging introduces the following improvements.
This release is recommended (but not required) for all iOS native users. It is strongly recommended for users of action categories.
Improvement | Description |
---|---|
iOS SDK 3.7.1.3.2 |
Bug Fixes:
Improvements:
Note: Changes in the Notification Service require that you add MceConfig.json to your Notification Service target. See step 5 of Enabling media attachment and multiple action support for more details. If you are using a configuration object rather than MceConfig.json, see step 2 of Initialize the iOS SDK with a NSDictionary object. |
December 2018 improvements – Compatible with 18.4 IBM WCA
On December 20th, IBM Mobile Messaging introduces the following improvements. This release is recommended only for users affected by the issues listed.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.13 |
Bug Fixes:
Improvements:
|
November 2018 improvements – Compatible with 18.4 IBM WCA
On November 15th, IBM Mobile Messaging introduces the following improvements. This release is recommended only for users affected by the issues listed.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.12 |
Bug Fixes:
Improvements:
|
November 2018 improvements – Compatible with 18.4 IBM WCA Release
On November 1st, IBM Mobile Messaging introduces the following improvements. This release is recommended for all Xamarin users, and strongly recommended for Xamarin users who are targeting iOS 12 and/or Android API 26.
Improvement | Description |
---|---|
Xamarin SDK 3.3.2.3 |
Bug Fixes:
Improvements:
|
October 2018 improvements – Compatible with 18.3 WCA Release
On October 25th, IBM Mobile Messaging introduces the following improvements.
This release is recommended for all Cordova users, and strongly recommended for Cordova users who are targeting iOS 12 and/or Android API 26.
Improvement | Description |
---|---|
Cordova SDK 3.6.3 |
Bug Fixes:
Improvements:
|
October 2018 improvements – Compatible with 18.3 IBM WCA Release
On October 23rd, IBM Mobile Messaging introduces the following improvements.
This release is recommended (but not required) for all users, but strongly recommended for users targeting iOS 12.0.1 and higher.
Improvement | Description |
---|---|
iOS SDK 3.7.1.3.1 |
Bug Fixes:
Improvements:
|
October 2018 improvements – Compatible with 18.3 IBM WCA Release
On October 18th, IBM Mobile Messaging introduces the following improvements.
This release is recommended (but not required) for all users.
Improvement | Description |
---|---|
iOS SDK 3.7.1.3.0 |
Bug Fixes:
Improvements:
|
October 2018 improvements – Compatible with 18.3 IBM WCA
On October 11th, IBM Mobile Messaging introduces the following improvements. This release is recommended for all users, and strongly recommended for users targeting API 26 and all users of 3.7.1.2.6 and higher.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.11 |
Bug Fixes:
Improvements:
|
September 2018 improvements – Compatible with 18.2 IBM WCA
On September 14th, IBM Mobile Messaging introduces the following improvements. This release is recommended (but not required) for all users, and strongly recommended for all Kitkat users.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.9 |
Bug Fixes:
Improvements:
|
September 2018 improvements – Compatible with 18.2 IBM WCA Release
On September 12th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Xamarin SDK 3.3.2.2 |
Bug Fixes:
Improvements:
|
August 2018 improvements – Compatible with 18.2 WCA Release
On August 24th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.6.2 |
Bug Fixes:
Improvements:
Note: As of 10 October 2018, Cordova did not yet support Xcode 10. Cordova users should continue to use Xcode 9 and will be unable to make use of iOS 12 features until Cordova adds support. |
August 2018 improvements – Compatible with 18.2 IBM WCA Release
On August 23rd, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Xamarin SDK 3.3.2.1 |
Bug Fixes:
Improvements:
|
August 2018 improvements – Compatible with 18.2 WCA Release
On August 10th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.6.1 |
Bug Fixes:
Improvements:
Note: Cordova 3.6.1 requires changes which prevent it from being used on both GCM and FCM. For that reason, it supports FCM only. Documentation on how to convert back to GCM will be coming soon, but be aware that no testing other than basic push testing has been done on GCM. |
August 2018 improvements – Compatible with 18.2 IBM WCA
On August 7th, IBM Mobile Messaging introduces the following improvements. This release is recommended (but not required) for all users.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.8 |
Bug Fixes:
Improvements:
|
July 2018 improvements – Compatible with 18.2 IBM WCA
On July 5th, IBM Mobile Messaging introduces the following improvements. This release is recommended (but not required) for all users.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.6 |
Bug Fixes:
Improvements:
Note: Android SDK 3.7.1.2.6 has a known defect. If users force close the app, the background service which scans for beacons/geofences will crash and restart. Because it restarts, users will not experience any loss of function. Developers who are using crash reporting frameworks may see this reported. |
Jun 2018 improvements – Compatible with 18.1 IBM WCA Release
On June 26th, IBM Mobile Messaging introduces the following improvements. This release is recommended (but not required) for all users.
Improvement | Description |
---|---|
iOS SDK 3.7.1.2.3 |
Bug Fixes:
Improvements:
|
June 2018 improvements – Compatible with 18.1 IBM WCA
On June 22nd, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.4 |
Bug Fixes:
Improvements:
Note: Android SDK 3.7.1.2.4 has a known defect. If users force close the app, the background service which scans for beacons/geofences will crash and restart. Because it restarts, users will not experience any loss of function. Developers who are using crash reporting frameworks may see this reported. |
June 2018 improvements – Compatible with 18.1 WCA Release
On June 6th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.6.0 |
Bug Fixes:
Improvements:
|
May 31 2018 improvements – Compatible with 18.1 IBM WCA Release
On May 31st, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Xamarin SDK 3.3.2.0 |
Bug Fixes:
Improvements:
|
May 2018 improvements – Compatible with 18.1 IBM WCA
On May 28th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.3 |
Bug Fixes:
Improvements:
Note: Android SDK 3.7.1.2.3 has a known defect. If users force close the app, the background service which scans for beacons/geofences will crash and restart. Because it restarts, users will not experience any loss of function. Developers who are using crash reporting frameworks may see this reported. |
May 2018 improvements – Compatible with 18.1 IBM WCA Release
On May 14th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.1.2.2 |
Bug Fixes:
Improvements:
|
May 2018 improvements – Compatible with 18.1 IBM WCA Release
On May 7th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.7.1.2.1 |
Bug Fixes:
Improvements:
Note: Android SDK 3.7.1.2.1 has a known defect. If users force close the app, the background service which scans for beacons/geofences will crash and restart. Because it restarts, users will not experience any loss of function. Developers who are using crash reporting frameworks may see this reported. |
May 2018 improvements – Compatible with 18.1 IBM WCA Release
On May 1st, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.1.2.1 |
Bug Fixes:
Improvements:
|
April 2018 improvements – Compatible with 18.1 IBM WCA
On April 4th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.7.1.2 |
Bug Fixes:
Improvements:
Note: Android SDK 3.7.1.2 has a known defect. If users force close the app, the background service which scans for beacons/geofences will crash and restart. Because it restarts, users will not experience any loss of function. Developers who are using crash reporting frameworks may see this reported. |
March 2018 improvements – Compatible with 18.1 IBM WCA Release
On March 30th, IBM Mobile Messaging introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.1.2 |
Bug Fixes:
Improvements:
As iOS 9 has less than 5% market share, testing has been on iOS 10 and 11 only. |
March 2018 improvements – Compatible with 18.1 IBM Marketing Cloud Release
On March 7th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.1.1.1 |
Bug Fixes:
Improvements:
|
March 2018 improvements – Compatible with 18.1 IBM Marketing Cloud Release
On March 1st, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.1.1 |
Bug Fixes:
Improvements:
|
February 2018 improvements – Compatible with 18.1 IBM Marketing Cloud Release
On February 28th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.7.1.0.3 |
Bug Fixes:
Improvements:
|
February 2018 improvements – Compatible with 18.1 IBM Marketing Cloud Release
On February 13th, IBM Mobile Push Notification introduces the following improvements.
Note: this version of the SDK introduces changes in AndroidManifest.xml for GCM. The receiver com.ibm.mce.sdk.gcm.GcmBroadcastReceiver is replaced with com.google.android.gms.gcm.GcmReceiver. The service com.ibm.mce.sdk.gcm.GcmIntentService is replaced with com.ibm.mce.sdk.gcm.MceGcmListenerService. For further details, see Configuring Basic Push Services for Android Apps.
Improvement | Description |
---|---|
Android SDK 3.7.1.0.2 |
Bug Fixes:
Improvements:
|
February 2018 improvements – Compatible with 18.1 Watson Campaign Automation
On February 1st, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.7.1.0.1 |
Bug Fixes:
Improvements:
|
January 2018 improvements – Compatible with 18.1 Watson Campaign Automation
On January 26th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Xamarin SDK 3.3.1.0 |
Bug Fixes:
Improvements:
|
January 2018 improvements – Compatible with 18.1 Watson Campaign Automation
On January 23rd, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.5.0 |
Note: Cordova 7.0.0 for Android introduces breaking changes to file path locations. For this SDK release, please use the 6.4.0 Android release of Cordova: cordova platform add android@6.4.0 For iOS, you can use Cordova 7.0.0. Bug Fixes:
Improvements:
|
January 2018 improvements – Compatible with 18.1 Watson Campaign Automation Release
On January 17th, IBM Mobile Push Notification introduces the following improvements.
Note: There have been changes in MceConfig.json; we recommend you take the latest version from the SDK and update it for your app, rather than using an older version.
Improvement | Description |
---|---|
Android SDK 3.7.1.0 |
Bug Fixes:
Improvements:
|
iOS SDK 3.7.1.0 |
Bug Fixes:
Improvements:
|
Additional November 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On November 29th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.7.0.1 |
Bug Fixes:
Improvements:
|
Additional November 2017 improvements – Compatible with 17.3 IBM Watson Campaign Automation Release
On November 16th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.4.3 |
Bug Fixes:
Improvements:
|
Additional November 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On November 1st, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.0.5 |
Bug Fixes:
Improvements:
|
November 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On November 1st, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.0.4 |
Bug Fixes:
Improvements:
|
Additional October 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On October 26th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.4.1 |
Bug Fixes:
Improvements:
|
Xamarin SDK 3.3.0.1 |
Bug Fixes:
Improvements:
|
Additional October 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On October 23rd, IBM Mobile Push Notification introduces the following additional improvements.
Improvement | Description |
---|---|
Android SDK 3.7.0.0.1 |
Bug Fixes:
Improvements:
|
October 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On October 13th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.7.0.3 |
Bug Fixes:
Improvements:
|
Additional September 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On September 29th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS 11 Support |
The 3.7.0.1 release adds support for iOS 11. Note that iOS 11 has some underlying changes which result in different behavior for certain types of messages. Additional details may be found here. |
Support for deferred location initialization |
This release adds support for deferred initialization of the location subsystem on iOS. (Native Android already has this feature.) To use deferred location initialization, set |
iOS SDK 3.7.0.1 |
Bug Fixes:
Improvements:
|
Additional September 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On September 19th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
Deprecation |
With the release of the 3.7.0.0 native SDKs, some Cordova and Xamarin APIs have been deprecated. Alternatives exist that will reduce network traffic and improve customer experience and battery life in most cases. The set user attributes API has been deprecated. Use the update attributes API instead to set values, and the delete attributes API to delete values. The direct clients for attributes and events have been deprecated. Use the queued clients instead, which will retry if server errors occur. The channel attributes API has been deprecated. If you are using channel attributes, please contact support to discuss alternatives. |
---|---|
Cordova 3.4.0 |
Improvements:
|
Xamarin 3.3.0.0 |
Improvements:
|
September 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On September 5th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
Deprecation |
With the 3.7.0.0 release, some APIs have been deprecated. Alternatives exist that will reduce network traffic and improve customer experience and battery life in most cases. The set user attributes API has been deprecated. Use the update attributes API instead to set values, and the delete attributes API to delete values. The direct clients for attributes and events have been deprecated. Use the queued clients instead, which will retry if server errors occur. The channel attributes API has been deprecated. If you are using channel attributes, please contact support to discuss alternatives. |
---|---|
Android SDK 3.7.0.0 |
Bug Fixes:
Improvements:
|
August 2017 improvements – Compatible with 17.3 Watson Campaign Automation Release
On August 30th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
Deprecation |
With the 3.7.0.0 release, some APIs have been deprecated. Alternatives exist that will reduce network traffic and improve customer experience and battery life in most cases. The set user attributes API has been deprecated. Use the update attributes API instead to set values, and the delete attributes API to delete values. The direct clients for attributes and events have been deprecated. Use the queued clients instead, which will retry if server errors occur. The channel attributes API has been deprecated. If you are using channel attributes, please contact support to discuss alternatives. |
---|---|
iOS SDK 3.7.0.0 |
Bug Fixes:
Improvements:
|
July 2017 improvements – Compatible with 17.2 IBM Marketing Cloud Release
On July 26th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.7.0 |
Bug Fixes:
Improvements:
|
Android SDK 3.6.6.3 |
Improvements:
|
Additional June 2017 improvements – Compatible with 17.2 IBM Marketing Cloud Release
On June 27th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.6.1 |
|
Android SDK 3.6.6.2 |
Optimizations:
|
June 2017 improvements – Compatible with 17.2 IBM Marketing Cloud Release
On June5th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.3.1 |
|
May 2017 improvements – Compatible with 17.2 IBM Marketing Cloud Release
On May 22nd and May 24th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Xamarin SDK 3.2.0.0 |
New Features:
Bug fixes:
|
Android SDK 3.6.6.1 |
Bug fixes:
|
May 2017 improvements – Compatible with 17.2 IBM Marketing Cloud Release
On May 16th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.6.0 |
New features:
Bug fixes:
|
Android SDK 3.6.6.0 |
New features:
Bug fixes:
|
April 2017 improvements – Compatible with 17.1 IBM Marketing Cloud Release
On April 28th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.4.3 |
|
April 2017 improvements – Compatible with 17.1 IBM Marketing Cloud Release
On April 21st, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.4.2 |
|
April 2017 improvements – Compatible with 17.1 IBM Marketing Cloud Release
On April 6th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Cordova SDK 3.3.0.1 |
|
March 2017 improvements – Compatible with 17.1 IBM Marketing Cloud Release
On March 7th, IBM Mobile Push Notification introduces the following improvements.
Note: these fixes introduce changes in inbox code due to refactoring.
Improvement | Description |
---|---|
iOS SDK 3.6.4.1 | Bugfix: Resolved issue when sending the same rich message with different personalization values. |
Android SDK 3.6.5.0 |
|
February 2017 improvements – Compatible with 17.1 IBM Marketing Cloud Release
On February 14th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.4.0.1 & Android SDK 3.6.4.0 |
New functionality added to both iOS and Android SDKs
|
Additional Android only improvements |
|
Cordova SDK 3.2.9 | Added iBeacon and Geofence support, iOS 10 general support as well as media attachments. |
November 2016 improvements – Compatible with 16.4 IBM Marketing Cloud Release
On November 10th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.3.1 |
Due to issues during the beta period of iOS 10, our SDK was changed to an Embedded Binary style framework. These issues have now been resolved in the latest Xcode builds, however it turned out that the Embedded Binary style causes some issues when Archiving your build to submit to the app store. We have addressed these issues in the 3.6.3.1 release by switching back to the Static Framework style SDK build process. Please upgrade to this SDK version if you are in the process of submitting a new mobile app to App Store for the first time or publishing an update. |
October 2016 improvements – Compatible with 16.4 IBM Marketing Cloud Release
On October 26th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.3.0 & Android SDK 3.6.3.0 |
Starting with the 3.6.3.0 release, both iOS and Android SDKs can report when users enter and exit geofences that have been configured by the customerâs location admin in the IBM Marketing Cloud (IMC) console/UI. This SDK works with the IMC 16.4 release, and allows marketers to engage with their mobile app users in real-time based on user location. In the iOS 3.6.3.0 SDK, the event management system has been improved as well. |
September 2016 improvements – Compatible with 16.3 IBM Marketing Cloud Release
On September 9th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.2.0 |
This package of IBM Marketing Cloud iOS Mobile Push SDK contains formal iOS 10 notification support. All iOS 10 features described in the August 17th releases notes are available here. This SDK is built with Xcode 8 build 8A218a for the iOS 10 golden master. Developers can use this SDK to publish apps in the App Store in time for September 13th Apple release date. Additional enhancements include support for detecting and correcting accidental appKey misconfiguration in Mobile App, similar to what was introduced in Android SDK 3.6.1.7 in June. Note: IBM Marketing Cloud does not recommend that app developers switch appKey in subsequent publishes once the app has already been published. |
August 2016 improvements – Compatible with 16.3 IBM Marketing Cloud Release
On August 17th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
iOS SDK 3.6.2.0-beta5 |
This beta package of IBM Marketing Cloud iOS Mobile Push SDK contains iOS 10 notification support, media attachment and text entry support as well as updated sample apps to demonstrate iOS 10 usage. Swift sample app changes include updating it to Swift 3.0 syntax. Both standard sample and swift sample apps contain new methods for registering with iOS 10 for APNS. Starting with this release, we will include the Apple watch plugin within the SDK package. This package supports Watch OS 3 beta version. We will follow-up with a formal release of iOS SDK when Apple iOS 10 and Xcode 8 Release Candidate versions are available. Non-iOS 10 enhancements include support for detecting and correcting accidental appKey misconfiguration in Mobile App, similar to what was introduced in Android SDK 3.6.1.7 in June. Note: IBM Marketing Cloud does not recommend that app developers switch appKey in subsequent publishes once the app has already been published. |
More July 2016 improvements – Compatible with 16.3 IBM Marketing Cloud Release
On July 27th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.6.1.9 |
This release of Android Push Notification SDK includes enhancements that allow marketers to exploit new push notification functionality in latest release of Android OS – Android 7.0 Nougat (Android N):
|
Xamarin Forms SDK 3.0.0.0 |
|
July 2016 improvements – Compatible with latest 16.2 IBM Marketing Cloud Release
On July 5th, IBM Mobile Push Notification introduces the following improvements.
Improvement | Description |
---|---|
Android SDK 3.6.1.8 |
|
June 2016 improvements – Compatible with latest 16.2 IBM Marketing Cloud Release
On June 28th, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Android SDK 3.6.1.7 |
|
April 2016 improvements – Compatible with 16.1 and 16.2 IBM Marketing Cloud Releases
On April 22nd, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Android SDK 3.6.1.6 & iOS SDK 3.6.1.3 & Cordova SDK 3.2.7 |
UI support for these templates will be included in the upcoming IBM Marketing Cloud 16.2, where they will become part of the default templates dropdown menu. Until then, the templates can still be used with some configuration of Templates under the Development menu in the Marketing Cloud UI. |
iOS SDK 3.6.1.3 |
|
Android SDK 3.6.1.6 |
|
Windows SDK 3.1.1.0 |
|
Cordova SDK 3.2.7 |
|
February 2016 improvements – Compatible with 16.1 IBM Marketing Cloud Release
On February 15th, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
iOS SDK 3.6.0.13 |
Bug fix : Fixed first launch isPushEnabled/isPushDisabled event sending. |
Android SDK 3.6.0.11 |
Bug fixes: Logging system crash fix as well as Dial action failure on Android M fix. |
Cordova SDK 3.1.11 |
|
January 2016 improvements – Compatible with 16.1 IBM Marketing Cloud Release
On Jaunary 15th, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Windows 10 SDK 3.0.0.0 |
Starting with IBM Marketing Cloud release 16.1, we now provide API support for a new platform for Push Notification – Windows 10. (Support in the UI will come in a future release.) You will find a brand new Windows 3.0.0.0 SDK on our Download page. It allows you to send Simple Push Notifications at this time, with Inbox and In-App support coming in future releases. This SDK includes much of the functionality that already exists in iOS and Android platforms such as:
|
Cordova SDK 3.1.9 |
Replaced iOS SDK with 3.6.0.12 and Android SDK with 3.6.0.8. Added support for Calendar, Snooze and Display Web Plugins. Modularized Inbox and In-app plugins |
Apple Watch Plugin 1.0.5 |
This release for the Apple Watch Plugin in the IBM Marketing Cloud provides improvements such as:
|
December 2015 improvements – Compatible with 15.3 IBM Marketing Cloud Release
On Dec 15th, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Android SDK 3.6.0.9 |
Android L notifications support – The SDK now supports “heads up” notifications (notifications can be marked as high priority which causes them to pop of the top of the screen when they arrive) and sensitive notifications (notification can be marked as sensitive and will not be shown on the lock screen if the user defined that sensitive notifications will not be displayed on the lock screen). Custom Chrome tabs – The open URL action uses a custom Chrome tab (if it is supported, such as in Android M) instead of opening the Chrome application with the URL. Session tracking improvements. The session tracking service is now scheduled when the application is sent to the background, and will activate after session timeout +1 minutes. When activated, it checks if the current session has timed out. If so, it sends a session timeout event. The session tracking service is disabled when the application is brought to the foreground. Previously, the session tracking service ran without regard to foreground/background status. Because in Android M services can be stopped by the OS, we ensure all the services are up every time the application is sent to the foreground. Defining baseUrl in the SDK config file is no longer mandatory. If it is not defined, the US production server URL is used by default. If you are provisioned with a non-US Engage POD, please work with Customer Support to determine the correct baseUrl setting for your application. Bug fixes: – The inbox subject text is now expanded when the text is too long to be displayed in one line instead of being cut off. |
On Dec 4th, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
iOS SDK 3.6.0.12 |
This SDK has improved Singleton Superclass locking |
November 2015 improvements – Compatible with 15.3 IBM Marketing Cloud Release
On Nov 16th, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
iOS SDK 3.6.0.11 |
The new iOS 3.6.0.11 package adds Swift support to the SDK, along with a new Swift sample app. It also adds support for detecting device form factor and carrier, and better support for detecting device model. We also fixed a defect with detecting development or production configuration. Now development and production certificates are both recognized. Finally, we added the -fembed-bitcode flag for additional bitcode support. |
Cordova Plugin 3.1.7 |
The new iOS SDK 3.6.0.11 package is now included in Cordova Plugin 3.1.7 |
October 2015 improvements – Compatible with 15.3 IBM Marketing Cloud Release
On October 10th, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Note for Android 3.6.0.6 SDK |
From this release onward, the interval of the session tracking service will default to 20 minutes. Also, session tracking service enabling control is included in this SDK publish. The tracking service will be started only if session tracking is enabled and the service is defined in the manifest. |
Cordova plug-in 3.1.4 support for inbox and in-app messages | The Apache Cordova plug-in and its sample app now include support for inbox and in-app messages. |
September 2015 improvements – 15.3 IBM Marketing Cloud Release
On September 26, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Note for Android 3.6.0.5 SDK |
For this release, the sample app Manifest file is missing the following definition. Add the following to your Android Manifest file to prevent battery drain. <service android:name=”com.ibm.mce.sdk.alarm.SessionTrackingIntentService” /> |
iOS native static framework | The iOS native framework is no longer a dynamic/embedded binary framework as this caused problems with various versions of iOS. It has been replaced with a static framework style. This also means that the framework should no longer be added to the embedded binaries section of the project, but instead added to the normal linked frameworks section. |
Support for inbox and in-app messages for iOS and Android devices | The iOS and Android SDKs now support receiving inbox messages (attached to simple messages or inbox-only) and in-app messages. The sample app demonstrates example use. This version of the Cordova plug-in does not include the sample code and plug-ins for actions such as Add to Calendar, Snooze, or Display Web. These are supported in the native SDK, and it does not prevent you from writing code to handle these. |
MceConfig.plist file format changed for iOS and Android | The file format for MceConfig.plist was changed to MCEConfig.json. |
Unified inbox support for iOS and Android | Unified inbox allows an inbox to be shared across devices. Changes a mobile app user makes to the inbox on one device are synced with the inbox on other devices with the same user and application. |
Objective-C, Java, and JavaScript API updates | The Objective-C, Java, and JavaScript APIs have been updated to support in-app and inbox messages. |
Migration support for IBM Mobile Push Notification platform | The back-end system can disable IBM Mobile Push Notification XIDs when the same device registers with the IBM Marketing Cloud. Consult the Support team for more details. |
Updated calendar plug-in for iOS | The calendar plug-in for iOS was updated to include interactive = true or false in the payload. |
Exposed logging for developers for Android | You can add log level message types to MceConfig.json to produce additional logging. This may help you debug issues with registration and mobile app messages. |
Automatic plug-in detection for Android | Plug-ins can now be detected automatically. They are configured by using a common JSON configuration file. |
Xcode7 and iOS9 support | The iOS SDK is built with Xcode7 and bitcode enabled. iOS SDK 3.6.0.8 supports iOS7, iOS8, and iOS9 with this SDK. |
September 2015 improvements
On September 1, IBM Mobile Push Notification introduces the following bug fixes:
- Added NaN (Not a Number) checks to session length calculations
- Added JSON object validation prior to creating JSON data
May 2015 improvements
On May 29, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Apache Cordova plug-in and sample app | You can use the Apache Cordova plug-in and sample app with your hybrid apps. The iOS and Android SDKs support the Cordova plug-in. |
Support for userId/channelId merged results | The server automatically checks to see whether the userId/channelId for each of your app users has changed. If it has, the results are merged through the server and stored in one record. |
IBM MobileFirstâą Platform Foundation support | You can use the 3.x SDKs with your IBM MobileFirst Platform Foundation 6.3 and 7.0 projects. |
Log level messages types for iOS | You can add log level message types to the MceConfig.plist file to help you debug output messages. |
Action plug-ins support for iOS and Android | You can add action plug-ins to your iOS and Android apps to enhance your push notifications. Plug-ins for iOS include Add to Calendar, Add to Passbook, and Snooze. Plug-ins for Android include Add to Calendar, Snooze, and Display Web. |
Custom expandable notifications for Android | You can use custom expandable notifications to customize the layout of your push notification to include large text sizes, image support, and up to three elements for expandable notifications. |
Objective-C, Java, and JavaScript API support | API documentation for Objective-C, Java, and JavaScript APIs is available. |
Xcode 6 framework | The iOS SDK is compatible with Xcode 6.3. This framework is newer than the older, prelinked style framework and takes less space in the application. |
CocoaPod support | You can use CocoaPod for a simpler way to install iOS frameworks into your app. For more information, see https://cocoapods.org/. |
Sample app enhancements | The sample app has an updated user interface and improved handling of crashes for smaller devices and rotation. |
Auto detect appKey environment | The MceConfig.plist file includes both types of app keys: devAppKey and prodAppKey. You can include both app keys so you can run your app from Xcode to the device in development mode and from the App Store or an ad hoc build in production mode. |
Additions to the attributes and events API in the Android SDK | You can determine whether your attribute and event operations are successful. You can perform attribute and event operations and receive the response through a callback. You can also receive attribute and event offline operation results through the SDK broadcast events. |
February 2015 improvements
On February 20, IBM Mobile Push Notification introduces the following improvements.
Enhancement | Description |
---|---|
Push notification capabilities in Silverpop EngageÂź | You can use the push notification capabilities that are provided by within Silverpop Engage to configure your apps and the actions that are associated with them within Engage by using either the iOS SDK or the Android SDK. |
iOS SDK Android SDK |
The SDKs are improved to work with Silverpop Engage, and support the following features:
You cannot receive a notification without being registered with Google Cloud Messaging (GCM); however, you can be registered with the Mobile Customer Engagement server and set attributes and send events. The IBMÂź Push Notification SDK for Android supports mobile devices that do not work with GCM. You can use all the features, except for push notifications. |
Custom actions | You can plug in to action handling by registering your own actions, or custom actions. Custom actions methods are defined by the developer and run when an action is selected by the user with the registered type value. |
Migration of documentation to Knowledge Center | You can use Knowledge Center to perform any of the following actions:
|
Go Back to the Mobile App Messaging home page.
is there a way to subscribe to the SDK release notes / Updates to receive these as an email?
Hi Michael,
Yes – depending on what you want to do, check the following checkboxes at the bottom of the page:
Notify me of follow-up comments by email.
Notify me of new posts by email.
Subscribe
Subscribed.
Subscribed
… [Trackback]
[…] Informations on that Topic: developer.ibm.com/customer-engagement/2017/06/05/5864-2/ […]