Skip to content
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

[Tech debt] Firebase recommends creating using separate keys for Firebase and Maps API credentials #2097

Open
4 tasks
gino-m opened this issue Nov 16, 2024 · 1 comment
Labels
type: code health Improvements to readability or robustness of codebase

Comments

@gino-m
Copy link
Collaborator

gino-m commented Nov 16, 2024

Because of this, we'll need to:

  • Create Android and JavaScript Maps API API keys in the maintainers dev project
  • Update the web build script to read the key (from a file)?
  • Update the Android build script to read the key (from a file)?
  • Update the guide in the wiki

@shobhitagarwal1612 @anandwana001 @rfontanarosa FYI

@gino-m gino-m added the type: code health Improvements to readability or robustness of codebase label Nov 16, 2024
@gino-m gino-m changed the title [DevEx] Maps API keys no longer created on Firebase setup [Tech debt] Firebase recommends creating using separate keys for Firebase and Maps API credentials Nov 16, 2024
@gino-m
Copy link
Collaborator Author

gino-m commented Nov 16, 2024

In the end, I was able to manually enable Maps APIs under the Firebase keys in API Credentials in Cloud Console for the dev instance. This is a workaround, however, and the above still applies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: code health Improvements to readability or robustness of codebase
Projects
Status: No status
Development

No branches or pull requests

1 participant