Does not work with new Places API, legacy Places API not available for new GCP projects

[jjfattz]

New GCP projects cannot enable the legacy Places API anymore and therefore cannot use this package until it is updated to work with the new Places API.

[arpu-nagar]

been stuck on this for 2 days now, thinking of implementing something of my own

[CandyNorth]

been stuck on this for 2 days now, thinking of implementing something of my own

Same here.

I saw another issue that was closed, which explains that this library calls the wrong API endpoint.

@FaridSafi / anyone planning on looking into this?

Thank you.

[Daniel-W1]

yes, +1

[Andrei21XD]

same issue +1

[equilizer]

facing the same problem

[akozy1]

Same issue +1

[adamalexander]

Yep, not working anymore.

[dvvidd7]

ok, so I successfully got the link to the old places API and enabled it but it still doesn't work. google support told me to activate both the new and the old API but without any result, except for the fact that I got rid of the "(NOBRIDGE) ERROR This API project is not authorized to use this API" error. maybe you can do something with it and share the fix with us. https://console.cloud.google.com/apis/library/places-backend.googleapis.com

[MohitNarkhede]

+1

[MohitNarkhede]

@arpu-nagar did you find any solution?

[nlarif]

I managed to make it work with the new Places API :

1. I took the 2.5.7 version or the last commit from master to include this PR https://github.com/FaridSafi/react-native-google-places-autocomplete/pull/943/files#diff-c0d73f319f1167879412f6c75dcd9cc124356ef467bb09cc3874a36ce3cdecdc:
   packages.json:
"react-native-google-places-autocomplete": "https://github.com/FaridSafi/react-native-google-places-autocomplete#master"
2. I had to patch node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.js
   import Qs from 'qs';
+import 'react-native-get-random-values';
import { v4 as uuidv4 } from 'uuid';
   (see last paragraph of https://www.npmjs.com/package/uuid)
3. Then I used the new prop isNewPlacesAPI={true} of (see the PR above)

[Ramer357]

@nlarif and what restrictions have you put on your API key in the google cloud console?

[nlarif]

I just allowed the existing API key of Legacy Places to be used with the new Places API: GCP Console > APIs & Services > Credentials > Your existing key > Edit API Key > API restriction > Add New Places API

[Ramer357]

and shouldn't the request url be changed? i think there is something wrong with the request in the GooglePlacesAutocomplete.js file as the request.status is 0 (i console.logged it because it still doesn't work)