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
The setup should leave the workspace deployable: record the selected project as the CLI default, and — when Firestore is selected — generate starter security rules plus the firebase.json firestore section, the way firebase init firestore does.
Actual behavior
Every later firebase-tools command prompts for (or fails without) a project, and firebase deploy --only firestore:rules has nothing to deploy. Related downstream reports: #3559 (empty firebase.json, closed unfixed), #3546/#3676 (ng deploy setup loop — the angular.json deploy-target half, out of scope here).
Version info
Angular: 21.2.x Firebase: 12.x AngularFire: 21.0.0-rc.0
How to reproduce these conditions
ng new my-app && cd my-appng add @angular/fire@next, sign in, select a project and Firestore..firebasercdoes not exist (the project selected during setup is recorded nowhere),firebase.jsonis{}(see Firebase.json empty after running 'ng add @angular/fire' #3559), and nofirestore.rulesexists.Expected behavior
The setup should leave the workspace deployable: record the selected project as the CLI default, and — when Firestore is selected — generate starter security rules plus the
firebase.jsonfirestore section, the wayfirebase init firestoredoes.Actual behavior
Every later firebase-tools command prompts for (or fails without) a project, and
firebase deploy --only firestore:ruleshas nothing to deploy. Related downstream reports: #3559 (empty firebase.json, closed unfixed), #3546/#3676 (ng deploysetup loop — the angular.json deploy-target half, out of scope here).