We still expect all Tasks where progressMinutes >= 60.
What is the need/purpose of .subscrbe in the first example? Either way, the expected result is the same. Why does .subscribe() need to be implicitly specified?
. subscribe tells the server which data to send the client. The local results are the same, but if you don’t subscribe, the server will not send you any data.
Well, hmmm. Our testing shows that with NO subscription, our app still receives events and data. It’s very confusing. Here’s our code that opens flex Realm. Note that the subscription section is commented out. There is NO other code in the app that does anything with opening the Realm.
When this code is run, if I open the Realm Console and manually add data, it’s immediately sent and sync’d with the client - and vice-versa. When a ToDo is added on the client it’s immediately pushed to Atlas.
So in spite of having no subscriptions, the app still receives data.
What is going on? .subscribe is not used anywhere in the app.
Subscriptions are persisted in the Realm and will be used between app restarts. If you had setup subscriptions previously, it’s possible that they are responsible for the data synchronization you’re observing. You can check what subscriptions are already setup for a Realm by accessing the realm.subscriptions property.