Watusi for WhatsApp: how the iOS tweak installs and what it changes

What Watusi modifies and which install path fits your device

Watusi for WhatsApp is an iOS tweak that extends WhatsApp Messenger and WhatsApp Business with features not in the App Store builds. Distribution runs through three channels depending on whether the device is jailbroken. fouadraheb.com/watusi is the project homepage, and changelogs are published at apt.fouadraheb.com/package/com.fouadraheb.watusi3/changelogs.

No compiled plugin code lives in the repository. Four top-level entries make up the project on GitHub: .gitignore, README.md, an altstore/ directory containing AltStore source metadata, and an images/ folder. All functional content is distributed as pre-built IPA files hosted at fouadraheb.com and through third-party services.

Jailbreak installs use a Cydia, Zebra or Sileo package repository. Sideloading via AltStore works on any device without a jailbreak but requires a computer and re-signing every seven days with a free Apple ID. TrollStore bypasses re-signing entirely but is restricted to specific iOS version ranges. Each path uses a different IPA variant, and using the wrong one for the install method causes crashes.

Jailbreak path: add apt.fouadraheb.com to your package manager

Adding https://apt.fouadraheb.com to Cydia, Zebra or Sileo puts Watusi in the package list. No IPA file is involved: the package manager handles download, installation and later updates from the repository itself. That is a meaningful difference from the AltStore and TrollStore paths, where each update requires downloading a new IPA and reinstalling.

Device jailbreakability for specific iOS versions is covered at appledb.dev/device-selection/, which the README links to directly. Watusi's README does not enumerate a supported iOS range for the jailbreak path; that depends on which jailbreak tools are available for a given firmware. As Apple releases updates, jailbreak coverage changes independently of Watusi.

Unlike sideloading, a jailbreak gives the tweak direct system access to inject into WhatsApp's process rather than relying on the restricted entitlements of a developer-signed build. That access is what allows features that sideloaded builds cannot replicate. For a device already jailbroken on a compatible firmware, repository-based install is the lowest-maintenance option over time.

AltStore sideloading: a computer, an Apple ID and the 7-day ceiling

AltStore sideloading requires a Mac or Windows computer, an internet connection and an Apple ID (email and password). On iOS 16, Developer Mode may need to be enabled first, found under Settings, then Privacy and Security, then Developer Mode. Two-factor authentication works with AltStore; app-specific passwords do not.

Getting AltStore onto the phone starts with AltServer on the computer: after downloading AltServer from altstore.io, connecting the iPhone, and right-clicking the AltServer icon, the Install AltStore menu entry installs AltStore to the selected device. Apple ID credentials are entered at that point. With AltStore installed, an IPA copied to the phone is imported through My Apps by tapping the plus button in the top right corner.

A free Apple ID code-signs the app for seven days. AltStore refreshes the signature if the computer running AltServer is reachable when the window nears expiry. If the computer is unavailable and the certificate expires, WhatsApp stops opening until re-signed. A paying signing certificate, described in the README as keeping the app valid for one year instead of seven days, removes that constraint at the cost of a third-party subscription.

The IPA table: six variants separated by signing context

Six IPA files cover two applications (WhatsApp and WhatsApp Business) and two bundle identifiers each (original and duplicate). Original bundles (net.whatsapp.WhatsApp and net.whatsapp.WhatsAppSMB) replace the App Store installation. Duplicate bundles (com.fouadraheb.watusi and com.fouadraheb.watusiSMB) install alongside the original so both run on the same device. Before sideloading, confirming no existing WhatsApp shares the target bundle identifier avoids a conflict at install time.

Sideload IPAs (labeled SL) have the Plugins folder removed and include crash fixes for devices without full developer entitlements. TrollStore IPAs (labeled TS) are fake-signed with original entitlements and carry no crash fixes. Using a TrollStore IPA through AltStore produces a broken install, and the README warns in uppercase that the TS files will crash if not used in TrollStore or with a proper signing certificate.

Three tweaks, Stalky, OnlineNotify and ContactSync, are off at install time across all variants. Enabling any of them requires a manual toggle inside Watusi Settings after installation.

TrollStore: tight iOS version limits and a second table for notification failures

