Does not work on real devices unless IP is set to Device running DevTools

[ShoeBoom]

Currently to test on a physical device we need to change the IP, this is not ideal in a collaborative environment

  useSyncQueriesExternal({
    queryClient,
    socketURL: "http://192.xxx.xx.xxx:42831",
    deviceName: Platform?.OS || "web",
    platform: Platform?.OS || "web", 
    deviceId: Platform?.OS || "web", 
    extraDeviceInfo: {
      appVersion: "1.0.0",
    },
    enableLogs: false,
  });

Would it be possible to perhaps do a port scan for 42831 over local network? There would be some security issues but maybe we could add a confirmation on the device with a key that's saved to DevTools?

I would be open to helping on this, unless it's already in the works

[LovesWorking]

Currently to test on a physical device we need to change the IP, this is not ideal in a collaborative environment

  useSyncQueriesExternal({
    queryClient,
    socketURL: "http://192.xxx.xx.xxx:42831",
    deviceName: Platform?.OS || "web",
    platform: Platform?.OS || "web", 
    deviceId: Platform?.OS || "web", 
    extraDeviceInfo: {
      appVersion: "1.0.0",
    },
    enableLogs: false,
  });

Would it be possible to perhaps do a port scan for 42831 over local network? There would be some security issues but maybe we could add a confirmation on the device with a key that's saved to DevTools?

I would be open to helping on this, unless it's already in the works

Sounds awesome. I haven't thought about using it on a real device yet. You could make a helper function to do this and just pass it to this hook? Once that's done you can either make a PR or provide the code and I'll add it in.

Great idea thank you!

[ShoeBoom]

Ok so i did a bit more research on IP spaces. Turns out 192.168.0.0/16 has 65,536 addresses.

You could get the physical device's IP and narrow it down to 256 addresses (192.168.XX.0 - 192.168.XX.0) assuming:

1. XX is the same for both devices.
2. user is not using 172.16.0.0/12 or 10.0.0.0/8 which have over a million addresses

and with those caveats I can't find a way to get the device's IP without some other native dependency so i don't like this.

I decided to use the IP provided by the expo debugger instead.

import Constants from "expo-constants";

const hostIP =
  Constants.expoGoConfig?.debuggerHost?.split(`:`)[0] ||
  Constants.expoConfig?.hostUri?.split(`:`)[0];

  useSyncQueriesExternal({
    queryClient,
    socketURL: `http://${hostIP}:42831`, // Default port for React Native DevTools
    deviceName: Platform?.OS || "web", // Platform detection
    platform: Platform?.OS || "web", // Use appropriate platform identifier
    deviceId: Platform?.OS || "web", // Use a PERSISTENT identifier (see note below)
    extraDeviceInfo: {
      // Optional additional info about your device
      appVersion: "1.0.0",
      // Add any relevant platform info
    },
    enableLogs: false,
  });

if anyone still want's to work on the scanner here is what i got to https://gist.github.com/ShoeBoom/709899e46129d25f211447bc90d615cf

[LovesWorking]

https://gist.github.com/ShoeBoom/709899e46129d25f211447bc90d615cf

Thanks for the update! I'll add that to the docs. Yea, an alternative I've done before is hosting the dashboard on your server as well and then it works no matter what.