Skip to content

ng add never writes .firebaserc or Firestore starter files — deploys have no default project and no rules #3713

Description

@armando-navarro

Version info

Angular: 21.2.x Firebase: 12.x AngularFire: 21.0.0-rc.0

How to reproduce these conditions

  1. ng new my-app && cd my-app
  2. ng add @angular/fire@next, sign in, select a project and Firestore.
  3. After the schematic finishes: .firebaserc does not exist (the project selected during setup is recorded nowhere), firebase.json is {} (see Firebase.json empty after running 'ng add @angular/fire' #3559), and no firestore.rules exists.

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.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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions