On August 31, 2021, the Places Monitor extension for the Adobe Experience Platform Mobile SDKs will be deprecated. The Places Monitor extension will not receive further updates or support beyond August 31st.
Customers that currently use the Places Monitor extension can continue usage of this extension with the understanding that no additional updates or support will be available through Adobe.
The deprecation of the Places Monitor extension has no bearing or negative impact on the Places Service extension which will continue to be supported with enhancements and updates.
Customers that are looking to transition away from the Places Monitor extension to their own monitoring solution should review the documentation for: Use Places Service with your own monitoring solution. This document explains how to interact with the Places Service by implementing Core Location services on iOS or Location Services from Google Play.
Table of Contents
- About this project
- Current version
- Contributing to the project
- Environment setup
- Tips for Location testing on Android
- Licensing
The Places Monitor for Android is used to manage the integration between Android's Geo Location services and the Android Places extension for the Adobe Experience Platform SDK.
Integrate the Places Monitor into your app by including the following in your gradle file's dependencies:
implementation 'com.adobe.marketing.mobile:places-monitor:2.+'
Adobe is not currently accepting external contributions for this project, as it is still in the process of being fully set up. It is our desire to open this project to external contributions in the near future.
We look forward to working with you!
Android Studio 3.4 or newer is required to open this project. If necessary, please update here.
In Android Studio, open the code/build.gradle file
To improve user experience, Android 8.0 (Oreo - API level 26) imposes background execution limits, a mechanism which limits certain behaviors by apps that are not running in the foreground (for more information, read the Android documentation here). The result of this is a considerably lower chance of triggering a location update while testing a backgrounded app on an emulator. One way of making sure you get a location update / Geofence trigger while your app is in the background is by opening the Google maps app in the emulator and start faking the location. This usually results in a geofence event being triggered within a few seconds.
-
In Android Nougat and other previous versions, users must both give permission for an app to receive Location updates and enable Google Play's Location Services. The easiest way to do this is by opening the "Google Map" app and then granting the permission for google services thorough that app.
-
If you are running in an Android Emulator older than API 24, there is a chance that the Google Play Services for providing location is not updated. In such case you will be presented with the prompt to update Google Play Services within your application.
This project is licensed under the Apache V2 License. See LICENSE for more information.