Deprecations

This page lists all Google Maps Platform products and features which are currently in a deprecation period. This includes products under Maps, Routes, and Places.

How deprecation works

The deprecation period for a product, feature, or version begins on the announcement date for the deprecation. The product, feature, or version will continue to be available throughout the deprecation period (typically 12 months). Once the deprecation period has elapsed, the product, feature, or version will be turned off, and will no longer be available.

Deprecation in SDK versions

In SDKs and the Maps JavaScript API, feature deprecations are tied to version availability. New major versions declare breaking changes including feature deprecations and release notes indicate the maximum supporting version of each deprecated feature. You can continue to use the deprecated feature for as long as its maximum supporting SDK version is available. To upgrade to the next major version of the SDK, you must remove use of the deprecated feature from your code or migrate to its replacement.

Learn more about Maps JavaScript API version availability, which follows a quarterly release and decommissioning schedule.

See guidance on managing version dependencies with the Maps SDK for Android, Maps SDK for iOS, Places SDK for Android, and Places SDK for iOS.

Active deprecations

This section lists all products and features which are currently in a deprecation period.

Obsolete place IDs (March 16, 2021 - March 30, 2022)

On March 30, 2022, all Google Maps Platform APIs will stop accepting certain obsolete place IDs. Beginning on March 30, 2022, any requests made using obsolete place IDs will be rejected, and return error code INVALID_REQUEST. To prevent user experience degradation, please refresh all place IDs that are older than 12 months before March 30, 2022.

Maps Module in google.load (October 13, 2020 -October 13, 2021)

The service that provides the "Maps" module for google.load is deprecated as of October 13, 2020, and will be turned off on October 13, 2021. Subsequent requests to load the "Maps" module in google.load will result in an error, and no map will load. See the Migration Guide for more information.

Places Library, Maps JavaScript API GMSPlaceField now uses the NS_OPTIONS macro (As of v4.0.0)

Starting with Places Library, Maps JavaScript API v4.0.0, GMSPlaceField now uses the NS_OPTIONS macro instead of NS_ENUM for better Swift support. Read more about Migrating to GMSPlaceField as NS_OPTIONS.

To continue using GMSPlaceField as NS_ENUM, specify v3.10.0 or earlier in your dependencies.

Places SDK for iOS methods: setAutocompleteBoundsUsingNorthEastCorner:SouthWestCorner, initWithBounds:filter (v3.10.0 - v4.0.0)

The setAutocompleteBoundsUsingNorthEastCorner:SouthWestCorner helper method is deprecated as of v3.10.0, and is unsupported in v4.0.0 and higher. Instead, use locationBias, or locationRestriction.

The initWithBounds:filter method is deprecated as of v3.10.0, and is unsupported in v4.0.0 and higher. Instead, use initWithFilter: in GMSAutocompleteFetcher.

The maximum supporting version for these deprecated methods is v3.10.0.

For details about replacement methods, see Appendix 1.

GMSCoordinateBounds in Place Autocomplete (v3.9.0 - v4.0.0)

Several properties/parameters utilizing GMSCoordinateBounds in the Places Library, JavaScript API Autocomplete service, are deprecated as of v3.9.0, and are unsupported in v4.0.0 and higher. The maximum supporting version for the deprecated properties/parameters is v3.10.0.

Bounds in GMSAutocompleteViewController

The following GMSAutocompleteViewController properties are deprecated:

For equivalent functionality, use GMSAutocompleteViewController.autocompleteFilter, with either GMSAutocompleteFilter.locationBias or GMSAutocompleteFilter.locationRestriction. The minimum version of the Places SDK for iOS with these replacement properties is v3.8.0.

Bounds in findAutocompletePredictionsFromQuery and autocompleteQuery

For equivalent functionality, use findAutocompletePredictionsFromQuery:filter:sessionToken:callback with either GMSAutocompleteFilter.locationBias or GMSAutocompleteFilter.locationRestriction. The minimum version of the Places SDK for iOS with these replacement properties is v3.8.0.

For details about replacement methods, see Appendix 1.

Places field GMSPlace.openNowStatus (v3.0.0 - v4.0.0)

The Places field/property GMSPlace.openNowStatus in the Places SDK for iOS is deprecated as of v3.0.0, and is unsupported in v4.0.0 and higher. The maximum supporting version for the deprecated field is v3.10.0.

Instead, use functions GMSPlace.isOpen or GMSPlace.isOpenAtDate. The minimum version of the Places SDK for iOS with these replacement functions is v3.3.0.

Places field: permanently_closed (May 26, 2020 - May 26, 2021)

