-
Notifications
You must be signed in to change notification settings - Fork 189
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
requestHistoryForChannel: callback never called #65
Comments
Hi @vvit Did you called connect method of PubNub singleton? Best regards, |
During the initialisation phase I call connect block:
and get the error:
After that I call [PubNub requestHistoryForChannel:...] which is causing a problem I described. |
Well, it has been designed this way. Initial connection failure will stack further requests till internet connection restore (special case). If connection will go down after successful connection, it will report errors. |
All right, so I guess I need to check these conditions before making the On 28 трав. 2014, at 18:21, Sergey notifications@github.com wrote: Well, it has been designed this way. Initial connection failure will stack — |
Hi. I use that call to get the channel history:
But it seems if there's no Internet connection (airplane mode) the completion block is never called.
Can you check that?
Thanks a lot.
The text was updated successfully, but these errors were encountered: