-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inform about bad keys #376
Comments
Same issue here. As per the docs: // Promise
loader
.load()
.then((google) => {
new google.maps.Map(document.getElementById("map"), mapOptions);
})
.catch(e => {
// do something
}); I'd usually expect that errors from "bad keys" can be caught here. I need such validation logic as I'm letting my users input their own keys for testing purposes. Is there even a way to validate maps api keys? I have not found anything in the docs. |
Is any news? @wangela |
This can be implemented in client-code using the Since the key-validation happens at an unknown time while using the API, it is not possible to include this information in the response to the |
Not sure what the implementation should look like. But it would be useful to know if they key is valid or not and allow a different code path in the application.
The text was updated successfully, but these errors were encountered: