Last modified September 10, 2018 by Shelly Wolfe

Geo SDK release notes

Request a copy of the Swrve Geo Sample project for your app platform from your Customer Success Manager at They will enable Geoplaces in your Swrve dashboard and give you your Geo API key and username.

For upgrade instructions, see the Geo SDK Upgrade Guide.

Release 2.0.1

Release Date: September 10, 2018


  • 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.


  • 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.