Firebase Auth: can't delete Firestore documents in promise returned from currentUser.delete()

Question

I am using firebase authentication and angularfirestore in my app, and I came across a strange problem. I want to delete a user document in firestore after I delete the user in firebase auth as shown below, but the firestore portion doesnt work.

Edit 2: In the code, this.currentUser is not the same as angularFireAuth.auth.currentUser. It is a local variable I created separately.

return this.angularFireAuth.auth.currentUser.delete().then(() => {
            this.angularFirestore.collection("userData").doc(this.currentUser.email).delete().then(() => {
                this.currentUser = null;
                this.currentUserSubject$.next(this.currentUser);
                this.setAuthenticationDetails({authType: null, rememberMe: false});
                this.storageService.setRememberedUser(null);
            });
        })

However, if I were delete the document from firestore first, and delete the user from firebase auth afterwards, it works.

return this.angularFirestore.collection("userData").doc(this.currentUser.email).delete().then(() => {
            return this.angularFireAuth.auth.currentUser.delete().then(() => {
                this.currentUser = null;
                this.currentUserSubject$.next(this.currentUser);
                this.setAuthenticationDetails({authType: null, rememberMe: false});
                this.storageService.setRememberedUser(null);
            });
        })

Anyone knows why this is happening? They both return promises so i expected the behaviour to be the same.

Edit 1: added catch, but nothing's being printed

return this.angularFireAuth.auth.currentUser.delete().then(() => {
            return this.angularFirestore.collection("userData").doc(this.currentUser.email).delete().then(() => {
                this.currentUser = null;
                this.currentUserSubject$.next(this.currentUser);
                this.setAuthenticationDetails({authType: null, rememberMe: false});
                this.storageService.setRememberedUser(null);
            }, (error) => {
                console.log(error);
            });
        }, (error) => {
            console.log(error);
        })

Edit 3: Security Rules

rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /{document=**} {
      allow read, write: if true;
    }
  }
}

Doug Stevenson · Accepted Answer · 2020-08-05 14:42:44Z

1

What you're observing makes sense to me.

If you have security rules set up on Firestore that require an authenticated user in order to delete the documents, it makes sense that the documents would fail to delete after removing the user account (as the user is not longer authenticated). You will definitely want to do everything you can while authenticated before signing out or deleting the user account.

You should add error checking to your code to find out if anything went wrong with the document delete. Right now, you don't have any catch callbacks on the promise chain, so you'd never know if something went wrong. I suspect you'll see a "permission denied" type of error on the document delete due to security rules rejecting the request.

answered Aug 5, 2020 at 14:42

Doug Stevenson

321k37 gold badges458 silver badges474 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Daruul Over a year ago

Hi, i added the catch callbacks, but in the console nothing is being printed (which is very strange, since I'd expect some error if the request is not going through?). Also, I don't have any security rules that require users to be authenticated

RameshD Over a year ago

Even if you have not written security rules on your own, it might have security rules like below created on project creation. So be mindful about that. Daruul makes perfect sense in his comment and we can not perform operation if user is not logged if security rules exits. firebase.google.com/docs/firestore/security/get-started

Daruul Over a year ago

My security rule allows for all operations so can't be that

Doug Stevenson Over a year ago

Please edit the question to show your security rules.

Doug Stevenson Over a year ago

If you don't get some sort of result after a document write, then you should file a bug with angularfire with your specific steps to reproduce.

|

Ashely Shu · Accepted Answer · 2020-08-05 15:46:20Z

0

I think what happened is that after you do auth.currentUser.delete(), this.currentUser also gets cleared (if it holds auth.currentUser)

So you are just deleting doc("") which didn't fail. But there is no such document, so you won't see anything.

answered Aug 5, 2020 at 15:46

Ashely Shu

136 bronze badges

1 Comment

Daruul Over a year ago

Thats my bad, I didn't make it clear that this.currentUser is a local variable that isn't affected by auth.currentUser(). I've tested it with console.log and this.currentUser isn't null, hence why I asked this. Really confused

Collectives™ on Stack Overflow

Firebase Auth: can't delete Firestore documents in promise returned from currentUser.delete()

2 Answers 2

6 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

6 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related