Frequently asked questions
Short answers to the questions that come up most often.
Does this work with Expo Go?
Auto-discovery does not, because Expo Go's Info.plist doesn't declare _rexpo._tcp. Use a dev build, or fall back to manual wsUrl mode which works in Expo Go too.
Will this end up in my production app?
No. The agents only run when __DEV__ is true. The Expo config plugin is a no-op when EAS_BUILD_PROFILE === "production". No Bonjour services, no local-network permission, no runtime code reaches your release build.
Does it work over cellular or different Wi-Fi networks?
No. Auto-discovery is local-network only. The device and the desktop have to be on the same network. If you need to debug across networks, use manual wsUrl with a reachable address (e.g. via ngrok).
Can I capture XMLHttpRequest or WebSocket traffic?
Not yet. Today the network agent covers fetch and axios. XHR and WebSocket monitoring is on the roadmap.
Does it support custom axios instances?
Yes. Call addAxiosInstance(yourClient) after initNetworkAgent and it will be patched alongside the global one.
Is there telemetry?
No. The desktop app does not phone home. All traffic stays between the agent and the desktop over your local network.
Is it free?
Yes — MIT-licensed, fully open source. Contributions welcome.
Why "Rexpo"?
React + Expo. The smallest, ugliest name that survived a whiteboard session.