Skip to support

Support

Start with gateway health, then the queue

Most problems can be isolated by checking server readiness, the last phone heartbeat, permissions, routing, and the final job state—in that order.

Server checks

  1. Open the readiness endpoint or run the documented doctor command.
  2. Confirm HTTPS, storage write access, disk space, and a recent verified backup.
  3. Check sanitised logs for an error code—never share secrets or message content.

Phone checks

  1. Open the Flutter app and review its gateway health checklist.
  2. Confirm SMS and phone permissions, the selected SIM, and network service.
  3. Check the last successful poll and pending reconciliation count before retrying.

Safe installation

Use only the authenticated, signed release artifact. Compare its version and SHA-256 checksum, keep Play Protect enabled, and stop if Android reports an unverified source or signature.

Avoid duplicate sends

If a phone timed out after submitting to the radio, treat the outcome as uncertain. Reconcile the status first; do not immediately queue the same message again.

Still stuck?

Send the application version, anonymised error code, approximate time, deployment method, and checks already completed. Do not send passwords, tokens, phone numbers, message bodies, environment files, or full database records.

sms@support.scratchive.com