For upgrade instructions, see the Geo SDK upgrade guide.

Release 2.1.1

Release date: February 11, 2019

Fixes

• Fixed an issue where certain device properties were being sent as user property updates every time the Geo SDK initialized.

Release 2.1

Release date: January 31, 2019

The Swrve Geo SDK 2.1 has a hard dependency on the native Swrve SDK version 6.0.1 and supports Bluedot SDK version 1.13.1.

Features

• Added support for Bluedot SDK 1.13.1, which includes the following improvements:
  • Android: No longer requires persistent foreground notification on Oreo+, allowing for deprecation of the existing SwrveGeoSDK.init method that took a Notification object. The Bluedot SDK no longer displays an alarm clock icon and Bluetooth permissions are now optional.
  • iOS: Improvements for restarting the SwrveGeoSDK after a device is rebooted or force closed.
• Added a new API for delaying the very first start of the SwrveGeoSDK to allow for requesting a user’s permission to use location services at an opportune time.
• Improved the background operation of requesting notifications.
• Android: Added maxDisplayWindowMinutes geo config property that prevents a notification showing if the time between the entry or exit of a geoplace and the triggering of the notification is greater than this value. This can happen due to restrictions on Android O+.

Fixes

• Android: Fixed an issue in the SwrveGeoSDK where notifications were requested with an invalid install date parameter.

Release 2.0.1

Release date: September 10, 2018

Fixes

• Android: Fixed an issue that caused geo notification campaigns configured with a geoplace enter event to be displayed when a user exited a geoplace.

Release 2.0

Release date: September 3, 2018

The Swrve Geo SDK 2.0 has a hard dependency on the native Swrve SDK version 5.3 and supports Bluedot SDK version 1.12.1.

Features

• Added support for creating geo-triggered notification campaigns in the Swrve dashboard. Swrve geo-triggered campaigns use local rich notifications and do not require a push token. For more information, see Creating geo-triggered campaigns.
• Added custom filtering of notifications to enable your app to modify the content of a notification or perform a final check and approval before displaying a notification. For more information, see CustomFilter in SwrveGeoConfig.
• Added custom properties to geoplace settings that you can later use to include the property values in your geo-tiggered campaign notification content. For example, you might want to include custom properties such as a location name or deeplink: “Welcome to ${geoplace.restaurantname|fallback=”our”} restaurant!”
• Added QA user logging for debugging geoplaces.
• Removed the username parameter from the SwrveGeoSDK initialization methods.