The simulated location only held while the map screen was visible and the app was foregrounded. The resend loop was a main-runloop Timer in the view's @State, and .onDisappear tore it down along with the background assertion — so switching tabs, locking the phone, or ~30s of background each stopped the resends, let the simulation connection die, and snapped the device back to its real location. - Add LocationSimulationKeepAlive, which owns the held coordinate, resends it from a dispatch timer instead of the main runloop, takes forced audio and location holds (so it works with the user's keep-alive toggles off), and renews its background assertion rather than letting it expire. - MapSelectionView delegates the resend loop to the service, and .onDisappear no longer stops the simulation — only an explicit Clear releases it. On reappear the view re-adopts the held coordinate so the UI is not misleading. - MainTabView's URL-scheme path holds on simulate, and releases *before* clearing so a queued resend cannot re-apply a location just cleared. This is the part of the reliability problem the PR never addressed: its network-path work only governs the JIT/debug tunnel, while location simulation runs over its own separate rp_pairing connection. Not verified on device — the background-suspension behaviour needs testing on real hardware. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .github | ||
| assets | ||
| StikDebug | ||
| StikDebug.xcodeproj | ||
| StikDebugTests | ||
| StikDebugUITests | ||
| .gitignore | ||
| info.md | ||
| LICENSE | ||
| README.md | ||
StikDebug
An on-device debugger/JIT enabler for iOS versions 17.4+ powered by idevice.
Features
- JIT: Enable Just In Time compilation for sideloaded apps that have the
get-task-allowentitlement. - App Launching: Launch every app installed on your device.
- Console: Live app and system logs.
- Scripts: Manage automation scripts (mainly used for iOS 26 JIT).
- App Expiry: See when apps will expire and install/remove profiles.
- Device Info: View detailed device metadata.
- Processes: Inspect running apps/processes and terminate them.
- Location Simulator: Simulate the GPS location of your device.
Download
Note
Notice: StikDebug is no longer available on the App Store. Please use the official download methods below.
Compatibility
| iOS Version | Status | Notes |
|---|---|---|
| 1.0 – 17.3.X | Not supported | Uses Different Connection Protocols |
| 17.4 – 18.x | Fully supported | Stable |
| 26.0+ | Supported | Limited App Availability (Developers need to update their apps to work.) |
How to Enable JIT
StikDebug enables JIT for sideloaded apps on iOS 17.4+ without needing a computer after the initial pairing setup.
Requirements
- StikDebug installed (via AltSource, direct .ipa, or self-built)
- A valid pairing file (.plist / .mobiledevicepairing) for your device
- SideStore / AltStore / similar sideload tool (for app refreshing)
- A loopback VPN such as LocalDevVPN
Steps
-
Obtain a pairing file
- Detailed guide: Pairing File Instructions (or ask in Discord).
-
Set up VPN
- Launch LocalDevVPN and enable the VPN.
-
Enable JIT for an app
- Launch StikDebug and tapp the
Enable JITbutton. - Select your sideloaded app from the list in StikDebug.
- Launch StikDebug and tapp the
Troubleshooting
- "Connection dropped" or loopback errors → Check iOS version compatibility / beta warnings.
- Heartbeat errors → Ensure that LocalDevVPN is on. Any network works (Wi-Fi or cellular); the tunnel rides the VPN, so cellular-only is supported. It may also be a pairing file issue.
- Session drops after switching to another app → Keep the background keep-alive enabled (Settings → Background Keep-Alive). While a JIT/debug session is active, StikDebug plays inaudible audio and holds a background assertion so the session survives being switched out of the app instead of timing out.
- Pairing file issues → Replace file with device unlocked & trusted.
- Still stuck? Join the Discord with logs/screenshots.
Building from Source
Important
Integrating StikDebug or StikJIT into your own project?
See the StikJIT Integration Guide for integration instructions.
Requirements
- macOS (latest recommended)
- Xcode 16+ (Xcode 26+ preferred for iOS 26+ support)
- iOS device on iOS 17.4+ (for testing)
- Git
- Basic Xcode/Swift knowledge
Steps
-
Clone the repo
git clone https://github.com/StikDebug/StikDebug.git cd StikDebug -
Open in Xcode
- Launch Xcode
- Open
StikDebug.xcodeproj
-
Configure signing
- Select the StikDebug target
- Go to Signing & Capabilities
- Sign in with your Apple ID (free or paid developer account)
- Set a unique Bundle Identifier (e.g.,
com.yourname.StikDebug)
-
Build & install
- Select your connected device
- Press Cmd + R (or Product → Run)
- Trust the certificate on device: Settings → General → VPN & Device Management
After install, follow the JIT setup steps above (pairing import, etc.).
Contributing
Thank you for your interest in contributing to this project. Contributions of all kinds are welcome.
Reporting Bugs
If you discover a bug, please open an issue and include:
- A clear and descriptive title
- Steps to reproduce the issue
- Expected behavior vs. actual behavior
- Relevant logs, screenshots, or environment details (iOS version, device model, etc.)
Suggesting Features
To propose a new feature, open a feature request issue and provide:
- A clear description of the feature
- The problem it solves or the use case it addresses
- Any relevant examples or implementation ideas
Code Contributions (Best Practices)
- Follow normal Swift and SwiftUI style.
- Write clear and easy to understand code.
- Keep your changes consistent with how the project is already set up.
- Make sure everything builds and works without errors.
We appreciate your time and effort in helping improve this project.
Code Help
License
StikDebug is licensed under AGPL-3.0. See LICENSE for details.

