Documentation Index
Fetch the complete documentation index at: /docs/llms.txt
Use this file to discover all available pages before exploring further.
Diagnose Mesh SDK discovery, permissions, encrypted sessions, persistence and backend delivery problems, and collect the details support needs.
| Symptom | Check | Action |
|---|---|---|
| No peer appears | Bluetooth permission, radio state, foreground app state, compatible transport and app configuration | Run the BLE quickstart on two nearby physical devices. Phone Wi-Fi Direct and MultipeerConnectivity carry no traffic in v0.27.0. |
| Address is missing | identity_ready, startup errors and secure storage | Resolve storage/startup failure before sending. |
| Peer appears but encryption never becomes ready | Session events, time settings and peer version | Check identity/key-package errors; do not disable encryption to hide the failure. |
| Message remains pending | message_deferred, message_undeliverable, path availability and retention | Restore a path and keep processing events. Undeliverable is not a terminal failure. |
| SDK says delivered, workflow is incomplete | Receiving application record and receipt | Check application acceptance separately from transport delivery. |
| Data disappears after restart | Stable app/profile, persistent state and MLS store, flush boundary | Preserve identity and state together; await the relevant local commit. |
| Shared document does not converge | Correct space, membership, interest filters and data_* events | Compare document IDs and ensure both peers are eligible replicas. |
| Service does not respond | Provider authorization, method, version and application handler | Check the request ID and app deadline; inspect provider logs. |
| Backend has duplicates | Stable event ID and destination idempotency | Correct adapter transaction/retry behaviour. |
| Works in debug, stops in background | OS lifecycle and wake-task configuration | Test the release build under the deployment’s actual power and background policy. |
message_delivered and message_failed settle the SDK send. message_retrying, message_deferred and message_undeliverable describe pending work. message_decryption_failed reports a decryption attempt; it is not a terminal send outcome.
Queue storage is bounded. Expiry and capacity eviction are failures that your application must surface. Do not promise unlimited retention or guaranteed delivery without a reachable path.