RootCauseunvalidated
The API key likely has only the correct/modern Places API enabled (or vice versa) but the autocomplete component is calling a different variant of the Places web service endpoints (Legacy vs New), leading to an 'API not activated' response.
d5a3cb5d-70d2-4e3e-b866-782b8db9f9a8
The API key likely has only the correct/modern Places API enabled (or vice versa) but the autocomplete component is calling a different variant of the Places web service endpoints (Legacy vs New), leading to an 'API not activated' response.