Missing notifications after client reset.

[clementetb]

Expected results

Get a change notification on an object collection after manually recovering some data during a discard local changes client reset.

Actual Results

We don't get a notification. If we commit an empty transaction then the notification is propagated with the changes done in a previous transaction.

Steps & Code to Reproduce

1. Add a listener to an object collection.
2. Trigger discard local client reset.
3. At onAfter write some data to the -before- after Realm.
4. No notification is received for that new data.

Core version

Core version: 13.23.1

[sync-by-unito[bot]]

➤ danieltabacaru commented:

[[email protected]] Is this something that may be fixed by your latest work on client reset?

[tgoyne]

Possibly, but this isn't specifically one of the bugs I've seen. Still probably doesn't make sense to try to work on this until after #7161 is done.

[danieltabacaru]

Right. Thanks for the heads up.

[sync-by-unito[bot]]

➤ danieltabacaru commented:

[[email protected]] I can try reproducing this, but by just looking at the code before realm in onAfter callback is frozen, so attempting to create a transaction on that realm should crash the app. Isn't that the case?

[sync-by-unito[bot]]

➤ danieltabacaru commented:

Waiting for Clement to answer.

[sync-by-unito[bot]]

➤ clementetb commented:

My bad, I meant the after realm instance.