You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 17, 2019. It is now read-only.
In MeteorClient.m, removeSubscriptions: returns immediately if it's not okay to send. But in addSubscription: it first adds to the _subscriptions and _subscriptionsParameters dictionary before checking if it's okay to send.
In the case of no connection, after calling addSubscription:
-This ends up allowing for a later callback for a subscription that shouldn't exist (when connection is established).
-Or if removeSubscription: is called, it still allows for the callback (when connection is established).
Please let me know if I am/not reading this correctly. This scenario is causing my callback to function when I wouldn't think it would, since it's not allowing me to remove the subscription.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In MeteorClient.m, removeSubscriptions: returns immediately if it's not okay to send. But in addSubscription: it first adds to the _subscriptions and _subscriptionsParameters dictionary before checking if it's okay to send.
In the case of no connection, after calling addSubscription:
-This ends up allowing for a later callback for a subscription that shouldn't exist (when connection is established).
-Or if removeSubscription: is called, it still allows for the callback (when connection is established).
Please let me know if I am/not reading this correctly. This scenario is causing my callback to function when I wouldn't think it would, since it's not allowing me to remove the subscription.
The text was updated successfully, but these errors were encountered: