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.
Which version to link to?
For mission-critical apps, link to the latest dot release of the major version that you are using (X.*), and upgrade yearly to the new major version.
As you release new versions of your application throughout the year, you may start using newer dot versions of the Places SDK for iOS. This will not require updates in your application as new dot versions are backward compatible.
- If you discover issues in the Places SDK for iOS, fixes will be provided in a backward-compatible way for 12 months after the initial release of the major version, per the Mobile support policy. You will not need to urgently upgrade to an incompatible SDK version to benefit from fixes.
- The latest improvements and features are easy to adopt when your app is already built on the latest version.
- Annual incremental updates to the newest major version of the SDK may require less work to adapt, rewrite, and test your application, than having to handle backwards-incompatible changes introduced across multiple major version releases.
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.
- Less frequent maintenance work.
- New versions of your app keep supporting users' devices running older mobile operating systems for longer (until you need to upgrade to a new SDK version).
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.
Always specify a version number in your dependencies instead of using an optimistic operator
~>) since that can lead to unpredictable and unrepeatable builds. The
Places SDK for iOS adheres to semantic versioning,
and new major version releases include breaking changes.
An example Podfile dependency using Podfile syntax:
source 'https://github.com/CocoaPods/Specs.git' platform :ios, '14.0' target 'YOUR_APPLICATION_TARGET_NAME_HERE' do pod 'GooglePlaces', '8.2.1' end
Maintenance and upgrade
To build with the latest improvements, regularly check for newer versions and update your version specifications. If you are updating to a new major version, check the release notes for backwards-incompatible changes and how to update your code.
Open a terminal and go to the directory containing the
pod outdatedto see if a newer version of the Places SDK for iOS is available.
- If a newer version of the SDK is found, update your
Podfilewith this new version. See Specifying pod versions to learn how to set a specific version in your
- Make any necessary changes as a result of the upgrade. See the Release Notes for a list of the changes in each release.
- Clean and rebuild your project by selecting Product > Clean and then Product > Build
Get the link to the latest source files at Installing the SDK.
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.