-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial progress listener callback does not trigger when waiting for initial remote data #6976
Comments
➤ Christan Melchior commented: Not 100% sure what this is about. [~claus.rorbech] can you clarify? |
The convention is that registering a progress listener should yield an immediate callback with the current state. This does not seem to happen when using the Basically just an issue tracking the failing test in https://github.com/realm/realm-java/blob/v10/realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/ProgressListenerTests.kt#L278 |
➤ Claus Rørbech commented: Even though the stack trace provided in https://jira.mongodb.org/browse/HELP-17846 indicates that this is related to sync not progressing, it could also be related to https://jira.mongodb.org/browse/ROBJSTORE-98? |
➤ Claus Rørbech commented: Seems to be the second case of realm/realm-core#4302 |
➤ Paolo Manna commented: [~claus.rorbech] Is this now considered solved? Any changes to the SDK? |
➤ Claus Rørbech commented: [~paolo.manna] The fix is on the cloud side, so no need to update. That said, I haven't verified it yet, but am in the process of verifying it with our integration tests. |
➤ Paolo Manna commented: [~claus.rorbech] Great, thanks, let me know the outcome, so that I can confidently update the customer about it! |
When opening a synced realm with the
waitForInitialRemoteData
options there is no initial callback to following registered progress listeners.The text was updated successfully, but these errors were encountered: