Places and Places Monitor Extensions
Places Service
PlacesMonitor 2.2.1
Android
PlacesMonitor 2.1.3
iOS
ACPPlaces 1.3.1 (iOS)
Places 1.4.1 (Android)
PlacesMonitor 2.2.0
Android
Places 1.4.0
Android
setAuthorizationStatus
, to set the device authorization status for Places Services. The value is stored and used in the Places shared state.PlacesMonitor 2.1.2
iOS
ACPPlaces 1.3.0
iOS
setAuthorizationStatus
, to set the device authorization status for Places Services. The value is stored and used in the Places shared state.PlacesMonitor 2.1.1
iOS
PlacesMonitor 2.1.1
Android
PlacesMonitor 2.1.0
iOS
setRequestAuthorizationLevel
, to set the type of location authorization request for which the user will be prompted.Android
setLocationPermission
, to set the type of location permission request for which the user will be prompted.The following updates were made in this release:
Here is a list of the updates to the Places UI:
The following updates were made in this release:
The following updates were made in this release:
Monitoring status is now persisted between launches.
The handling of the callback, which resulted from a location permission request no longer requires you to extend PlacesActivity.
Changed an existing API, allowing developers to clear all Places data from the device:
Old API: public static void stop();
New API: public static void stop (final boolean clearData);
Updated the use of the getNearbyPointsOfInterest
API to handle error scenarios more effectively.
The following updates were made in this release:
To clear all Places data from the device,
in ACPPlacesMonitor, replaced an existing API + (void) stop;
with+ (void) stop: (BOOL) clearData;
.
Updated the use of the ACPPlaces getNearbyPointsOfInterest
API to handle error scenarios more effectively.
The following updates were made in this release:
getNearbyPointsOfInterest
callback was returning error code SERVER_RESPONSE_ERROR instead of CONNECTIVITY_ERROR
on no internet.getNearbyPointsOfInterest
API (without the errorCallback) will have the successCallback
called with empty poi list, in case of error retrieving the nearby points of interest.The following updates were made in this release:
iOS Places 1.2.0
Added a new API that clears out all Places-related data from shared state, in-app memory, and NSUserDefaults
.
The following updates were made in this release:
iOS Places Monitor 1.0.2
The following updates were made in this release:
iOS Places 1.1.0
Android Places Monitor 1.0.1
Fixed the following issues in the Places UI:
The following updates were made in this release:
Android Places 1.2.0
Android Places Monitor 1.0.0
Initial release of the Places Monitor for Android.
The Places Monitor manages the OS-level Location APIs and communicates directly with the Places extension. With both extensions installed, customers can have out-of-the-box region monitoring in their application.
For more information about the Places Monitor, click here.
Android Places 1.1.0
The following updates were made in this release:
iOS Places Monitor 1.0.1
iOS Places Monitor 1.0.0
Initial release of the Places Monitor for iOS.
The Places Monitor manages the OS-level Location APIs and communicates directly with the Places extension. With both extensions installed, customers can have out-of-the-box region monitoring in their application.
This is the first release of Places Service, a set of tools that allows customers to enrich their users’ experiences with real world location data. For the first release, our primary use case is to enable mobile apps to retrieve custom location data and act on that data through Adobe Experience Platform Launch.
Here are the key features in this release:
We have released a management UI where you can view and manage your points of interest (POIs). You also can organize your POIs into libraries. In addition to standard metadata such as city, state, and category, we also support the ability to add custom metadata to your POIs.
Using the Places Extension, you can add your Places Service libraries to your mobile app and act on their POIs. Using the rule builder in Experience Platform Launch, you can trigger actions to fire when users enter and exit POIs.
In the Places extension:
For more information about the Places extension, see Places extension.
You can use the Places APIs to do the following:
Allow developers to populate and update their list of POIs.
Build your own UI or integrate with an existing POI database.
Use the Places API batch endpoints to do a bulk import of POIs.
You can use the provided Python utility to complete the bulk import.
For more information about the Places APIs, see Web service API.
The Analytics extension is being updated to automatically add location context data from your Places Service database to all outgoing Analytics calls when a user is in a POI (Passive calls). This update will also allow rule creation to fire Analytics track calls directly at POI entry or exit (Active calls).