Last modified September 21, 2018 by Gordon Glauser

Android SDK Release Notes

Swrve has an open source SDK repository. There are two options for downloading the latest public Swrve Android SDK:

  • Download the SDK from the GitHub public repository.
  • Integrate the SDK libraries using Maven from the Swrve repository on Jcenter. To integrate this library with your project, add the following code to your build.gradle file:
    1. First, add the Swrve repository:
    2. Then, select a Swrve library to install, ensuring you include the latest SDK version number: 5.3.2
      Basic Android SDK

      Firebase-flavored SDK – select if you’re using any Firebase services, such as IAP or Firebase Cloud Messaging

      Google-flavored SDK – select if you’re using any of Google Play’s services, such as IAP or Google Cloud Messaging

      Amazon-flavored SDK – select if you’re using Amazon Device Messaging

For upgrade instructions, see Android SDK Upgrade Guide. To view the feature support matrix, see SDK Feature Support Matrix.


Release 5.3.2

Release Date: September 21, 2018

Fixes:

  • Fixed an issue that occurred when rendering notifications without expandable text. The SDK was setting the BigText style even though it was not needed, resulting in bad rendering on Android 6.X devices.

Release 5.3.1

Release Date: September 17, 2018

Fixes:

  • Fixed an issue where the SDK delivered an empty payload to SwrveNotificationListener. Thanks to Cameron Rattray for your contribution!

Release 5.3

Release Date: September 3, 2018

Warnings:

  • In line with Google’s decision to deprecate Google Cloud Messaging and remove support for it in April 2019, we have deprecated the swrve-google flavor of the SDK and you should migrate to the swrve-firebase SDK. We will discontinue support for for the swrve-google flavor of the SDK in version 6.0 later this year. If you have any questions about migrating from Google Cloud Messaging to Firebase Cloud Messaging, contact your Customer Success Manager at support@swrve.com.

Features:

  • Added support for displaying a Swrve in-app message or Conversation campaign directly after a customer engages with a push notification. For more information, see Linking push notifications to in-app campaigns.
  • Added support for the release of Swrve Geo SDK add-on v2.0. This includes a new workflow for setting up your geo-triggered campaigns. For more information, see Creating geo-triggered campaigns.
  • Updated and revamped the Swrve sample projects in GitHub, including a new MinimalIntegration project. Also improved the integration with multiple push provider samples (for more information, see MultipleFCMProviders samples).
  • Various refactors and improvements to how Notifications are built.
  • Upgraded the following build tools and services:
    • Gradle build tool – from 4.1 to 4.4
    • Gradle Android tools – from 3.0.1 to 3.2.1
    • google-services – from 3.1.0 to 3.2.1
    • play-services-ads – from 11.8.0 to 15.0.1
    • play-services-gcm – from 11.8.0 to 15.0.1
    • firebase-messaging – from 11.8.0 to 17.1.0 (Note: This upgrade means SwrveFirebaseInstanceIdService is now deprecated. It is no longer required and the upgrade is simply to remove it from manifest.)
  • Added new SwrveNotificationConfig object that you should use to configure global settings for notifications (icons, title and accent color) instead of configuring via meta-data tags in AndroidManifest.xml. We will remove support for configuring via AndroidManifest.xml in version 6.0 later this year. For more information, see SwrveConfig for adding SwrveNotificationConfig in the Android Integration guide.
  • Deprecated SwrveSDK.setPushNotificationListener() and will remove it in version 6.0 later this year. Instead, configure the push notification listener via SwrveConfig.

Fixes:

  • Fixed an issue that prevented Javadocs from being displayed in Android Studio.
  • Fixed a rare issue that caused event duplication.
  • Fixed a rare issue with push notification titles where if the title was left blank when creating the notification in Swrve, the title of the previous notification the device received was used.

Release 5.2

Release Date: March 5, 2018

