Last modified November 12, 2019 by Shelly Wolfe

Geo SDK release notes

Request a copy of the Swrve Geo Sample project for your app platform from your CSM at support@swrve.com. They will enable Geoplaces in your Swrve dashboard and give you your Geo API key.

For upgrade instructions, see the Geo SDK upgrade guide.

Release 2.3.1 (iOS)

Release date: November 12, 2019

Features

  • Added support for Bluedot SDK 15.1.2 (iOS 13, Xcode 11, Swift 5).

Release 2.3.1 (iOS)

Release date: August 29, 2019

Features

  • Added support for Bluedot SDK version 15.0.0.

Fixes

  • Fixed an issue with restarting the SDK on apps that have data protection enabled and delayed start of the Geo SDK plugin in their configuration.

Release 2.3

Release date: August 1, 2019

The Swrve Geo SDK 2.3 has a hard dependency on the native Swrve SDK version 6.2.

Features

  • Added support for configuring cooldown periods at app-wide, individual geoplace, and campaign levels. QA users can bypass the cooldown period using the Reset device state checkbox in the QA device settings screen. For more information, see About geoplaces.
  • Added support for configuring geoplace opening hours. For more information, see About geoplaces.

Fixes

  • iOS: Fixed offline notification processing.

Release 2.2.1

Release date: May 15, 2019

Features

  • iOS: Recompiled the iOS Swrve Geo SDK to add support for XCode 10.2 and Bluedot SDK version 1.13.3. This release does not include any other fixes or features. Only upgrade to this version if you’re using XCode 10.2+.

Release 2.2

Release date: April 8, 2019

The Swrve Geo SDK 2.2 has a hard dependency on the native Swrve SDK version 6.1.

Features

  • Added support for triggering and displaying geo notifications when a device is offline.

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.