You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: