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

[FR]: Why require google-services.json, if possible without it? #1040

Open
maxgmer opened this issue Jun 4, 2024 · 1 comment
Open

[FR]: Why require google-services.json, if possible without it? #1040

maxgmer opened this issue Jun 4, 2024 · 1 comment

Comments

@maxgmer
Copy link

maxgmer commented Jun 4, 2024

Description

Right now it's pain in the butt to enable one project to work with multiple Firebase environments.

To avoid doing stupid stuff like creating/deleting google-services.json files with pre-build scripts, we just use the AppOptions constructor and manually provide all of the data google-services.json contains.
But iOS has annoying errors about plist missing, which forces us to keep google-services.json mock files for iOS and Android (with fake credentials).

Considering how non-optimal the file configuration UX is, why not make it optional?

P.S.If AppOptions is incomplete, would be great if you make it a complete alternative to config files.

API Proposal

No response

Firebase Product(s)

All

Targeted Platform(s)

Apple Platforms, Android

@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@argzdev argzdev removed the new New issue. label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants