Before today, the only way to tell us a CarterWare tweak was broken was an email address buried on a support page. Almost nobody uses that. People who hit a bug in a jailbreak tweak usually just uninstall it, or post "doesn't work" in a Reddit thread we never see.
So before we start pushing the tweaks harder, every one of them needed a Report a Bug button that takes ten seconds to use and gives us enough detail to actually fix something. Here's how we built it across eight tweaks in one day without adding a single dependency.
What a useful bug report needs
Most bug reports are missing the same three things: which version, which iOS, which phone. Users don't know where to find them, so we stopped asking. The report should arrive with:
- the tweak and its installed version (not the version the user thinks they have)
- iOS version and exact iPhone model
- the jailbreak (Dopamine, palera1n and so on)
- what happened, plus optional steps and a crash log
Everything else is optional, including an email address. Making email required cuts submissions sharply, and a ticket number is enough for someone to follow up later.
The endpoint: a few hundred lines on a server we already run
We already run a small Express server for payments and downloads, backed by SQLite through Node's built-in node:sqlite. The bug endpoint lives there:
POST /bugsaccepts JSON from the website and plain form posts as a no-JavaScript fallback.- Each field has a hard length cap, and the product must be one of our real package IDs.
- Spam control is boring on purpose: per-IP rate limits (6 an hour, 20 a day), a hidden honeypot field that only bots fill in, and a one-way hash of the IP instead of the address itself.
- New reports email us immediately, with the reporter set as the reply-to address. If they left an email, they get an acknowledgement with their ticket number.
Reports land in an owner-only inbox at /account/bugs, behind the same email-code login customers use. Each report can be marked new, confirmed, fixed or closed. There's no ticketing SaaS and no monthly bill, and it's all in one database file we already back up.
The form: static HTML that prefills itself
The public form is a static page on the tweaks site. It reads query parameters (pkg, v, ios, device, jb) and fills in the matching fields. If someone opens it on an iPhone without parameters, it still pulls the iOS version from the browser's user agent. On submit, it posts to the endpoint and swaps the form for a big ticket number like CW-0001.
The button: one shared header, eight tweaks
Each tweak has a settings pane in the iOS Settings app. We wrote one Objective-C header, CWBugReport.h, that does the work when the button is tapped:
- Reads the installed version straight from dpkg's status database for that package ID.
- Reads the iOS version and the hardware identifier (like
iPhone16,2) and maps it to a readable name. - Checks for marker files to name the jailbreak.
- Builds the prefilled URL and opens it in Safari.
Each tweak's settings controller gets a three-line method that calls it with its own package ID. A small sync script copies the header into every tweak and appends a "Support" section with the button to each settings page. Re-running it is safe, so new tweaks get the button by running one command.
Testing it on a real phone
Simulators don't run jailbreak tweaks, so testing happened on a jailbroken iPhone 15 Pro Max on iOS 17.1. We installed the new builds, opened Settings, tapped Report a Bug in Fold, and Safari opened with Fold 1.2.6 · iOS 17.1 · iPhone 15 Pro Max (iPhone16,2) already filled in. We submitted it, got ticket CW-0001, and the notification email was delivered to our inbox within a couple of seconds.
What we'd tell any small software team
- Collect device details automatically. The fields users can't easily find are the ones you need most.
- Keep the form short and email optional. A report you get beats a perfect report you don't.
- Use infrastructure you already have. A table, an endpoint and an email cover most of what a small product needs from a ticketing system.
- Close the loop. A ticket number and a changelog line saying "fixed" are what turn a frustrated user into one who reports the next bug too.
If you're shipping software and want this kind of tooling built into your product, get in touch. And if you run CarterWare tweaks and something is off, the button is waiting in Settings.