Closed ryanramage closed 6 years ago
So many things can cause websocket issues.
Regardless you should await client.subscribe()
.
thanks. good catch.
ok, changes made, and still getting the same behaviour.
I understand that websockets can be flaky. We are in a pretty stable local dev environment, so we are ruling out mobile connectivity/reconnect issues.
Only other thing I can think of is we have an older hapi version (13.5.3). Maybe there is some interplay with that causing issues. I will try and upgrade.
Which version of nes are you using? Did you check all the bug fixes since then?
both client and serve are at nes@9.0.1.
I'm sorry, i am jumping ship to use the ws module direct. I will leave my branch of my app available if you want me to test anything.
And I appreciate you being responsive to my issue. If there is anything else to provide you with, let me know.
nes 9 doesn't work with hapi 13. It requires hapi 17. Not sure what you are doing there. Closing since you are no longer using it.
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
I am trying to use nes, and it nice because it was so easy to set up.
Issue is some publish payloads dont get to the subscriber. Usually for sure the first one or two get delivered, but some subsequents ones dont, and then later on they will. No idea why.
code snips (both client and serve are at nes@9.0.1)
Server
Client