Replies: 2 comments
-
Not all transports are fully compatible with react native at the moment, it may be more appropriate to raise this as an issue on the react-native-repo |
Beta Was this translation helpful? Give feedback.
0 replies
-
Issue has been raised here ipfs-shipyard/js-libp2p-react-native#7 with a bounty. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently trying to connect alice (node.js or react-native - behind NAT) and bobs (node.js - public IP) via webrtc through a circuit relay server (node.js - public IP)
I cannot hardcode bobs multiaddr as many bobs may exist in my network. Only the circuit relays can be hardcoded.
Say I have a connection through a circuit relay with an example connection multiaddr like so
/ip4/${ip_address}/tcp/${port_number}/ws/p2p/12D3KooWSFr7xJnyREpieyX5sGw2mCzc4k6LEa2KEBkXNhYXoVhB/p2p-circuit/webrtc/p2p/12D3KooWDYhZLWM7XagHSf9HSZT338UN9LesS1ckQRhdnnQSSkk6
Dialing the peer simply returns the same connection multiaddr type (p2p-circuit/webrtc)
let res = await node.dial(connection?.remoteAddr);
I am expecting a webrtc connection so I can negotiate a webrtc protocol. Here is an example of what I am expecting to pass.
Edit
The following works from node.js alice but not react-native alice. It seems as though webRTC is broken with React-native.
Beta Was this translation helpful? Give feedback.
All reactions