No longer notify RealmResults changes from other clients

[jumilla]

Synchronized Realm (using MongoDB Realm) no longer notify of RealmResults changes from other clients on Core version 11.4.1.

It have been notified of myself updates.

I have confirmed that the change-set has been downloaded from sync server in a sync log.
I have confirmed that it works on Core version 11.3.1.

Maybe it's due to the following Pull Request:
#4839

Expected results

Realm sync client notifies RealmResults changes from other clients.

Actual Results

Realm sync client doesn't notify RealmResults changes from other clients.

Core version

Core version: 11.4.1

[jumilla]

There are sync-logs.
It has been slightly processed to protect environmental information.

-- Sync Log - Core version: 11.4.1 on Client A
[RealmSync] 1 Connection[1]: Changeset (parsed):
InternStrings 0="AppReport"
EraseObject path=AppReport[ObjectId{6145485b4fbcbb18bf9.....}]

[RealmSync] 2 Connection[1]: Session[1]: Received: DOWNLOAD(download_server_version=23, download_client_version=0, latest_server_version=23, latest_server_version_salt=..., upload_client_version=11, upload_server_version=22, downloadable_bytes=0, num_changesets=1, ...)
[RealmSync] 2 Connection[1]: Session[1]: 1 remote changeset integrated, producing client version 12
[RealmSync] 2 Connection[1]: Session[1]: Sending: UPLOAD(progress_client_version=12, progress_server_version=23, locked_server_version=23, num_changesets=0)
[RealmSync] 2 Connection[1]: Session[1]: Progress handler called, downloaded = 10539, downloadable(total) = 10539, uploaded = 0, uploadable = 0, reliable_download_progress = true, snapshot version = 12

-- Sync Log - Core version: 11.3.1 on Client B
[RealmSync] 1 Connection[2]: Changeset (parsed):
InternStrings 0="AppReport"
EraseObject path=AppReport[ObjectId{6145485b4fbcbb18bf9.....}]

[RealmSync] 2 Connection[2]: Session[2]: Received: DOWNLOAD(download_server_version=23, download_client_version=0, latest_server_version=23, latest_server_version_salt=..., upload_client_version=32, upload_server_version=22, downloadable_bytes=0, num_changesets=1, ...)
[RealmSync] 2 Using already open Realm file: [WorkingDirectory]/mongodb-realm/.../%22office%22.realm
[RealmSync] 2 Connection[2]: Session[2]: 1 remote changeset integrated, producing client version 33
[RealmSync] 2 Using already open Realm file: /mongodb-realm/.../%22office%22.realm
[RealmSync] 2 Connection[2]: Session[2]: Sending: UPLOAD(progress_client_version=33, progress_server_version=23, locked_server_version=23, num_changesets=0)
[RealmSync] 2 Using already open Realm file: [WorkingDirectory]/mongodb-realm/.../%22office%22.realm
[RealmSync] 2 Connection[2]: Session[2]: Progress handler called, downloaded = 10539, downloadable(total) = 10539, uploaded = 0, uploadable = 0, reliable_download_progress = true, snapshot version = 33
[RealmSync] 2 Using already open Realm file: [WorkingDirectory]/mongodb-realm/.../%22office%22.realm
[RealmSync] 2 Connection[2]: Session[2]: Progress handler called, downloaded = 10539, downloadable(total) = 10539, uploaded = 0, uploadable = 0, reliable_download_progress = true, snapshot version = 33

[jedelbo]

@tgoyne could you have a look at this to see if this could be caused by the change that is mentioned?

[jumilla]

@tgoyne could you have a look at this to see if this could be caused by the change that is mentioned?

Why don't you reply for this issue.

Changing on realm-cocoa is not an essential solution.

Bugs on realm-core, still remain.

[jumilla]

@jedelbo Thanks!

[tgoyne]

I don't see any reason to think that #4839 is related or that there's a core bug here.

[jumilla]

@tgoyne

This issue is not a phenomenon that only appears in 'realm-cocoa', so you will need to verify it in libraries for other language as well.

[nirinchev]

@jumilla have you experienced the issue with other SDKs? If so, please file an issue in the relevant SDK's repository. Per Thomas's investigation, this was caused by a bug in realm-cocoa which is now fixed.

[jumilla]

@nirinchev Where was the cause in realm-cocoa?
Thomas does not explain clearly.

[nirinchev]

It's in the linked PR from this issue:

If you navigate to the PR you can see what the cause of the issue was and how it was resolved.