fix(core): update error messages mentioning init usage - #16294
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
2 participants
Per b/525041208,
This PR updates the error messages in App Check, Auth, and Installations that were displayed when a default firebase instance wasn't configured. More specifically, it removes the mention of doing your configuration in the
@mainstruct's initializer.Initializing firebase in the
init()method of your app may or may not work depending on the products you're using. Some products require the app to be fully initialized before being configured, andinit()is called before the app is done launching, so attempting to configure these products would cause crashes.Folks can continue to initialize firebase in
init()if it's working for their selected products, but it's not something we should continue to push as a "supported method" if not all of our products support it.In the future, we should investigate the overhead and requirements it would take to adapt our SDKs to not be so reliant on the application's existence and launch state, but that'd take a large amount of overhead to properly investigate.