Skip to content
Android Places monitor extension
Java
Branch: dev
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci rename variable Jul 17, 2019
.github
code
.gitignore
CHANGELOG
CODE_OF_CONDUCT.md
LICENSE -initial commit of android places monitor May 2, 2019
README.md

README.md

Getting started with the Places Monitor for Android

Table of Contents

  1. About this project
  2. Current version
  3. Contributing to the project
  4. Environment setup
  5. Tips for Location testing on Android
  6. Licensing

About this project

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.

Current version

Maven Central CircleCI

Integrate the Places Monitor into your app by including the following in your gradle file's dependencies:

implementation 'com.adobe.marketing.mobile:places-monitor:1.+'

Contributing to the project

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!

Environment setup

Android Studio 3.4 or newer is required to open this project. If necessary, please update here.

Open the Android Studio project

In Android Studio, open the code/build.gradle file

Tips for Location testing on Android

Running the app on Android API 26 and above

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.

Running the app on Android API 25 and below

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

Licensing

This project is licensed under the Apache V2 License. See LICENSE for more information.

You can’t perform that action at this time.