Places API Autocomplete widget using the Places API (New) [401460263]

Fixed

Feature Request

Status Update

No update yet.

Description

nb...@gmail.com

created issue #1

Mar 7, 2025 02:11PM

Documented in these two threads.

https://stackoverflow.com/questions/79482008/google-places-api-new-autocomplete-not-working

https://stackoverflow.com/questions/79480026/why-do-i-keep-getting-the-apinotactivatedmaperror-when-ive-checked-that-my-api

Since March 1st, it is more complicated to enable the Legacy Places API. However there is no replacement Autocomplete widget yet based on the Places API (New), as a Generally Available feature.

Workaround: enable the Legacy Places API per #6 below.

Comments

br...@google.com <br...@google.com> Mar 9, 2025 11:04PM

Assigned to br...@google.com.

br...@google.com <br...@google.com> #2Mar 10, 2025 12:23AM

Thank you for posting.

We are currently looking into this and will get back to you as soon as we have an update.

br...@google.com <br...@google.com> #3Mar 10, 2025 04:42AM

Thank you for posting.

The issue has been logged internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications when the fix is released.

iv...@devforth.io <iv...@devforth.io> #4Mar 11, 2025 11:25AM

Just in case here are 2 JS fiddles to help with reproduction if someone needs it

Old API:

https://jsfiddle.net/05t4dbrh/2/

New API (beta):

https://jsfiddle.net/05t4dbrh/1/

Nothing works with the same issue

PS: alpha channel for New API has no error and even shows autocomplete dropdown, however callback is not called, also it seams like alpha channel can't be used in production because shows additional alert. Issue is very critical for us because none of the autocomplete widgets from google are working ATM.

ch...@inet-media.ca <ch...@inet-media.ca> #5Mar 11, 2025 06:54PM

According to Google Support, Autocomplete (NEW) Requires BOTH: Places (New) API + Places Legacy to be enabled (who knows why?) -- I was instructed to enable Legacy by going to: https://console.cloud.google.com/apis/library/places-backend.googleapis.com

Once that is enabled, the Autocomplete element worked as expected when using their Sample code: https://developers.google.com/maps/documentation/javascript/examples/place-autocomplete-element

ni...@google.com <ni...@google.com> #6Mar 11, 2025 08:17PM

Just to clarify: the issue is not specific to Vue or React. If you want to use a Places Autocomplete widget UI, there are two options:

The Preview Autocomplete widget. This widget requires the alpha version of the Maps JavaScript API, and uses the Places (New) API. This is a Preview version which is not suitable for production use
The GA Autocomplete widget, which uses the Places API (Legacy) service.

Given that the new API does not yet support an Autocomplete widget as a GA feature, it is appropriate to enable the Legacy API in this case. The link to enable the Legacy API is https://console.cloud.google.com/apis/library/places-backend.googleapis.com .

Once the new Autocomplete widget is GA, and the frameworks of your choice support them, it is recommended to migrate to the new Autocomplete widget.

We'll be updating the docs shortly to clarify this. Sorry for the confusion!

nb...@gmail.com <nb...@gmail.com> #7Mar 11, 2025 08:39PM

That was going to be my original solution (use Places API (Legacy) service), but that isn't an option I can enable in my cloud account. Attached a screenshot of everything available in my account.

Screenshot 2025-03-11 at 3.38.30 PM.png

60 KB

View

Download

ni...@google.com <ni...@google.com> #8Mar 11, 2025 08:44PM

Re: #7, Have you tried the direct link https://console.cloud.google.com/apis/library/places-backend.googleapis.com ?

nb...@gmail.com <nb...@gmail.com> #9Mar 11, 2025 08:46PM

Excellent, didn't know about the direct link. It's enabled. Thank you!

lu...@gmail.com <lu...@gmail.com> #10Mar 13, 2025 02:05PM

The link to the normal places API works. Just tested on 3 different sites that had the issue and all are working correctly now. Do not that for one case, I had to disable Places API (New) since it was overlapping with the dropdown of Places Api normal one. Most likely the way they got called, other than that, by simply sticking to the normal Places API, it works fine. It is the new that started breaking all sites.

ni...@google.com <ni...@google.com> #11Mar 14, 2025 02:48PM

Thanks for the report #10 - would you mind filing a support case with the issue you have experienced when enabling both APIs? That is definitely not expected and not a known issue. Thanks!

jh...@google.com <jh...@google.com> #12Mar 20, 2025 02:10PM

As an addendum to

comment #6

, #10, and #11, the Places Autocomplete widget in Preview currently uses the Places (legacy) API as its backend. It will switch to using the Places API (New) on or after the 31st March 2025; along with other incompatible changes.
We therefore recommend enabling Places (New) API as soon as possible.

We have sent a heads-up and migration guide to active developers using this widget in production a few weeks ago, please find it attached to this message as well.

Message last modified on Mar 20, 2025 02:11PM

395080217__62739404__196065.pdf

81 KB

View

Download

kk...@awesomemotive.com <kk...@awesomemotive.com> #13Mar 26, 2025 10:51AM

Comment has been deleted.

Message last modified on Mar 27, 2025 03:10AM

br...@google.com <br...@google.com> #14Mar 27, 2025 03:10AM

comment #13

Hi there, I think I found that not everything is still fixed in alpha channel (or maybe I don't understand something)

I have created an app with enabled apis:

Places API (new)
Maps JavaScript API
Geocoding API

If I initiate autocomplete with new google.maps.places.PlaceAutocompleteElement() it works. But if I initiate it with google.maps.places.Autocomplete(input) with the exiting input HTML element, it still shows the error "This API project is not authorized to use this API. Places API error: ApiNotActivatedMapError"

Here is an example with both fields. https://jsfiddle.net/de1qvnpj/ (link changed due to PII)

Questions:

is google.maps.places.Autocomplete(input) syntax going to be supported with new Places API?
if not, what is the other way to initailize autocomplete on existing input elements?

Message last modified on Mar 27, 2025 03:11AM

br...@google.com <br...@google.com> #15Mar 27, 2025 03:17AM

Re: comment #13

The new google.maps.places.Autocomplete() method is part of the Places API (Legacy), which required separate activation and has been deprecated since March 1, 2025. Therefore, to initialize Place Autocomplete (New) on existing input elements, it's recommended to use the programmatic interface via AutocompleteSuggestion.fetchAutocompleteSuggestions from the Place Autocomplete Data API. This interface lets you fetch place predictions and manage the autocomplete experience or widget yourself. For more details on migrating to the new Place Autocomplete, please refer to this documentation.

Thank you for your understanding.

Message last modified on Mar 27, 2025 03:45AM

lu...@gmail.com <lu...@gmail.com> #16Mar 29, 2025 05:04PM

I can confirm what was said above about the google.maps.places.Autocomplete(input) that shows with the warning "This API project is not authorized to use this API. " still. But just saw the comment about the AutocompleteSuggestion.fetchAutocompleteSuggestions so I will be reading that document. Thank you.

br...@google.com <br...@google.com> #17Apr 4, 2025 03:59AM

Marked as fixed.

Thank you for your patience.

We are pleased to announce that the Place Autocomplete Widget has transitioned from Preview to General Availability (GA) and is now available in the weekly channel. Please refer to the Maps JavaScript API Release Notes for more details. Additionally, the documentation has been updated accordingly. For further information regarding the migration of the Place Autocomplete Widget, please see this documentation.