Troubleshooting Connection Issues

Solutions for common SDK-to-Desktop connectivity problems.

Device Not Appearing in Desktop

Check 1: Is the Desktop App running?

The Desktop App must be started before the mobile app. The WebSocket server starts on port 9333 at launch.

Check 2: Is debug mode enabled?

// Recommended: debug: true in init()
await WhatzBug.init({
  projectId: 'your-project-id',
  publishableKey: 'pk_your_key',
  apiBaseUrl: 'https://api.whatzbug.com',
  debug: true,
});

// Legacy alternative (still works):
// WhatzBug.enableDebug({ appName: 'My App' });

Check 3: Correct host for your connection type?

ScenarioExpected HostHow to Set
Android Emulator10.0.2.2 (auto)Default — no config needed
USB Devicelocalhostadb reverse tcp:9333 tcp:9333
Wi-Fi DeviceYour machine IPhost: '192.168.x.x'
iOS Simulatorlocalhost (auto)Default — no config needed

Check 4: Port conflict?

lsof -i :9333

Check 5: ADB reverse (USB Android)

adb reverse tcp:9333 tcp:9333
adb reverse --list

Device Connects Then Disconnects

Likely cause: Heartbeat timeout. The SDK and Desktop exchange ping/pong messages every 10 seconds. Check that your network allows sustained WebSocket connections.

No Data in Panels

  • Verify debug mode is enabled (debug: true in init, or enableDebug() called after init)
  • Check device capabilities in the Connection Panel
  • Interact with the app — panels show live data, not history before connection

SDK Build Errors

Cannot find module '@whatzbug/react-native'

Run npm install again. For iOS, run cd ios && pod install.

Related