Noobs question. Is it standard process for a published project should auto create a new project (same name)? Isn’t it looks duplicated?
Oh, that is weird! Are you manually creating a Firebase project at some point? When you work in prototyper and press the Publish button to automatically publish via App Hosting, it does automatically create a Firebase project for you at that point. To my knowledge, it shouldn’t create two projects, but if you’re already creating one, and then publishing via the button, maybe that’s why there are two of them.
indeed! here is my workflow with prototype
- Create a game, “Tic Tac Toe”
- Tell the agent i need to create online play, able to save history and invite friend (hence required sign in with Firebase Auth)
- Manually create a project in firebase console
- manually link env/env.local with my firebase project
- Console > Firebase Auth > enable Google signin provider > add project URL into authorized domain
- Everything tested ok, then publish
- Duplicated project created
it’s very normal workflow as firebase auth can’t work without a physical project created, AFAIK.
Yep, totally makes sense. So what I usually do to avoid that is hit the publish button pretty early on to create a linked firebase project, but I don’t actually go through with publishing to app hosting until later. But that way I have a project ready to go. Same thing happens when you auto-generate a Gemini API key (it’ll create that linked project). We’re working on improvements to the flow.