Installing through TrollStore overwrites the App Store WhatsApp, so the App Store version must be present and activated first. After that, the TrollStore IPA is downloaded, opened in TrollStore and installed over the original. TrollStore's own setup is a separate prerequisite; the README links to its GitHub repository at github.com/opa334/TrollStore and to ios.cfw.guide for guidance.

Two device groups have different iOS version requirements: iPhone X and devices with A11 chips need iOS 14 through 16.6.1, while iPhone 11 and newer need iOS 14 through 16.6 beta 1. Any device outside those ranges cannot use this path. Push notifications and iCloud features work correctly through TrollStore, which is the main advantage over AltStore sideloading.

A second table in the TrollStore section lists NoPlugins variants for WhatsApp and WhatsApp Business. These are for users who encounter notification failures after installation, a problem the README traces to extensions injecting into WhatsApp service processes. A blog post at blog.fouadraheb.com covers the underlying mechanism. One detail the README does not address: the main TrollStore table includes Duplicate bundle variants, but the NoPlugins table does not. No explanation for that omission appears in the repository.

Signing certificates via Flekstore as a year-long alternative

A signing certificate bypasses the seven-day re-signing window by keeping the app valid for one year. Flekstore at flekstore.com supports adding the source at https://source.fouadraheb.com so Watusi can be downloaded directly to the device. KravaSign at kravasign.com/fouadraheb is listed as a second option.

For users with AltStore Beta, adding the same source (https://source.fouadraheb.com) to AltStore enables direct in-app download without manually copying an IPA file. That removes the step of finding and transferring the file but still uses a seven-day signing window unless a certificate is in use.

Certificate-based sideloading avoids the daily need for a computer running AltServer, which is the main practical reason to pay for one. Pricing, terms and security properties of Flekstore and KravaSign are outside what the README documents. Evaluating a signing service is a separate decision from choosing whether to use Watusi at all.

Stalky, OnlineNotify and ContactSync: what the names say and what the README omits

All three tweaks are off at install time and require a manual enable in Watusi Settings. Beyond their names and the toggle location, the README provides no description of what each does, what data each accesses or what the other party to a conversation can detect. Changelogs at apt.fouadraheb.com/package/com.fouadraheb.watusi3/changelogs are the only documented source of feature-level detail.

Shipping these three disabled is a practical design choice. Features that surface information about other users (online status, contact activity, notification timing) carry implications that differ from purely local modifications such as theme changes or layout tweaks. An active choice to enable them separates a user from someone who installed a defaults-on version. What each accesses in practice requires reading the changelogs or examining the installed app.

Other Watusi features are not enumerated in the README. Installing and reading the changelogs is the only way to see the full list. Anyone comparing Watusi to stock WhatsApp before installing should treat the README as a navigation document rather than a feature index.

No source code in the repository and no public build process

Beyond .gitignore, README.md and images/, the only functional directory is altstore/, which holds the JSON metadata that AltStore reads when a user adds https://source.fouadraheb.com as a source. No Theos project files, build scripts or plugin source appear anywhere in the repository. Watusi exists on GitHub primarily as a distribution point and a setup guide, not as an inspectable codebase.

For a user deciding whether to install, this means the behavior of the binary cannot be audited from the repository. Reading changelogs at apt.fouadraheb.com is one verification step; examining the binary with analysis tools is another. Neither is covered in the README.

Versioning is tracked through the IPA filenames and the changelogs at the Cydia repository URL. The repository has no GitHub releases. A user who wants to confirm they have the current build needs to compare the version in the README's IPA table against what is available through their chosen install source before downloading.

Editorial conclusion

Use Watusi if you are on a jailbroken iPhone or comfortable with AltStore and want WhatsApp features the official app does not provide. Skip it if re-signing every seven days is not workable and you do not want to pay for a signing certificate, or if running a modified binary conflicts with your employer's mobile device policy. Before installing, verify your iOS version against the TrollStore compatibility table in the README if push notifications matter to you, and check the changelogs at apt.fouadraheb.com/package/com.fouadraheb.watusi3/changelogs against the WhatsApp version in the App Store before updating either app.

Frequently asked questions

Official sources

1. FouadRaheb/Watusi-for-WhatsApp on GitHub
2. Issues
3. Project website
4. README