JIT on iOS Without a Computer: Meet StikDebug
If you've ever sideloaded an app onto your iPhone, you know the routine. You get the app installed, you launch it, and then you hit the wall that is Just-In-Time compilation being disabled. For a lot of emulators and other demanding apps, that's the difference between something that runs and something that stutters or refuses to start. The usual fix involves tethering to a computer and jumping through debugger hoops. StikDebug is an open-source project that aims to remove the computer from that equation entirely.
What It Does
StikDebug is an on-device debugger and JIT enabler for iOS 17.4 and later, powered by the idevice library. In plain terms, it lets you enable Just-In-Time compilation for sideloaded apps that carry the get-task-allow entitlement—and it does so from the phone itself, once you've handled the initial pairing setup. No Mac or PC sitting next to you required.
That's the headline feature, but the app bundles in a fair amount of extra tooling. It can launch any app installed on your device, stream live app and system logs, manage automation scripts (which the README notes are mainly used for iOS 26 JIT), and show you when your sideloaded apps are set to expire—including the ability to install and remove profiles. There's also device metadata inspection, a process viewer that lets you terminate running apps, and a GPS location simulator. So it's less a single-purpose utility and more a small on-device toolbox for people who tinker with sideloading.
Why It's Cool
The core appeal here is obvious if you've been in the sideloading scene for any length of time: the computer dependency is the annoying part. Pairing files, cable connections, and desktop-side tools have long been the price of admission for JIT. StikDebug's pitch is that after that first pairing step, you can flip JIT on from the device itself.
A few things stand out beyond that:
- The feature set reaches past JIT. The console, process manager, and app expiry view are the kinds of things you'd normally stitch together from multiple tools. Having them in one place is genuinely convenient, especially when you're debugging why a sideloaded app is misbehaving.
- The compatibility table is honest. iOS 17.4 through 18.x is marked fully supported and stable. iOS 26.0+ is supported but limited, with a note that developers need to update their apps to work. That kind of transparency is refreshing—it tells you upfront where you might run into trouble instead of letting you find out the hard way.
- It's built on idevice. Rather than reinventing device communication, the project leans on an existing library, which suggests a more maintainable foundation than a from-scratch protocol implementation.
- The iOS 26 script support is forward-looking. Scripts for JIT on newer iOS versions hint that the maintainers are already thinking about the next set of constraints rather than resting on what works today.
It's also worth noting the practical distribution reality: the README states StikDebug is no longer on the App Store, and points you to an AltSource or a direct .ipa download instead. That's consistent with what the tool does—this isn't the kind of capability Apple tends to leave on its storefront.
How to Try It
Before you start, gather what you'll need. The README lists four requirements: StikDebug itself (via AltSource, direct .ipa, or self-built), a valid pairing file (.plist or .mobiledevicepairing), a sideload tool like SideStore or AltStore for app refreshing, and a loopback VPN such as LocalDevVPN.
- Get a pairing file. The README links to a dedicated pairing file guide in the StikDebug-Guide repo, or you can ask in their Discord. This is the one step that still ties back to a computer, so do it first.
- Set up the VPN. Launch LocalDevVPN and enable it. The loopback connection is part of how the on-device communication works.
- Enable JIT. Open StikDebug, tap the
Enable JITbutton, and pick your sideloaded app from the list.
If you hit a "Connection dropped" or loopback error, the README's troubleshooting section (truncated in what I could see) is where to look next—and the Discord is there as a fallback.
You can grab the latest release and browse the source at github.com/StikDebug/StikDebug. The download buttons in the README point to an AltSource link and a direct .ipa.
Final Thoughts
StikDebug is clearly aimed at a specific audience: people who sideload iOS apps and are tired of dragging a laptop into the process every time they want JIT enabled. If that's you, the combination of on-device JIT toggling plus the console and process tools makes it a reasonable one-stop option—provided you're on a supported iOS version and willing to do the pairing file dance once. The honest compatibility notes and the move off the App Store tell you the maintainers know exactly who they're building for. It's a niche tool for a niche problem, and it seems to own that niche well.