pubnub/swift

`connectionStatus` is `connected`, but messages are not received after internet connection manipulation

Opened this issue · 2 comments

akuzminskyi commented

Hi,
I'm testing some behaviors with/without internet connection. and sometimes I'm expecting an issue when connectionStatus is connected but messages are not received which is related to connection/disconnection which I'm testing. and after calling reconnect() it starts to work again.
The last status in didReceiveStatus is also connected

Initially, I thought to check if the connection is disconnected and call reconnect() after that but it didn't cover 👆 - I think it can be an issue somewhere.

So my question: is there any consequences/side effects if reconnect() is called more frequently even if the status is connected to cover 👆?

PubNubConfguration: automaticRetry: .default
I'll try to find steps to reproduce.

jguz-pubnub commented

Hi @akuzminskyi, could you provide steps to reproduce? There are no consequences if you don't do it very frequently. The request will be repeated with the last used timetoken, so you shouldn't miss these messages that weren't delivered due to issues regarding the internet connection.

  • 👍1
  • 👀1
jguz-pubnub commented

Also, the reason you don't get the error immediately after turning off your internet connection is because of the timeout value which is relatively large for the request we use under the hood. The question is, what happens if your internet connection is restored? Did the subscribe loop also restore?

  • 👀1