Hi, we're seeing these errors being logged out in our application when working on features which involve different application lifecycle states (resumed/paused/terminated/inactive). I believe in this instance the flow went like this:
App opened, pusher connected and subscribed to channel successfully,
Screen locked with app in the foreground,
Pusher disconnected - everything is as expected.
We receive a call from some other user through call kit -> app is woken up in background,
Pusher reconnects, but we do not resubscribe to channel (only want to do that when screen is unlocked and app is resumed by user),
Caller ends call, call kit closes for receiver, app goes back to sleep/inactive state.
Unlock screen, app is in foreground and attempts to reconnect (disconnect, unsubscribe, subscribe, connect in this order),
Errors are seen in console.
After a while, it managed to connect successfully. Is there something implemented incorrectly on the app's side, or on the library's end? Thanks!
Hi, we're seeing these errors being logged out in our application when working on features which involve different application lifecycle states (resumed/paused/terminated/inactive). I believe in this instance the flow went like this:
After a while, it managed to connect successfully. Is there something implemented incorrectly on the app's side, or on the library's end? Thanks!