Launch JIT enabled iOS app with a second iOS device
This app uses libimobiledevice and WiFi pairing to use one iOS device to launch apps with the debugger on another iOS device. This “tethered” launch allows JIT to work on the second iOS device. It can also create a VPN tunnel to allow a device to debug itself.
AltStore is the preferred way to install Jitterbug. You can also sideload the IPA through other means or install it on a jailbroken device using AppSync Unified.
Install Jitterbug on your primary device and the app you wish to launch on your secondary device.
On macOS and Windows, make sure you have iTunes installed. On Linux, make sure usbmuxd
is installed (sudo apt install usbmuxd
).
Run jitterbugpair
with your secondary device plugged in to generate YOUR-UDID.mobiledevicepairing
. You need to have a passcode enabled and the device should be unlocked. The first time you run the tool, you will get a prompt for your passcode. Type it in and keep the screen on and unlocked and run the tool again to generate the pairing.
Use AirDrop, email, or another means to copy the .mobiledevicepairing
to your primary iOS device. When you open it, it should launch Jitterbug and import automatically.
Download the Developer Image for the iOS version running on your secondary iOS device (or the closest version if your version is not listed) and copy both DeveloperDiskImage.dmg
and DeveloperDiskImage.dmg.signature
to your primary iOS device. Open Jitterbug, go to “Support Files” and import both files.
Open Jitterbug, go to “Launcher”, and look for your secondary iOS device to show up. If it is not showing up, make sure both devices are connected to the same network (tethering from primary to secondary OR secondary to primary is OK). Select the device and choose the pairing file. Then choose the app to launch and choose the DeveloperDiskImage.dmg
file.
git submodule update --init --recursive
CodeSigning.xcconfig.sample
to CodeSigning.xcconfig
and edit it, filling in the information detailed in the next section.Jitterbug.xcodeproj
.Jitterbug can create a VPN tunnel so a device can debug itself. This requires the “Network Extensions” entitlement which is not available to free developer accounts. If you have a free account, you will get a code signing error when trying to build. Jitterbug Lite is a build target that does not require Network Extensions and can be built with a free account.
Because Apple requires unique bundle IDs for developers, you need to choose a unique bundle ID prefix and fill it in CodeSigning.xcconfig
.
If you have a paid account, you can find DEVELOPMENT_TEAM
by going here. If you have a free account, you can find your Team ID by creating a new Xcode project for iOS, selecting your team under Signing & Capabilities, and looking for the value of DEVELOPMENT_TEAM
build setting.
The software to generate a pairing token is available for macOS, Linux, and Windows.
git submodule update --init --recursive
brew install meson [email protected] libusbmuxd libimobiledevice pkg-config
PKG_CONFIG_PATH="/usr/local/opt/[email protected]/lib/pkgconfig" meson build && cd build && meson compile
build/jitterbugpair
. You can install it with meson install
.git submodule update --init --recursive
sudo apt install meson libgcrypt-dev libusbmuxd-dev libimobiledevice-dev libunistring-dev
meson build && cd build && ninja
build/jitterbugpair
. You can install it with sudo ninja install
.pacman -Syy git mingw64/mingw-w64-x86_64-gcc mingw64/mingw-w64-x86_64-pkg-config mingw64/mingw-w64-x86_64-meson mingw64/mingw-w64-x86_64-libusbmuxd mingw64/mingw-w64-x86_64-libimobiledevice
git clone --recursive https://github.com/osy/Jitterbug.git
cd Jitterbug
meson build && cd build && meson compile
build/jitterbugpair.exe
and build/libwinpthread-1.dll
. Both files needs to be in the same directory to run.You may have already mounted the developer image. Try launching an app.
This application does not have the get-task-allow
entitlement. Or this is not an development app.