Open arupadhy opened 5 years ago
This happens with node 8 also (recently), they (Apple) changed something ... again ..
Could be an intermittent issue with Apple's servers. I haven't noticed issues personally.
Perhaps apple fixed it on their end?
@andreialecu i think the library isn't handling scenarios where 'other end of socket is abruptly closed'....I see an open pull request that tries to catch the error at 'session' level...that fixes the problem of other apps (depending on this library) not to register events at process level.
Would be better to simply reject the promise for such cases (might require little bit of refactoring)...Let me know if you are open to reviewing a mr
we started noticing this after upgrade to node 10 I am digging more into this library code base...Is there a recommended way to avoid econnreset if other end of tcp socket is closed abruptly?