Troubleshooting the mobile app
Start with the line under the dial on the phone’s Gateway tab. It says why the phone isn’t sending, and most fixes follow from it.
The phone is offline
Section titled “The phone is offline”The dashboard shows the phone as offline, and the dial says Offline.
| Line under the dial | Fix |
|---|---|
| Connecting to api.smsfabric.com | Wait a few seconds. If it stays, check the phone’s Wi-Fi or mobile data. |
| Can’t reach api.smsfabric.com. Retrying on its own. | Check the phone’s connection. Try opening a website on it. The app keeps retrying, so you don’t need to restart it. |
| The gateway isn’t running. | Tap Start gateway. |
| SMS permission is off. Allow it to send. | Allow the SMS permission again. See “A permission was turned off” below. |
If the phone shows online on its own screen but the dashboard says offline, Android has probably stopped the app in the background since you last looked. Open the app, then follow Battery and background so it doesn’t happen again.
Reports waiting to upload means the phone sent messages but couldn’t tell the server yet. It uploads the reports when the connection is back. You don’t need to do anything.
Messages are stuck in the queue
Section titled “Messages are stuck in the queue”Messages for a phone wait on the server while it’s offline, paused or disabled. They go out when it’s back, or move to another online phone in the same pool.
- On the phone, check the dial. If it says Paused, tap Resume the gateway.
- If it says Offline, fix the connection as above.
- In the dashboard, open Devices and check the phone isn’t disabled, and that it has a SIM marked as default.
- If messages reach the phone but fail, open one on the Messages tab and read its error code. See Why a message failed.
To keep sending while one phone is down, add two or more phones to a pool. The server moves a pool’s messages to another online phone.
The pairing code expired
Section titled “The pairing code expired”The phone says This pairing code has expired or was already used.
A pairing code lasts 10 minutes and works once. In the dashboard’s Pair a phone dialog, click New code and scan again. If you typed the code, check you typed all 16 characters (capital letters and dashes are optional), and that Server URL matches the server you use.
A permission was turned off
Section titled “A permission was turned off”Android can turn off a permission when you deny it in a prompt, when you change it in the system settings, or when it resets permissions for apps you haven’t opened in a while.
- SMS: the dial says the permission is off. Open Android’s Settings, then Apps, then SMSFabric, then Permissions, and allow SMS. Allow Phone too, so the app can list your SIMs.
- Notifications: if the “SMSFabric gateway is running” notification is gone, allow notifications for SMSFabric in the same place. Without it, Android stops the gateway in the background.
- Camera: the scanner says the camera isn’t available. Allow the camera, or tap Enter the code instead and type the code.
On Android 11 and later, turn off Pause app activity if unused (the wording varies by brand) for SMSFabric, so Android doesn’t take permissions back from a gateway nobody opens.
The gateway stops when the screen is off
Section titled “The gateway stops when the screen is off”The phone works while you look at it and goes offline later. This is battery optimization or the manufacturer’s own background limits. Follow every step on Battery and background, including the guide for your phone’s brand.
No SIM card found
Section titled “No SIM card found”The SIM cards panel says No SIM cards found.
- Check the SIM is inserted and active: make a call or send an SMS from Android’s own Messages app.
- For an eSIM, check it’s turned on in Android’s SIM settings.
- Check the Phone permission is allowed for SMSFabric (see above). The app needs it to read the SIM list.
- Tap the refresh button at the top of the Gateway tab.
If a SIM shows Number hidden by carrier, the phone still sends from it. Some carriers don’t store the number on the SIM.
The phone was disabled or signed out
Section titled “The phone was disabled or signed out”- This phone was disabled: an admin turned off sending for this phone in the dashboard. Ask them to click Enable sending in Devices, then tap Check again.
- Pair this phone again: the server no longer accepts this phone’s token, usually because it was unpaired from the dashboard. Tap Pair again and pair it with a new code.
The app asks for an update
Section titled “The app asks for an update”The app shows Update SMSFabric to keep sending and won’t go further. Your server needs a newer version of the app. Messages for this phone wait in the queue until it’s updated.
Tap Get the update. The Google Play build opens the store. The direct build opens the download page; install the new APK over the old one. You don’t need to pair again.
SMSFabric is down for maintenance
Section titled “SMSFabric is down for maintenance”While the SMSFabric team works on the service, the app shows SMSFabric is down for maintenance instead of its tabs. Sending and the dashboard are paused, and messages already queued are kept: they go out when the service is back. The screen says when that should be, and you don’t need to pair again.
Tap Try again to check whether the service is back; the app also returns to its tabs on its own when maintenance ends. Open the status page shows the latest news. Before planned maintenance, a notice above the tabs says Maintenance is planned. Sending keeps working for now.