Closed werebus closed 5 years ago
Oh, interesting
@werebus, is this also on iOS like #485?
Nope. It's on the web platform (https://m.pvta.com/#/plan-trip).
Oh, sorry. Reread the title of the issue right now. Thanks
I've looked into this and fixed the dropdown in development. I was able to do so by adding these APIs:
Geocoding
The Geocoding API is a service that provides geocoding and reverse geocoding of addresses.
Geocoding is the process of converting addresses (like a street address) into geographic coordinates (like latitude and longitude), which you can use to place markers on a map, or position the map. Reverse geocoding is the process of converting geographic coordinates into a human-readable address.
You can also use the Geocoding API to find the address for a given place ID.
Places
The Places API is a service that returns information about places using HTTP requests. Places are defined within this API as establishments, geographic locations, or prominent points of interest.
I wonder if this is related to #485, since the dropdown on android is also not functioning properly.
The thing that's stopping me from making this change to the other API keys is that I'm not sure if we need the Geocoding API to be added. Afterall, it is part of the Google Maps JavaScript API (currently the only API we're using on PVTrAck).
Update: all good! Deleting the Geocoding API made no difference
The problem was occurring in the autocomplete of the plan trip/the schedule page. So autocomplete relies on Places. I enabled that API.
To double check, I looked at the API picker on Google Maps Platform, which indicates that Places API includes the following request:
Place Autocomplete automatically fills in the name and/or address of a place as users type.
TLDR -- Enabling the Places API on Google Cloud fixes the problem in development. Should I do the same for production?
Please let me know if this sounds like a good idea @sherson, @anbranin, @werebus, and I'll make the proper changes. 👍
I think our app does use the Geocoding API to encode the user's current location into a place name.
Yes, if our app uses a particular API, that API needs to be enabled. And, at least for now, all of the versions of our app — iOS, Android, Web — use the same APIs.
Got it! Enabling them for production now.
Errr the autocomplete works on web, but I keep getting this message...
Enabled Directions API, all good.
After adding the APIs, looks good to me. Will reopen if there still seems to me an issue.
In the console:
I don't think that this is related to #485, but there's a chance.