Skip to main content
Simulators and emulators are fine for app and SDK wiring. They do not reproduce Bluetooth LE, Wi-Fi Direct or a browser mesh on a real network, so a green simulator build shows that the binding compiles and the basic calls work, not that devices reach each other. Test the mesh on two physical devices, or two hosts for Python, before you treat it as done.

What to run where

Milestones

A. Wiring (a simulator or one device). Install the SDK for your platform, follow the lifecycle order (listeners, then start(), then sends), make mesh-sdk-doctor pass on React Native, and launch one native build. B. Mesh smoke (hardware, or two hosts).
  1. Two peers discover each other over the configured transports.
  2. The session is confirmed on both sides: secure_session_established on a first pairing, or getEstablishmentState reporting SessionConfirmed on a repeat run (offline-protocol-verify pair on the local API). A session restored from storage at start() emits no new event, so waiting for one on devices that already paired looks like a failure.
  3. A message makes the round trip with encryption on, the default.
  4. On the local API, offline-protocol-verify pair, send and await succeed.
C. Release. Check the permissions and entitlements for every transport you ship on the devices you support, test the upgrade from the version your users run (see upgrade the SDK), and run the browser two-device checklist if you ship browser nodes.

Golden paths

The SDK’s integration testing matrix lists the automated tests in the SDK repository by layer. None of them replaces milestone B on physical radios.