This section contains release notes for the Consumer SDK for Android.
1.2.1 (June 7, 2023)
- Fixes a bug that causes the vehicle to flicker during journey sharing.
1.2.0 (November 21, 2022)
- Fixes bug that caused empty traffic to be reported in the
- "Traffic-aware polylines" is now generally available.
1.1.2 (October 27, 2022)
- Addresses bug that cause the route polyline to disappear after a
JourneySharingSessionis started more than once for a
Announcement: Freezing support for Android 5 (July 25, 2022)
For our v1.1.1 SDK version, we are providing an additional year of support for apps running on Android 5, for both API levels 21 and 22.
What this means:
Consumer SDK running on your Android apps will support a minimum Android 5 (API level 21) until June 30, 2023.
After June 30, 2023, we will support only Android API levels 23 and above. In other words, we will stop supporting Android API levels 21 and 22 across all SDK versions after that date. This means that bugs related to Android 21 or 22 in any SDK version (including 4.x) will not be fixed, and we do not guarantee that the SDKs will behave correctly.
v1.1.1 (July 25, 2022)
- Downgrades the minimum supported Android API level to 21.
v1.1.0 (April 28, 2022)
- Internal improvements.
v1.0.19 (March 17, 2022)
- Fixed a memory leak in the
v1.0.14 (November 30, 2021)
The minimum supported Android API level is now 23.
Changes to the
- Cleaned up some method names to make their meaning clearer, and to align with the iOS platform.
Changed some class names to form parity with iOS. Introduced
Cleaned up some method names. Revised or added JavaDoc comments to methods to convey clearer meanings.
Improved error handling.
Deprecated legacy wrappers
PolylineStyleOptionswere deprecated and replaced by
PolylineOptions, which are both shared with the Maps SDK.
Added crash detection and logging.
- An addition was made to allow you to opt out of this functionality. This was done as a part of a larger Geo-wide effort for crash monitoring.
- Remove unnecessary methods from the Authentication interfaces.
- Removed the
- Removed the
v0.9.28 (May 18, 2021)
- Updated all
ConsumerTripCallbackmethods to use
TripInfoas the parameter.
ConsumerTrip.isRefreshing(), which indicates whether
ConsumerTripis actively updating itself with fresh trip information from Fleet Engine.
- Replace Guava return types (
- Package name changes:
- com.google.android.libraries.ridesharing.common.AuthTokenContext -> com.google.android.libraries.ridesharing.consumer.auth.AuthTokenContext
- com.google.android.libraries.ridesharing.common.AuthTokenFactory -> com.google.android.libraries.ridesharing.consumer.auth.AuthTokenFactory
- com.google.android.libraries.ridesharing.common.FleetEngineServiceType -> com.google.android.libraries.ridesharing.consumer.auth.FleetEngineServiceType
- com.google.android.libraries.ridesharing.common.model.Trip -> com.google.android.libraries.ridesharing.consumer.model.Trip
- com.google.android.libraries.ridesharing.common.model.Vehicle -> com.google.android.libraries.ridesharing.consumer.model.Vehicle
- Fixed a race condition where the SDK could crash from interactions with the map before it is ready.
- The SDK no longer contains an unobfuscated copy of
- Fixed a bug with flickering traffic polylines on certain devices. Traffic segments will now have rounded ends.
v0.9.15 (October 7, 2020)
- This release introduces
Traffic Aware Polylines.
ConsumerTripCallback.onTripRemainingRouteTrafficUpdated()to indicate when traffic has changed.
PolylineStyleOptionsfor traffic customization (
ConsumerController.showSession()no longer accepts null as an argument.
v0.9.9 (July 15, 2020)
- This is a major change that introduces a modularized architecture with a
clearer relationship between the data-only layer (for example,
ConsumerTripManager) and the user interface layer (for example,
JourneySharingSession). For information on migrating to the new architecture, see the Modularization Migration Guide.
ConsumerTripobject is now obtained from
ConsumerTrip.unregisterCallbackhas been renamed to
ConsumerTrip.isCallbackRegisteredhas been renamed to
- Removed non-journey sharing APIs.
- Removed vehicle density map.
- Removed trip preview state.
- Removed pickup selection state.
- Removed dropoff selection state.
- Removed the following marker types:
ConsumerMapReadyCallbackfrom interfaces to abstract classes.
- Removed the custom FAB and its associated methods
ConsumerTripCallback, whether registered with or without a
LifecycleOwner, no longer automatically unregisters on
- AutoCamera is now enabled by default and never reenables or disables itself.
Previously, AutoCamera automatically reenabled on
TripStatus.ARRIVED_AT_PICKUPand disabled itself when the user interacted with the map during journey sharing.
- The following improvements have been made to journey sharing vehicle
- Journey sharing animation now handles the situation where a vehicle may legitimately travel back along an already-traversed route.
- The vehicle will now straight-line animate instead of route interpolating between points when it is determined algorithmically to be appropriate.
FINE_LOCATIONpermissions are no longer required.
- Updated the following dependency versions:
v0.9.1 (March 23, 2020)
optionsclass used during
ConsumerApiinitialization that lets the
FleetEngineaddress to be dynamically set. If the API is not called with a
FleetEnginevalue, it attempts to fetch it from the Android manifest or else falls back to the default value.
- The route polyline is not displayed when the trip status is
- Off-route vehicle tracking has been improved (requires DriverSDK 1.15):
- Vehicle tracking does not snap the vehicle to the route when the vehicle drives past the pickup point.
- Vehicle tracking enables displaying the vehicle off the road; for example, in unmapped parking lots.
- The vehicle icon now updates when the driver’s destination does not match the destination in Fleet Engine.
v0.8.6 (December 16, 2019)
ConsumerMapViewis no longer final.
- The active leg remaining distance is now calculated using server distance (driver reported + static route where applicable) instead of local snapping. This change produces more accurate remaining distance values.
New dependencies required. See the .pom file for details.
Added logs for trip request latency.
Added logs for trip response errors.
- Since version 0.8.1, the Consumer SDK for Android ships as a jetified zip archive. For information about how to de-jetify it, see Jetifier: Reverse mode.
v0.8.1 (September 13, 2019)
Support for ConsumerMapView.
ODRD artifacts now ship in a maven repository instead of an .aar zipfile. For more information, see Add the Consumer SDK to your app.
ConsumerController.disableAutoCamera()as the opposite function to
VehicleLocation.getUpdateTime()now returns a Long that represents the timestamp (in milliseconds).
AuthTokenFactoryinterface to expose a single method for token generation. Changed
AuthTokenFactoryfrom an interface to an abstract class to enable backwards compatibility in Java7. This change is backward compatible, but the old methods for single service token generation are deprecated, and will eventually be removed.
Assets now centered to icon center, eliminating shadow offset.
JOURNEY_SHARING onStartTripMonitoring()instead of waiting for monitored Trip's status.
Always returns data for first trip data update, even when trip data is out of sync.
Added Android Map Utils as a provided dependency.
- Fixed broken proguard export syntax for grpc keep.
v0.7.0 (August 7, 2019)
- Multidestination support for Journey Sharing.
New methods for
- You can obtain
TripInfofor the active trip with
- You can obtain
Fixed a bug where route is not trimmed to the vehicle location when trip monitoring starts in the middle of an active trip (not at head of route).
Fixed a bug where trip callbacks are not invoked for listeners registered on the Tripmanager after the TripManager has already fetched trip data.
Camera zoom now includes only the active route and the next trip waypoint (waypoint that belongs to the trip). Even if the remaining leg is visible, the zoom will never include it. Previously, the drop-off point was included in the zoom when the vehicle was either enroute to pickup, or arrived at pickup. This is no longer true.
Populate the zeroth remaining waypoint with Driver data (remaining waypoint list is returned from
Update all remaining waypoint ETAs when the ETA to the first waypoint in the list changes.
Force re-enable autocamera only when driver arrives at pickup. Previously, autocamera would reset to enabled for every trip state change. Autocamera is still enabled by default. Autocamera will not re-enable if a new active trip is set without a fresh call to
v0.6.1 (June 26, 2019)
- Carpool support for journey sharing.
Route animation now happens only when the route segment is in sync, resulting in an improved user experience.
Fixed vehicle "flickering" during animation interpolation when driver location updates are close together.
Fixed a bug where the vehicle starts at the head of the route instead of at its most updated location when trip monitoring starts in the middle of an active trip.
Display the active route polyline above the remaining route when they overlap.
- Now expose the gRPC
Statusclass with unobfuscated methods.
v0.5.1.01 (May 17, 2019)
- Back-to-back support for Journey Sharing.
|Old Value||New Value|
|Old Value||New Value|
- You can now set callbacks for states without entering the state.
ConsumerController.setLanguage(String languageCode)allows you to set the language used in FleetEngine calls (for pickup point descriptions, for example).
- Dropoff selection state now has a draggable pin.
- Removed camera animation in