[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation changes
[ ] Other... Please describe:
PR Checklist
For bug fixes / features, please check if your PR fulfills the following requirements:
[ ] Testing has been carried out for the changes have been added
[ ] Regression testing has been carried out for existing functionality
[X] Docs have been added / updated
What is the purpose of this PR?
A natural instinct would be to follow the guidelines in the GCP console and to place an Android app restriction on the key. This will not work as the regular HTTP interface is used, where the app is not identified as such. HTTP referrer restrictions also do not work, because none are passed to the API.
Ultimately, if any application restrictions are placed on the key, requests will fail.
Does this PR introduce a breaking change?
[ ] Yes
[X] No
What testing has been done on the changes in the PR?
What testing has been done on existing functionality?
PR Type
What kind of change does this PR introduce?
PR Checklist
For bug fixes / features, please check if your PR fulfills the following requirements:
What is the purpose of this PR?
A natural instinct would be to follow the guidelines in the GCP console and to place an Android app restriction on the key. This will not work as the regular HTTP interface is used, where the app is not identified as such. HTTP referrer restrictions also do not work, because none are passed to the API.
Ultimately, if any application restrictions are placed on the key, requests will fail.
Does this PR introduce a breaking change?
What testing has been done on the changes in the PR?
What testing has been done on existing functionality?
Other information