The Places field permanently_closed in the Places API and Places Library, Maps JavaScript API is deprecated as of May 26, 2020, and will be turned off on May 26, 2021. Instead, use business_status (Places API) or business_status (Places Library, JavaScript API) to get the operational status of businesses. The minimum version of Places Library, Maps JavaScript API with business_status is v3.40.

Places fields open_now, utc_offset (November 20, 2019 - February 20, 2021)

The Places fields open_now and utc_offset in the Places Library, Maps JavaScript API are deprecated as of November 20, 2019, and will be turned off on February 20, 2021.

These fields are only deprecated in the Places Library, Maps JavaScript API.

  • The open_now field has been replaced by PlaceResult.opening_hours.isOpen() in Place Details. For Nearby Search and Text Search, use the openNow:true request parameter to filter for places that are currently open. No equivalent is provided for Find Place. To get this value, you must now make a Place Details request.
  • The utc_offset field has been replaced by PlaceResult.utc_offset_minutes in Place Details.

The minimum version of Places Library, JavaScript API with isOpen() and utc_offset_minutes is v3.39. See Places Field Migration to learn more.

Places fields: reference, id, alt_id, scope (September 3, 2019 - August 10, 2020)

The Places fields reference, id, alt_id, and scope are deprecated as of September 3, 2019, and will be turned off on August 10, 2020.

  • The id and reference request parameters have been replaced by the place_id request parameter.
  • the alt_id and scope fields have no equivalent, as they were only used for the Place Add service which was turned off in July 2018.

See Place field migration for details.

Maps JavaScript API v2 (May 19, 2010 - May 26, 2021)

Version 2 of the Maps JavaScript API is deprecated as of May 19, 2010, and will be turned off on May 26, 2021. Although you can continue using the Maps JavaScript API v2 until May 26, 2021, maps using v2 will display a darkened map watermarked with the text "for development purposes only" on your site's v2 maps starting October 26, 2020. To avoid any inconvenience or user confusion when this happens, we strongly recommend migrating your site to the Maps JavaScript API v3 before October 26, 2020. Learn more about upgrading Your Maps JavaScript API Application from v2 to v3.

Completed deprecations

This section lists all products and features for which the deprecation period has elapsed. These products and features are no longer available.

Places fields: reference, id, alt_id, scope (September 3, 2019 - August 10, 2020)

The Places fields reference, id, alt_id, and scope are deprecated as of September 3, 2019, and will be turned off on August 10, 2020.

  • The id and reference response fields have been replaced by the place_id response field.
  • the alt_id and scope fields have no equivalent, as they were only used for the Place Add service which was turned off in July 2018.

Fusion Tables Layer (Experimental) (December 3, 2018 - December 3, 2019)

The Fusion Tables Layer in the Maps JavaScript API was turned off on December 3, 2019, and is no longer available as of version 3.38 (3.37 is the last version to support fusion tables). Learn more.

Places SDKs for Android and iOS (January 29, 2019 - July 29, 2019)

Effective January 29, 2019, the upgraded Places SDKs for Android and iOS replaced the existing versions of the Places SDKs. The current versions of the Places SDK for iOS, the Places SDK for Android, and the Place Picker, were deprecated as of January 29, 2019, and were turned off on July 29, 2019.

Place Add and Place Delete (June 30, 2017 - June 30, 2018)

Effective June 30, 2018, the Place Add and Place Delete features have been turned off, and are no longer available.

Appendix 1: Summary of Places SDK for iOS deprecated API replacements

The following table shows the replacement method to use for each deprecated method or property.

Deprecated method/property Use instead
setAutocompleteBoundsUsingNorthEastCorner:SouthWestCorner
(in GMSAutocompleteViewController)		 locationRestriction and locationBias
setAutocompleteBoundsUsingNorthEastCorner:SouthWestCorner
(in GMSAutocompleteResultsViewController)		 locationRestriction and locationBias
setAutocompleteBoundsUsingNorthEastCorner:SouthWestCorner
(in GMSAutocompleteTableDataSource)		 locationRestriction and locationBias
initWithBounds:filter
(in GMSAutocompleteFetcher)		 initWithFilter:
autocompleteBounds and autocompleteBoundsMode
(in GMSAutocompleteViewController)		 GMSAutocompleteViewController.autocompleteFilter with either locationBias or locationRestriction.
findAutocompletePredictionsFromQuery:bounds:boundsMode:filter:SessionToken:callback, autocompleteQuery:bounds:filter:callback, and autocompleteQuery:bounds:boundsMode:filter:callback
(in GMSPlacesClient)		 findAutocompletePredictionsFromQuery:filter:sessionToken:callback, with either locationBias or locationRestriction.

The minimum version of the Places SDK for iOS with the replacement properties is v3.8.0.