Location

Location Assembler contains the Rover SDK subsystems for Geofence, Beacon, and location tracking.

It can automatically use the Google Location services, which you can opt out of by passing false to the following boolean parameters. You may wish to do this if you want to use a Location SDK from a vendor other than Google, integrate with your own location implementation, or do not require the functionality.

Note: if you use any of the functionality, then you must complete the Google Play Services setup as per FCM Setup section of the SDK documentation (which is also needed for the Notifications module).

Assembler

Rover.initialize(
    // ...,
    LocationAssembler(
        automaticGeofenceMonitoring = true,
        automaticBeaconMonitoring = true,
        automaticLocationTracking = true
    )
)

automaticGeofenceMonitoring: Boolean

(Optional) Automatically use the Google Location Geofence API to monitor for geofence events. Default true.

Note: because of a fixed limit of geofences that may be monitored with the Google Geofence API, this may introduce conflicts with your own code. In that case, see below.

Set to false if you do not want Rover to provide this functionality.

automaticBeaconMonitoring: Boolean

(Optional) Automatically use the Google Nearby Messages API to monitor for Beacons. Default true.

This should not conflict with your own use of Nearby Messages API, so you can leave [automaticBeaconMonitoring] true even if you are using Google Nearby for your own beacons or messages.

Set to false if you do not want Rover to provide this functionality.

automaticLocationTracking: Boolean

Automatically use the Google Fused Location Provider API to track the device and user’s location in the background. This will make more accurate location information available about your users in the Rover Audience app. Default true.

This should not conflict with your own use of the Google Fused Location Provider API.

Set to false if you do not want Rover to provide this functionality.