Features:

  • Added support for OTT platforms. You can now integrate the Swrve SDK into Android TV or Amazon Fire TV to do tracking, resource A/B testing and in-app messages. Conversations and push notifications are not currently supported. For more information, see Swrve OTT Integrations.

Fixes:

  • Fixed an issue related to Android Oreo API 26 that caused in-app messages and Conversations to crash if the target SDK version was 27 (Fix for error in version 5.1.1). For information on the status of this issue, see the Google Issue Tracker.

Release 5.1.1

Release Date: January 15, 2018

Features:

  • Updated the Swrve SDK Multiple GCM Providers Sample project to make it compatible with Android O. For more information, see the  Android SDK Samples folder on GitHub.
  • Added an API for disabling Logcat logging that was removed in 5.0. You can disable logging via the SwrveConfig. For more information, see How Do I Configure SDK Device Logging?

Fixes:

  • Fixed an issue with rich push notification button actions where the notification drawer would not close if the button action was dismiss or a deeplink.
  • Fixed an issue related to Android Oreo API 26 that caused in-app messages and Conversations to crash if the target SDK version was 27. Thanks to GitHub user Dimezis for your contribution!

Release 5.1

Release Date: December 12, 2017

Features:

  • Includes updates required for Locations SDK 2.0. For more information, see the Locations SDK Release Notes.
  • Upgraded the SDK source libraries to compile with Gradle 4.1 and Android Studio 3.0.
  • Upgraded Google Play Services to 11.6.0 and support library tools to 27.0.2.

Release 5.0

Release Date: November 16, 2017

Features:

  • Includes refactors and code improvements for easier integration and to safely persist data per User ID. For more information, see the Android SDK 5.0 Upgrade Guide.
  • SDK activity tracking is now automatic and the SwrveSDK lifecycle (SwrveSDK.onCreate, and so forth) code is no longer needed. As a result, it is now necessary to pass the Application object into the createInstance method. For more information, see the Android SDK 5.0 Upgrade Guide.
  • Added support for nested push notification payload JSON.
  • You can now configure a device model blacklist in SwrveConfig to prohibit the SDK starting on particular device models. Defaults to “Calypso AppCrawler”.

Fixes:

  • It is no longer possible to use internal Swrve.* events to trigger in-app messages or conversations.

Release 4.11.3

Release Date: October 16, 2017

Fixes:

  • Fixed an issue relating to ProGuard rules that was causing a potential crash when using rich push notifications.

Release 4.11.2

Release Date: September 20, 2017

Features:

  • Updated GCM and FCM libraries to 11.2.0.
  • Added the ability to get the resource key set from a SwrveResource.
  • It is now possible to create Android O channels from the push notification payload.

Release 4.11.1

Release Date: August 28, 2017

Fixes:

  • Fixed a dependency issue with the Timber library.

Release 4.11

Release Date: August 16, 2017

Features:


Release 4.10.1

Release Date: Jun 7, 2017

Fixes:

  • Fixed an issue where if a push notification accent color wasn’t set, the notification wouldn’t show.

Release 4.10

Release Date: May 24, 2017

Features:

  • Added support for using silent push notifications to send background app content updates, for both Google and Amazon flavors.

Release 4.9

Release Date: March 21, 2017

Features:

  • The minimum API Level supported by the Swrve SDK has changed from 10 to 14. The Swrve SDK will not execute on an Android API Level lower than 14.
  • Upgraded the following tools and libraries:
    • Android Gradle tools – from 2.1.3 to 2.2.3
    • Android build tools – from 23.0.3 to 25.0.2
    • Android support jars – from 23.4.+ to 25.1+
    • Google GCM library – from 9.8.0 to 10.0.1
  • The Google Play Services version is no longer required in AndroidManifest.
  • The source code for the Amazon SDK now includes a stubbed amazon-device-messaging jar for compilation purposes.
  • Asset downloading for image and font now supports gzip.
  • It is now possible to lock Conversations orientation via the SwrveConfig.
  • User’s notification permission and importance level are now tracked automatically as user properties.
  • Upgraded open source tests to use the Robolectric version 3.2.2.

