Rodrigo Martín comments

Results 60 comments of


                                            Rodrigo Martín

fix(Android): Add missing timeout argument to socket.connect()

@jesperjohansson, thanks for the PR! However, the timeout has been moved to the JS part of the code, as you can see here: https://github.com/Rapsssito/react-native-tcp-socket/blob/c68215ca5e8d196cb069c6d8cfc3817fe3f28f4a/src/Socket.js#L153-L169

fix(Android): Add missing timeout argument to socket.connect()

@jesperjohansson, I didn't know that was happening. Then there must be a bug in the JS code.

fix: crash on write if socket is null

@cc-steina, thanks for the PR! However, this does not fix the root cause of the issue. Can you when the socket is being set to null after the server disconnection?

[iOS] server.close() callback never fires

@rkeiii, thanks for the feedback! I will release a fix ASAP

fix a bug of socket.write function

@itgou, thanks for the PR! However, while this is correct as implementation, it must also be reflected in the type declaration file for the Typescript users. If you do not...

[ios] [5.3.1] rare crash when going from background to foreground

@Overtorment, thanks for the feedback! iOS has a very special way of dealing with sockets when an app is in the background, which may be the root cause of this...

[ios] [5.3.1] rare crash when going from background to foreground

@Overtorment, could you tell me if you are using an HTTPS connection and if you are sending data when the app is in the background?

Host not reachable error handling

@sudray, I am sorry for your issue. Could you provide a minimal reproducible example code so I can test it in my local setup?

Host not reachable error handling

@Mohamed-kassim, sorry for my late reply. I am working on handling the same errors on iOS and Android. I will close this issue as soon as this is fixed!

Connection Success or Error not emitted from iOS for the first time in iOS 14 and above

@itzsankar, does this issue also occur with simulated devices?