Angular:: 4.3.4
Firebase: 4.6.0
AngularFire: 5.0.0-rc.4
It also happens with Angular 5.0.2 && firebase 4.6.2, but the Stackblitz provided runs those versions
Failing test unit, Plunkr, or JSFiddle demonstrating the problem
https://stackblitz.com/edit/angular-yhbuma
Image:

Steps to set up and reproduce
The items get deleted, but the rest of the list starts to disappear (not being deleted though).
* Errors in the JavaScript console *
No errors in the console.
The item I choose to delete is deleted, and the list is updated with the same number of items determined by the pageLimit.
The items of the list start to disappear randomly. If you delete cache/cookies or use incognito, the items are retrieved normally, unless you delete again an item.
The previous example works If I use the async pipe instead of subscribing. But it fails again in the same way if I add another query to the same path, but this time to count the total items.
Here is the Stackblitz: https://stackblitz.com/edit/angular-fl45ty
@diegotham Thank you so much for the detailed bug with the Stackblitz! This made it so much easier to troubleshoot.
This is a tricky bug, but I'm on the case. I'll get back to you as soon as I have more information.
@diegotham I have the same problem. Then I read document as below https://firebase.google.com/docs/firestore/manage-data/delete-data ,and I try this.afs.collection('categories').doc(pathOfdoc).delete();, this works.
So, I using is .snapshotChanges()It returns an array with a lot more information. Then you can use a map operator to get the data and the object Id from the array.
Hey guys, any news about this issue?
Hello everyone, is this issue has been resolved ?
Hi @davideast, any news about this issue?
This is due to multiple subscribes on a valueChanges + everything gltiching our with multiple listeners and conflicting data, you'll need to lean on rxjs more. If you update your stackblitz with project credentials, I'll fork and show you a fix.
Most helpful comment
@diegotham Thank you so much for the detailed bug with the Stackblitz! This made it so much easier to troubleshoot.
This is a tricky bug, but I'm on the case. I'll get back to you as soon as I have more information.