Skip to content

Throw incorrect/missing gapi config properties when gapi determines the properties are incorrect #117

@begedin

Description

@begedin

Currently, this is what happens when we set a google API key or other property in the configuration, but we set it incorrectly:

image

Google's pop-up registers an error, but there's no helpful error message from the add-on, like it is when the keys are missing.

The same error that get's thrown when a key is missing should also be thrown when the key is present, but it's determined to be invalid/incorrect. This way, the user will know what's going on even in cases like these.

Hopefully, Google's pop-up somehow returns an error as a result when this happens, so we should be able to get hold of that error.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions