Current production
Build 145, v1.2.08
VirusTotal shows 0 of 51 vendors flagging this APK, a fully clean report. This is the current build live on Google Play.
Open Build 145 reportSupport
Start here before emailing support. Many missing-message, RCS, MMS, folder, backup, and antivirus questions can be checked with the steps below or the FAQ.
Include your phone model, Android version, carrier, ZenSMS version, what you expected, what actually happened, and the steps to reproduce it.
Please attach a Diagnostic Bundle. It helps identify carrier, APN, network, permission, and MMS state-machine issues specific to your device.
The bundle includes device/app settings, permission states, message counts, self-test results, and recent MMS send/download events. It does not include message bodies, contact names, attachment content, or phone numbers in readable form.
If a bug happens when a message arrives, such as a group reply landing in the wrong thread, a photo not loading, or a strange MMS character appearing, open ZenSMS before the expected message arrives and leave it open. After the bad message arrives, do not clear the notification, delete the message, or force-close the app. Go straight to Settings -> Diagnostics and generate the bundle right away.
This matters because the most useful MMS routing events are kept in a short in-memory diagnostic log. Generating the bundle immediately gives support a much better chance of seeing whether Android delivered the message as SMS or MMS and where ZenSMS routed it.
ZenSMS has system folders and custom folders. System folders organize messages automatically. Custom folders and rules are premium features.
No third-party SMS app can receive RCS. If messages stop reaching you after switching from Samsung Messages, Google Messages, Verizon Messages+, or another RCS-capable app, Google recommends turning RCS chats off.
When you have the device, use Google Messages: Messages settings → RCS chats, and turn RCS chats off. You can keep ZenSMS as your default SMS app. If you cannot use the device, use Google’s deactivation portal at messages.google.com/disable-chat.
ZenSMS cannot receive or import RCS, and it cannot convert old RCS groups. See the Google Messages switching guide for the full notes.
Do not paste private message content into a support email unless you intentionally choose to share it. ZenSMS diagnostic tools are opt-in and are designed to avoid including message bodies or attachment content.
Some mobile security apps use generic rules for apps that can send, receive, or read SMS. Those permissions are required for a default SMS replacement app, but they are also permissions that real SMS malware can abuse. That is why a generic label like AdLibrary:Generisk or trojan.adlibrary/generisk is a weak signal by itself, not the same thing as a confirmed malware finding.
A stronger warning would be multiple major vendors flagging the same build with a specific malware family, especially vendors such as Bitdefender, Google, Microsoft, Kaspersky, ESET, Sophos, Malwarebytes, or similar high-signal engines.
Current production
VirusTotal shows 0 of 51 vendors flagging this APK, a fully clean report. This is the current build live on Google Play.
Open Build 145 reportNext release
VirusTotal shows 0 of 66 vendors flagging this APK. Build 147 is moving through Google Play staged rollout, so availability may take time.
Open Build 147 reportWe currently submit current release builds to Avast's whitelisting program because Avast/AVG engines ship on some OEM phones and can affect users during install. Older ZenSMS versions are not submitted retroactively because every AV vendor submission takes extra setup and follow-up time.
For third-party antivirus apps, we do not chase every generic warning. We focus on current builds, Google Play distribution, OEM-impacting scanners, and transparent public scan links so users can see the signal quality directly.
Exodus Privacy's public ZenSMS report currently shows 0 trackers. Their latest indexed report can trail the newest Google Play release, so treat it as independent evidence of the app's tracker profile, not as a scan of every current rollout build.