Versions

Select platform: Android iOS JavaScript

The Google Maps Platform team regularly updates SDKs with new features, bug fixes, and performance improvements. This page provides guidance on how to manage your dependencies on mobile SDKs.

  • For mission-critical apps, link to the latest dot release of the major version that you are using (X.*). This method requires you to make app updates at least once a year, when a new major version is released.
  • For non-critical apps, link to any fixed version. When you receive a deprecation notice for that fixed version, you will have 12 months to make your updated app code available to your users. This method means less frequent maintenance work, but the work may involve a greater amount of resources to adapt, rewrite, and test than would be required for annual updates. Such work would have to be completed before the deprecation.

Project Owners with monitored email addresses receive proactive notifications about changes that impact each of their projects. Stay informed about major updates, deprecations, and other changes.

Installation

In your app-level build.gradle file, always specify a version instead of a prefix range (+) or latest since these can lead to unpredictable and unrepeatable builds. The Places SDK for Android adheres to semantic versioning, and new major version releases may include breaking changes. The minimum API level supported is 16.

dependencies {
    implementation 'com.google.android.libraries.places:places:2.6.0'
}

Maintenance and upgrade

Android Studio automatically checks for newer available versions and provides a warning when a newer version of a dependency is available. To minimize technical debt, update to the newest available version as soon as possible. If you are updating to a new major version, check the release notes for backwards-incompatible changes and how to update your code.

In addition to polling for newer versions, Google Cloud project owners receive emails about backwards incompatible changes that may affect their projects. To get proactive notification about backwards incompatible changes, assign the owner role with a monitored email address for each of your projects.