-
Notifications
You must be signed in to change notification settings - Fork 165
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
Incorrect Subscriptions.State #3180
Comments
Can you share the exact code you're using? Generally speaking, the state would be complete if:
If your use case falls under any of these cases, then this is the expected behavior. |
@nirinchev I open the database with the following config:
as you can see, I have Subscriptions, and considering that the use case I reported is observed even on network loss, there is absolutely no way for realm to ascertain that the sync is complete, it has to connect to server to do that. |
There are two things to consider here:
|
That's interesting, yes, this is exactly the case, but that's not what I would expect from that method, because my app subscribes to essentially all of the entities with So, in my case, there is no way to wait for the changes, is there? Or should I use |
Correct - if a subscription is in a |
@nirinchev Is this also by design? That SyncSession is Active despite being in the Airplane mode? |
Yes, the session state indicates whether the session is attempting to communicate with the server. You are probably looking for ConnectionState which should indicate whether there's connection to the server. |
What happened?
realm.Subscriptions.State is set to Complete even when the network is down
Repro steps
After getting a realm instance, log
realm.Subscriptions.State
while network is down.Version
.NET 6
What Atlas Services are you using?
Atlas Device Sync
What type of application is this?
Other
Client OS and version
Windows 10
Code snippets
No response
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: