Places SDK for iOS
GMSPlaceField
now uses the
NS_OPTIONS
macro (As of v4.0.0)
Starting with Places SDK for iOS
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 SDK for iOS 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
- Parameters
bounds
and
boundsMode
for:
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
(Deprecated on May 26, 2020)
The Places field
permanently_closed
in the Places API
and Places Library, Maps JavaScript API is deprecated, and should not be used.
Instead, use
business_status
(Places API)
or
business_status
(Places Library)
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
(Deprecated on November 20, 2019)
The Places fields
open_now
and
utc_offset
in the Places Library, Maps JavaScript API
are deprecated as of November 20, 2019, and should not
be used.
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.
See
Places Field Migration
to learn more.
Maps JavaScript API:
google.maps.event.addDomListener()
and
google.maps.event.addDomListenerOnce()
(Deprecated on April 7, 2022)
The functions
[google.maps.event.addDomListener()](/maps/documentation/javascript/reference/event#event.addDomListener)
and
[google.maps.event.addDomListenerOnce()](/maps/documentation/javascript/reference/event#event.addDomListenerOnce)
in the Maps JavaScript API are deprecated, and should not be used. Instead, use the standard
addEventListener()
method.
These methods will continue to work and there is no plan to decommission them.
Completed deprecations
This section lists all products and features which have been decommissioned.
These products and features are no longer available.
Local Context Library, Maps JavaScript API (Deprecated as of v3.51.2)
Due to the limited adoption of this beta feature, Local Context Library
was discontinued in January 2024.
If you are interested in building a Local Context Library-like experience yourself, we suggest
that you check out the "Neighborhood Discovery" solution in
Quick
Builder
or use the
Places
Library
, Maps JavaScript API.
Code
samples
and
codelabs
for the Places Library can help you.
Google Maps Platform gaming services
(October 18, 2021 - December 31, 2022)
Since the introduction of our gaming services in 2018, were proud to launch
innovative new game experiences for developers. While we remain dedicated to
supporting the developer community, we’ve decommissioned Google Maps Platform
gaming services as of December 31, 2022 due to limited adoption.
Maps SDK for iOS v2.5 and lower (January 2022 - January 2023)
The Maps SDK for iOS v2.5 and lower were decommissioned in January 2023 which raised the minimum OS supported by Maps SDK for iOS to iOS 8 and the minimum supported IDE to Xcode 8.
We encourage you to
specify
and use
the latest version of the Maps SDK for iOS
.
Maps JavaScript API v2 (May 19, 2010 - May 26, 2021)
Version 2 of the Maps JavaScript API is no longer available as of
May 26, 2021. As a result, your site's v2 maps will stop working, and will
return JavaScript errors. To continue using maps on your site, migrate to the
Maps JavaScript API v3. Learn more about
upgrading Your Maps JavaScript API Application from v2 to v3
.
Places fields:
reference
,
id
,
alt_id
,
scope
(September 3, 2019 - August 10, 2020)
The Places fields
id
,
alt_id
, and
scope
are no longer available as of
August 10, 2020. The Places field
reference
is deprecated, and should not be
used.
- The
id
response field has been replaced by the
place_id
response field.
- The
reference
response field has been replaced by the
place_id
response,
and should not be used.
- 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.
iOS version 10, ARMv7 32-bit architecture in Maps SDK for iOS 5.0
As of
Maps SDK for iOS version 5.0
,
iOS 10 and the ARMv7 32-bit architecture are no longer supported.
Places SDK for iOS
With the release of
Places SDK for iOS 5.0
,
GMSCoordinateBounds
is decommissioned, replaced by
GMSPlacesViewportInfo
.
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.
Unsupported Place Search queries
in the Places API and Places Library, Maps JavaScript API
(March 31, 2022 - March 31, 2023)
Unsupported Place Search queries for Text Search, Nearby Search, and Find Place
in the Places API and Places Library, Maps JavaScript API
are deprecated as of March 31, 2022 and will
receive
INVALID_REQUEST
error responses beginning on March 31, 2023.
The
Places API
and
Places Library, Maps JavaScript API
support three methods to find places:
Text Search
,
Nearby Search
, and
Find Place
. Each
method accepts requests with supported combinations of parameters, and rejects
most requests with combinations of parameters that are not supported.
A few combinations of unsupported parameters have not been properly rejected
to date:
- Text Search requests with an empty or missing
query
parameter and without a
supported
type
parameter.
- Text Search requests with
query=*
.
- Nearby Search requests with
keyword=*
.
- Nearby Search requests with
name=*
.
- Find Place requests with
input=*
.
These unsupported Place Search requests must be replaced with one of the
following:
Nearby Search
requests
without the
keyword
(or
name
) parameter can be used to find nearby
establishments. It is recommended to also use the
type
parameter with one
supported type (see
Table 1: Place types
).
This provides the closest match to the current behavior of Text Search requests
with an empty or missing
query
parameter.
Geocoding API
requests with the
latlng
parameter can be used to find the nearest addresses.
This provides the closest match to the current behavior of:
- Text Search requests with
query=*
.
- Nearby Search requests with
keyword=*
.
- Nearby Search requests with
name=*
.
- Find Place requests with
input=*
.
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.