Incorrect sorting behavior, first record always positioned at the end v8.0.2.

[heliomarpm]

Hello, after upgrading from v7.24.0 to v8.0.2, all the compositions are showing incorrect behavior, the first record is always being returned in the last position.

this.fireStore.doc(Users/${this.userId}) .collection<Card>('Cards', ref => ref.where('active', '==', true) .orderBy('order') .orderBy('createdAt', 'desc'));

Example: {order: 1, condition2: 'AA' ...} {order: 2, condition2: 'BB' ...} {order: 3, condition2: 'AB' ...} {order: 4, condition2: 'DD' ...} {order: 3, condition2: 'AB' ...}

Return: {order: 2, condition2: 'BB' ...} {order: 3, condition2: 'AB' ...} {order: 3, condition2: 'AB' ...} {order: 4, condition2: 'DD' ...} {order: 1, condition2: 'AA' ...}

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[atsjo]

Saw similar behavior going from 8.0.1 to 8.0.2, in addition to problems propagating updates in my angular app... Downgrading to 8.0.1 fixes the problem...

[heliomarpm]

Saw similar behavior going from 8.0.1 to 8.0.2, in addition to problems propagating updates in my angular app... Downgrading to 8.0.1 fixes the problem...

I am working with ionic 5 + angular. I also had a propagation problem in version 8.0.2, my solution was to go back to 8.0.0.

[wu-hui]

I believe the issue is from angularfire, filed a issue there: https://github.com/angular/angularfire/issues/2657

[jamesdaniels]

If it is AngularFire it's not 2657. As developers are reporting that they started encountering it with 8.0.2 IMO it's probably the JS SDK.

[wu-hui]

@jamesdaniels Thanks!

@heliomarpm I tried reproduce with angularfire and could not reproduce. Can you kindly provide a mini repro? This would greatly help me identifying the root cause quicker.

[schmidt-sebastian]

This looks like https://github.com/firebase/firebase-js-sdk/issues/4079

@jamesdaniels Does AngularFire use oldIndex or newIndex from DocumentChange?

[jamesdaniels]

@schmidt-sebastian I suspect you're right, AngularFire and RxFire use both old/newIndex: AngularFire combineChange, RxFire processIndividualChange