supabase-node-chat-backend VS react-native-webrtc

Node - https://github.com/nsmet/supabase-node-chat-backend/blob/main/src/utils/socket.ts

You can see the full code for the react native app here and the full code for the backend here

{ "name": "supabase-node-chat-backend", "version": "1.0.0", "description": "Node backend for a chat application, using Supabase", "main": "index.ts", "scripts": { "start": "nodemon -r dotenv/config src/index.ts", "lint": "eslint . --fix", "test": "echo \"Error: no test specified\" && exit 1" }, "repository": { "type": "git", "url": "git+https://github.com/nsmet/supabase-node-chat-backend.git" }, "keywords": [ "supabase", "node", "chat" ], "author": "Nick Smet", "license": "ISC", "bugs": { "url": "https://github.com/nsmet/supabase-node-chat-backend/issues" }, "homepage": "https://github.com/nsmet/supabase-node-chat-backend#readme", "dependencies": { "@supabase/supabase-js": "^2.4.1", "body-parser": "^1.20.1", "dotenv": "^16.0.3", "express": "^4.18.2", "socket.io": "^4.5.4" }, "devDependencies": { "@types/express": "^4.17.15", "@types/node": "^18.11.18", "@typescript-eslint/eslint-plugin": "^5.48.2", "@typescript-eslint/parser": "^5.48.2", "eslint": "^8.32.0", "nodemon": "^2.0.20", "ts-node": "^10.9.1", "typescript": "^4.9.4" } }

Hi, I am using react-native-webrtc along with react-native-simple-peer for my webrtc video calls. I tried using a custom turn server and twilio's servers as well. All the servers that I am using give IceGatheringState: complete on this website, so I feel that the servers are working fine. I am unable to connect the calls whenever I'm using mobile data or am on different networks and get the error Ice Connection failed. Have tried toggling values for trickle and also tried completely relying on the turn severs by using iceTransportPolicy: 'relay'. Have beat my head for quite some time regarding the solution for this and would appreciate any help, thanks!

I think WebRTC could be an alternative; it requires a signalling server and more manual setup, but at least with this—you don't get unexpected bills—the only thing that could go wrong is your signalling server crashing, but downtime shouldn't matter in this case. The other thing to consider is the effort it takes to go down this route & maintenance.

heres the stuff that IS available in the expo sdk: https://docs.expo.dev/versions/v47.0.0

You then use 3rd party modules (or build your own) for anything else you need. For example, webtrc: https://github.com/react-native-webrtc/react-native-webrtc

Maybe using WebRTC Data Channels, https://github.com/react-native-webrtc/react-native-webrtc/blob/HEAD/Documentation/BasicUsage.md

I am building a react native application using Expo and i need to add audio calling and video calling functionalities, however it seems that i cant use react-native-webrtc (Link here) without ejecting Expo.