[React Native] Pusher going to the failed status after second time going offline

Do you want to request a feature or report a bug? Looks like a bug. Or I don’t understand the options of enabledTransports. What is the current behavior?

Current behavior

1. Use enabledTransports: ['ws', 'wss'], cause why not, seems logical
2. Connect to the pusher and check everything is fine
3. Go to airplane mode
4. Pusher recovering
5. Go to airplane mode again
6. Pusher going to the status failed and never recovering.

Repro (too much code for that example, but it works if you have Pusher key): https://snack.expo.io/@dmitrybirin/70d96d

Expected behavior Pusher recovering everytime or There is note in the documentation, that the enabled transports options could lead to not recovering from disconnection

Which versions of Pusher, and which browsers / OS are affected by this issue? Did this work in previous versions of Pusher? If so, which? Platforms: iOS and Android React Native 0.62.2 Pusher-js 6.0.3

It’s not a big of a problem itself, but really confusing and maybe could be indicator of other problems.

[dmitrybirin]

Hey @leesio! 👋 Sorry, missed the question. I’ve reproduced the same behaviour above with more than 2 minutes wait in the connected state. So, looks like, some transports missed life)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you’d like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you.