java.lang.IllegalArgumentException Tcp Sockets: No socket with id

[pajkho]

java.lang.IllegalArgumentException Tcp Sockets: No socket with id

[Rapsssito]

@pajkho, this is a common issue if you are trying to use the socket while it has not established a connection yet. Make sure you wait for the connection callback before using the socket.

[pajkho]

The issue arises for us when having continuous writes to the tcp connection which doesn't stop until the end event happens. If the connection closes there can be a gap between the close of the connection and the end event where there is new writes which causes this error and the app crashes.

Wouldn't it be more reasonable to try/catch this to prevent the app from crashing and instead call the error event? It shouldn't be possible to crash the app because you mistakenly try to write to a closed connection.

[Rapsssito]

@pajkho, indeed, I will release a fix ASAP.

[github-actions]

🎉 This issue has been resolved in version 6.0.6 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