MOBaiLE Support

Help without guesswork.

Most setup problems come down to one of four things: backend health, the saved server URL, the API token, or a network path the phone cannot reach. Start there and you usually recover fast.

Open a GitHub issue Install guide Privacy policy Home

Quick recovery

Common fixes, grouped by symptom.

Use the symptom that matches what you see. The goal is to get you back to a successful first run, not send you wandering through every possible configuration.

Pairing does not complete

Confirm the backend responds at /health.
Re-open the pairing QR and make sure it is current.
Verify the app has the right Server URL, API Token, and Session ID.
If pairing fails immediately, rotate the pairing token with bash ./scripts/rotate_api_token.sh.

Works on Wi-Fi but not remotely

Do not use 127.0.0.1 on a real iPhone.
Prefer a Tailscale or HTTPS URL for remote use.
Confirm the chosen URL is reachable from the phone, not just from the host machine.
Run mobaile status on the host and check that the advertised URL still looks right.

Voice or mic flow feels broken

Confirm MOBaiLE has microphone and Speech Recognition permission in iOS Settings.
On Simulator or when on-device speech is unavailable, configure OPENAI_API_KEY for backend audio fallback.
If text works and audio does not, the backend path is usually fine and the problem is voice-specific.

The host seems idle or outdated

Run mobaile status to confirm the service is still ready.
Run mobaile update to pick up the latest installed backend and CLI.
If you changed code or config in a checkout, re-sync and restart the service.

Before opening an issue

A good issue report makes it obvious whether the problem is pairing, network reachability, host runtime, or voice fallback.

Say whether you are using a real iPhone or Simulator.
Include the setup path: local, LAN, Tailscale, or public HTTPS.
Include the exact symptom and the first step where it fails.
Include any relevant error message, but remove tokens and private URLs you do not want to publish.
Say whether /health and mobaile status both look healthy.

Where to get help

GitHub Issues are the main support path for setup problems, regressions, and feature requests. If you are using a distributed build, you can also use the support contact linked from the app's App Store listing.