Fixes:

  • The Conversations event queue is now flushed upon page transition and onPause.
  • Fixed an issue to ensure Conversations with unknown content are not displayed.

Release 4.8

Release Date: February 2, 2017

Features:

  • Conversations now include support for uploading custom or brand-specific fonts and using advanced text styling and spacing options.

Fixes:

  • Fixed alignment and touch appearance of Conversations star rating icons.
  • Fixed styling of Conversations option buttons.

Previous Releases Summary

  • November 24, 2016 – v4.7 – Added support for Amazon Device Messaging, for using date-type user properties to target your campaign audiences and for sending your own push engagement event.
  • November 7, 2016 – v4.6.2 – Bug fixes.
  • September 12, 2016 – v4.6.1 – Bug fixes.
  • August 31, 2016 – v4.6 – SDK now uses HTTPS by default for all endpoints.
  • July 5, 2016 – v4.5 – Conversations enhancements.
  • May 25, 2016 – v4.4 – Added support for using event payload conditions to trigger in-app messages and Conversations campaigns.
  • May 9, 2016 – v4.3.1 –  Added dependancy to Locations SDK v1.1 on Swrve iOS SDK v4.3.1 or higher.
  • April 7, 2016 – v4.3 – Added Star Rating survey template to Conversations.
  • February 11, 2016 – v4.2 – Added Message Center API and updated Google Cloud Messaging libraries.
  • November 30, 2015 – v4.1 – Restricted use of Swrve. namespace for custom events.
  • November 5, 2015 – v4.0.5 – Updated Google Cloud Messaging libraries.
  • October 21, 2015 – v4.0.4 – Bug fixes.
  • October 15, 2015 – v4.0.3 – Added compatibility with Android Marshmallow.
  • September 23, 2015 – v4.0.2 – Updated push notification plugin to latest GCM library and increased HTTP default timeout.
  • August 18, 2015 – v4.0.1 – Bug fixes.
  • July 7, 2015 – v4.0 – Added support for Conversations and moved from JAR to AAR distribution.
  • April 8, 2015 – v3.4 – Changed default background for in-app messages from solid black to transparent.
  • January 21, 2015 – v3.3.1 – Added support to automatically capture and send referrer information.
  • November 11, 2014 – v3.3 – Added support to log carrier information by default.
  • October 21, 2014 – v3.2 – Added support to generate a random UUID if no custom user ID is provided at initialization.
  • July 30, 2014 – v3.1 – Simplified Google Cloud Messaging push notification integration and added support for triggering in-app messages at session start.
  • May 27, 2014 – v3.0.1 – Bug fixes.
  • May 15, 2014 – v3.0 – Enhancements to real-time targeting and added separate JAR files for Google Play-flavored SDK.
  • April 3, 2014 – v2.10.1 – Bug fixes.
  • April 1, 2014 – v2.10 – Simplified in-app message actions and QA device registration.
  • March 4, 2014 – v2.9 – Added support for push notifications for Android devices.
  • v2.8 – Added support for Swrve’s redesigned in-app messaging functionality and push notifications Beta.
  • v2.7.1 – Bug fixes.
  • v2.7 – Added support for auto-generation of user IDs and unified the in-app messaging and analytics SDKs.
  • November 12, 2013 – v2.6 – Added support for extended IAP event and bug fixes.
  • October 16, 2013 – v2.5 – Added support for in-app messaging per campaign dismissal rules and bug fixes.
  • September 17, 2013 – v2.4 – Added support for in-app messaging QA logging.
  • August 20, 2013 – v2.3 – Added support for in-app messaging QA user functionality.
  • July 26, 2013 – v2.2 – Bug fixes.
  • July 2, 2013 – v.2.1 – Added support for app store filtering within in-app messaging.
  • May 22, 2013 – v.2.01 – Fixed possible crash while displaying messages whose images were not fully downloaded.
  • May 17, 2013 – First public release.