@libp2p/tcp No Longer Supported in React Native

[palmtown]

• Version:
  "@libp2p/tcp": "^10.0.19",
  "libp2p": "^2.6.2",
  "react-native-tcp-socket": "^6.2.0",

• Platform:
  64-bit (Windows)

• Subsystem:
  @libp2p/tcp

Severity:

Medium

Description:

In React Native 0.77.0, the following errors occur, making the TCP transport unusable. Previously, @libp2p/tcp appeared to work, as referenced in the repository: https://github.com/ipfs-shipyard/js-libp2p-react-native.

1. Adding tcp() to the transports key in the createLibp2p functions generates the below error in Exhibit 1 below.
2. Commit dd7b329, which introduced the code in Exhibit 2, causes react-native to fail as it defaults to the tcp.browser.js code.

Exhibit 1
TypeError: The listener must be a function at addListener (http://10.0.2.2:8081/node_modules\react-native-tcp-socket\node_modules\eventemitter3\index.bundle//&platform=android&lazy=true&app=com.reactnativep2p&modulesOnly=true&sourcePaths=url-server&dev=true&minify=false&runModule=true&shallow=true:61:26)

Exhibit 2
"browser": { "./dist/src/tcp.js": "./dist/src/tcp.browser.js" },

Steps to reproduce the error:

Create a react-native project, and add tcp() to the list of transports

[abuvanth]

yes same issue

[abuvanth]

@palmtown can i use old version of @libp2p/tcp lib for latest libp2p lib to make this works?

[palmtown]

@palmtown can i use old version of @libp2p/tcp lib for latest libp2p lib to make this works?

Hello @abuvanth

Good question! I tried an older version. However, I was unable to get it to work. Nonetheless, I only tried one. Therefore, it's a possibility.

[abuvanth]

when npm release of this fix

[palmtown]

Hello @achingbrain,

Thanks for the quick fix in @libp2p/tcp—much appreciated!

However, issue #1 from Exhibit #1 still persists. After debugging, I traced the problem to react-native-tcp-socket. Just as I was about to submit a report, I found your existing issue from 2023: react-native-tcp-socket#183.

Since this issue remains unresolved, do you have any workarounds?

@abuvanth, even with the fix here, the problem persists. The react-native-tcp-socket createServer function is not aligned with net.createServer, as detailed in react-native-tcp-socket#183.

I haven't found a workaround yet, but if you do, please share!

[achingbrain]

I don’t have a workaround, no.

If you want to see it working, could you submit a PR to react-native-tcp-socket with a fix?

It should be relatively straightforward to interpret the function args.

[palmtown]

I don’t have a workaround, no.

If you want to see it working, could you submit a PR to react-native-tcp-socket with a fix?

It should be relatively straightforward to interpret the function args.

Hello @achingbrain ,

I've successfully added support for the options parameter, enabling react-native-tcp-socket to initiate a connection to the relay server. However, the connection fails with the following error: libp2p:tcp:socket:error encrypting inbound connection from /ip4/X.X.X.X/tcp/58057 failed UnexpectedEOFError: unexpected end of input.

I'm seeking assistance to resolve this issue. To expedite a solution, I've posted a $300 bounty here: Rapsssito/react-native-tcp-socket#209.

If you or someone you know can help, please refer to the link above.

Thank you