The route corridor was sent to Overpass as one all-or-nothing query that embedded the coordinate string four times (roads + three bus-stop tag clauses). On long routes that regularly exceeded the 25s server timeout, and because the caller swallowed errors, every bus stop and speed limit was silently lost — exactly the 'stops never load' failure. The 700-point corridor cap also widened point spacing far beyond the 90m search radius on very long routes, cutting corners past stops even when the query succeeded. Rework the fetch into independent corridor chunks (~12km each, two in flight, per-chunk timeouts): - Each chunk is a small, fast request; a failed chunk only loses its own stretch instead of the whole route, and failures are logged. - Bus stops stream onto the map as chunks arrive via an onPartialBusStops callback instead of appearing only at the end. - The three bus-stop tag clauses are collapsed into one regex clause (a single corridor pass server-side); exact filtering stays client-side in tagsDescribeBusStop. - Results are deduplicated across chunk seams by OSM element id, and stops mapped twice (platform + stop_position a few meters apart) are merged spatially so markers and dwells aren't doubled. - Corridor spacing now stays within the search radius up to ~285km of route (24 chunks x 160 points) instead of degrading past ~50km. Verified the exact generated query shape against the live Overpass API: HTTP 200 in ~2s, element ids/geometry/lat-lon match the decoder, and the regex clause returns both legacy and public_transport-schema stops. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013DNqCsHShA4yNqgZ6ZZQy3 |
||
|---|---|---|
| .github | ||
| assets | ||
| StikDebug | ||
| StikDebug.xcodeproj | ||
| StikDebugTests | ||
| StikDebugUITests | ||
| .gitignore | ||
| CODE_REVIEW_REPORT_BY_FABLE_5.md | ||
| 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
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/StephenDev0/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.