More than one Beacon Proximity UUID and map view improvements – Release Notes September 19, 2017

During the last few weeks we made some improvements to our dashboard and to our libraries. Here is a short overview.

We now have added support for entering additional proximity UUIDs in the dashboard, instead of just one. When creating and updating a beacon you can select which UUID a beacon should use. If you’re the owner of a fleet of beacons, I recommend picking a single UUID for all your beacons. However, if you want to use a beacon fleet of somebody else as well, then using more than one UUIDs makes sense.

A couple improvements were made to our dashboard related to managing locations. We renamed the regions tab to the more intuitive name of “locations”. When you load that tab, the map will now zoom in to your geofences, instead of showing the whole world. If you decide to switch to the list view, it will remember this for the next time you visit the location tab. The next time it will straight open the list view again, instead of the map view.

To make the integration of the Android library easier, we changed the packaging of our library a bit. The library package is now configured to automatically pick up Google Play Services as a transitive dependency. You can no longer forget to add this dependency anymore. Look at the first step of our integration guide to see how it works now.

Both our plugins now allow collecting attribution events. Both the iOS and Android API have methods for this. Do you have events in your app and want to relate those to notification events or geotrigger events, then contact your customer success manager. We’ll be soon offering options to manage those straight from the dashboard.

We made it easier to prime your users before asking for the location services opt-in. This change is applied for iOS and Android. Especially for iOS 11, where the user gets the option to select When in Use, it is essential to do this. You can read more in Getting Your Users Ready to Opt-in for Location Permissions.

The iOS plugin is upgraded to make use of the User Notifications framework. This allows you to make use of the new notification functionality that is introduced in iOS 10 and extended in iOS 11. When targeting iOS 11, the old notification functionality is removed, thus upgrading to version 2.x of our plugin is required. You can read more about it in Migrating from UILocalNotification to iOS 10.


Spread the love