The fastest way to reach us is from inside the app: open Settings → Other → Send feedback. The form attaches a redacted diagnostic log automatically and lets you leave an optional reply-to email — no manual log export needed.
If you can’t reach the in-app form, email us instead:
Before You Write In
To help us reproduce the problem quickly, please include as much of the following as you can:
- Android version and phone model (for example: “Android 14, Xiaomi 14”).
- SmsForwarder version (shown at the bottom of the Settings page).
- Which feature is not working: SMS forwarding, RCS forwarding, MMS forwarding, call forwarding, app notification forwarding, remote control, Web Access (local network or access from anywhere), AI features (Advanced subscription, including Ask AI), backup/restore, scheduled Google Drive backup, or subscription.
- Which delivery channel is involved: Telegram, Email, Webhook, Slack, Bark, WhatsApp, Google Drive, or SMS.
- Whether the relevant permissions have been granted (text messages, calls, contacts, notifications, ignore battery optimization, vendor auto-start allowlist, notification access).
- Anything visible from a channel test message or from the Forwarding history page (the error or response shown there is usually the most useful clue).
- A diagnostic log. The in-app feedback form attaches and redacts one automatically. If you are writing by email instead, export the log from the Settings page and review it for personal information (phone numbers, email addresses, message bodies) before sharing.
Common Things to Check First
- At least one rule is enabled, and the matching rule type covers the kind of message you expect (SMS, RCS, MMS, call event, or app notification). There is no longer a separate global SMS / call / notification forwarding switch on the Settings page — whether a rule forwards is driven by the rule’s own enable toggle. (Bulk pause and resume is still available remotely through
#CTRL FORWARDING SMS / CALL / NOTIFICATION / ALL; see the Remote Control page.)
- The rule’s source-type chips are correct: for RCS messages, the rule’s RCS chip is on; for MMS, the MMS chip is on; for plain SMS, the SMS chip is on (it is always on by default).
- Every channel the rule fans out to is configured. If a rule has multiple channels selected, a problem with one channel does not stop the others — but make sure the channel you expect is actually in the rule’s channel list.
- Battery optimization is set to don’t optimize for SmsForwarder.
- If your phone is from Xiaomi, Huawei, OPPO, Vivo, Honor, or a similar brand, SmsForwarder is added to the auto-start / background activity allowlist in your phone’s settings.
- The destination channel passes its own test message.
- For Email with built-in sending (the default — no SMTP fields are shown), your subscription is active, the recipient address is correct, and you have checked the spam/junk folder. Built-in mail arrives from a fixed SmsForwarder sending address, not your own, so some inboxes file the first message as spam.
- For Email with a custom SMTP account, you are using an “app password” or “authorization code” if your provider requires one (Gmail, Outlook, QQ Mail, 163 Mail, iCloud, and others), with two-step verification enabled where the provider requires it for app passwords. The host, port, and encryption settings are auto-filled from your sender address for common providers.
- For Telegram, the bot has been started in the target chat at least once, and the chat ID is correct (a negative number for groups and channels).
- For Webhook / Slack / Bark, the URL is reachable from your phone’s network, and any required token, key, or secret is filled in.
- For WhatsApp (Meta Cloud API mode), you have already opened a 24-hour message window by sending a message from your WhatsApp to the Business number — Meta does not allow outbound messages otherwise. For CallMeBot mode, the API key activation flow on
callmebot.com has been completed for the recipient’s number.
- For Google Drive, the channel card shows Connected as <your Google account>. If it shows Reconnect needed, tap it and sign in again — this usually means the Google account password was changed or the OAuth grant was revoked from the user’s Google account security page. On the Google consent screen, leave the Google Drive checkbox ticked; if you uncheck it, the channel cannot create or write files.
- For RCS forwarding, Notification access is granted to SmsForwarder in Android system settings (RCS arrives as a system notification posted by the default messaging app — SmsForwarder cannot read RCS without notification access). If your default messaging app posts RCS notifications with the content hidden (“privacy mode” / “RCS preview off”), the forwarded message will not include the body either; either turn off RCS privacy in that app, or accept that the forwarded entry will note the message was redacted by the system.
- For app notification forwarding, Notification access is granted to SmsForwarder in Android system settings.
- For Web Access, the access token is current (rotate it from the Web Access page if you forgot it), the chosen local-network port is not blocked by another app on the phone or by a firewall, and — for access from anywhere — your subscription is Advanced and the phone is allowed to run in the background (battery optimization disabled). If the local browser only shows messages the app has already forwarded, that is expected when the Read SMS permission is not granted; grant it from Android settings to see the full inbox.
- For scheduled Google Drive backup, the scheduled-backup card on the Backup page shows a recent successful run timestamp. If it shows an error, reconnect Google Drive (this is independent from any Google Drive forwarding channel — each holds its own sign-in).
- For remote control, the sender’s number is on the allow list in full international format, for example
+14155551234.
- For AI features, your Google account has an active Advanced subscription, the AI master switch is on under Settings → AI, an AI cloud path is configured there — either the built-in cloud (the default for Advanced subscribers, no API key required) or a BYOK provider (Gemini, Claude, or OpenAI) with a working API key — and the specific capability you expect (one-time code, tags, translation, or summary) is turned on inside the rule’s AI card. (As of this app version, the per-capability toggles live on each rule, not on the global AI settings page.) For the
#AI remote command, the Natural-language remote command toggle is on under Remote control. For Ask AI, the same Advanced subscription and cloud path apply; Ask AI has its own daily allowance shown next to the regular AI usage card.
Useful Documentation