The project at the top of the page is munistack-w5e2c, the firebaserc file is showing the correct project, munistack-d7a84, the terminal is showing the correct active project: munistack-d7a84
I’ve tried resetting the VM, closing all windows. I’ve even deleted the w5e2c project and it’s still there.
Same here. What I realized:
- I went through prototyping
- When needed, build a Firebase project, storage, firestore, authentication and put all keys do .env.local file
- When ready to publis, Firebase Studio insists to build a new Firebase Project for App Hosting.
I could not set to publish to MY project. Defeated, I configured all again in the Studio created project and changed values in .env.local
You recreated your entire project to solve it is that what you’re saying? I’m a bit too far to do that. I have cloud functions, database is setup, indexes, etc.
Yes. I did it. But I had just started. Had to recreate auth, storage, firestore, indexes, etc. So, from now on, I will start a new project, publish it after the first prompt and then continue to build and setup stuff.
Facing the same problem too, is there no way around this. Doesn’t look good to have two projects managing one app, the one created by firebase studio is hosting and the one i created is doing the rest: db, storage etc