Calling the Places API legacy instead of Places API (NEW) #508
-
|
I 'm using useMapLibrary('places') to use the Places API, so I enabled Places API (NEW) on my google cloud console account, and I was getting an error saying DENIED_REQUEST, I enabled Places API (LEGACY) on my google cloud console and the request to the Places API is working, but I noticed that the call is sent to the Places API (Legacy). I need some clarifications on this, How to force the use for the Places API (NEW) ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Have a look here: #465 (comment) Essentially: The two will likely coexist for a bit, if you want to use the new API backend, you also need to use the new API classes ( |
Beta Was this translation helpful? Give feedback.
Have a look here: #465 (comment)
Essentially: The two will likely coexist for a bit, if you want to use the new API backend, you also need to use the new API classes (
google.maps.places.Place,google.maps.places.AutocompleteSuggestionetc.). There's no compatibility of the older API classes with the new backend service.