Firestore规则异常：读取正常但写入操作提示权限不足求助

Hey there, let's figure out why your Firestore write operation (addItem) is failing even though reads work perfectly. Here are the most common culprits and fixes to check:

1. Verify Your Firestore Rules Allow Writes #

First up, double-check your Firestore security rules—reads working means your read permissions are set correctly, but writes are likely locked down too tight or targeting the wrong path.

• Check if writes require authentication: If your rules look like this, you need to ensure the user is logged in before writing:

  match /items/{itemId} {
    allow read: if true; // Open for reads
    allow write: if request.auth != null; // Requires authenticated user
  }
  

  If your Angular app isn't authenticating the user before calling addItem, this will throw the permission error.

• Ensure path matches exactly: Make sure the collection path in your Angular code matches the path in your rules. For example, if your rules target /users/{userId}/items, but you're writing to /items in Angular, the permissions won't apply.

2. Confirm User Authentication State in Angular #

If your rules require an authenticated user, you need to make sure the user is fully logged in before attempting the write. It's easy to accidentally call addItem before the auth state has loaded.

• Wait for auth state to stabilize: Wrap your write operation in a subscription to the auth state to guarantee the user is authenticated:

  // In your Angular service
  import { AngularFireAuth } from '@angular/fire/compat/auth';
  import { AngularFirestore } from '@angular/fire/compat/firestore';
  
  constructor(private afAuth: AngularFireAuth, private afs: AngularFirestore) {}
  
  addItem(newItem: any) {
    this.afAuth.authState.subscribe(user => {
      if (user) {
        // User is authenticated—safe to write
        this.afs.collection('items').add(newItem)
          .then(docRef => console.log('Item added:', docRef.id))
          .catch(err => console.error('Write error:', err));
      } else {
        console.error('Cannot write: User is not logged in');
      }
    });
  }
  

3. Check for Rule Requirements on Document Fields #

Some Firestore rules enforce specific fields or values on write operations. For example, if your rule requires a createdAt timestamp set to the server time, you'll get a permission error if you don't include it.

• Example rule with field validation:

  allow write: if request.resource.data.createdAt == request.time;
  

• Fix in Angular: Include the required field using Firestore's server timestamp:

  this.afs.collection('items').add({
    ...newItem,
    createdAt: firebase.firestore.FieldValue.serverTimestamp()
  });
  

4. Use the Firestore Rules Simulator #

The Firebase Console's built-in Rules Simulator is your best friend here. It lets you test write operations directly and gives detailed feedback on why a rule is failing.

• Steps to use it:
  • Go to your Firebase Console → Firestore Database → Rules tab.
  • Click "Simulator" (top right).
  • Select "Create" as the operation, enter your collection path, and set the auth state (if your rules require it).
  • Run the simulation—the result will tell you exactly which part of your rule is blocking the write.

5. Ensure No Typos or Case Sensitivity Issues #

Firestore paths and field names are case-sensitive. Double-check that your Angular code uses the exact same collection name (e.g., Items vs items) and field names as your rules.

If you're still stuck, sharing your full Firestore rules code and the exact addItem method from your Angular service will help narrow down the issue even faster!

内容的提问来源于stack exchange，提问作者Atul Acharya