[GH-ISSUE #1052] [BUG] No pip when using StikDebug for Jit on the latest nightly release #929

New issue

Closed

opened 2026-03-03 15:37:22 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 15:37:22 +03:00

Owner

Originally created by @topman365pro on GitHub (Dec 25, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/1052

Describe the bug

When using StikDebug for JIT on the latest nightly release of LiveContainer, JIT appears to be successfully acquired, but it does not actually work at runtime. Apps that depend on JIT will launch and report that JIT is enabled, but as soon as an action that truly requires JIT is executed, the app either freezes or crashes.
Video:
https://share.icloud.com/photos/0d10y5I_-xI0SOvbAlwDmxTOQ
Device:
M2 iPad Pro on iOS 26.2

Instructions to reproduce

Connect to Localdev VPN
Open StikDebug
run an app that requires Jit and has a StikDebug Jit script associated with it
the app detects that Jit is acquired but when any actions that actually requires Jit is ran, the app either stalls or crashes
StikDebug shows error code -1, msg Socket (Kind (ConnectionReset)) or Socket(Kind(BrokenPipe)) with older versions of StikDebug

What version of LiveContainer and iOS are you using?

Version 3.6.60-Release (multitask-experimental/e852c64) (Tried both the multitask experimental and main release)

Verify steps

I downloaded LiveContainer from releases / actions section or LiveContainer's AltStore source.
I have the latest LiveContainer.
I installed LiveContainer through AltStore/SideStore/TrollStore or I'm confident that I signed LiveContainer correctly with all required entitlements.

Crash Log

No response

Other info

I even uninstalled the App Store version of StikDebug thinking it was the issue, nope
Thought using StikDebug in windowed mode would fix the issue since no pip is present, app black screens instead

Originally created by @topman365pro on GitHub (Dec 25, 2025). Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/1052 ### Describe the bug When using StikDebug for JIT on the latest nightly release of LiveContainer, JIT appears to be successfully acquired, but it does not actually work at runtime. Apps that depend on JIT will launch and report that JIT is enabled, but as soon as an action that truly requires JIT is executed, the app either freezes or crashes. Video: https://share.icloud.com/photos/0d10y5I_-xI0SOvbAlwDmxTOQ Device: M2 iPad Pro on iOS 26.2 ### Instructions to reproduce 1. Connect to Localdev VPN 2. Open StikDebug 3. run an app that requires Jit and has a StikDebug Jit script associated with it 4. the app detects that Jit is acquired but when any actions that actually requires Jit is ran, the app either stalls or crashes 5. StikDebug shows error code -1, msg Socket (Kind (ConnectionReset)) or Socket(Kind(BrokenPipe)) with older versions of StikDebug ### What version of LiveContainer and iOS are you using? Version 3.6.60-Release (multitask-experimental/e852c64) (Tried both the multitask experimental and main release) ### Verify steps - [x] I downloaded LiveContainer from releases / actions section or LiveContainer's AltStore source. - [x] I have the latest LiveContainer. - [x] I installed LiveContainer through AltStore/SideStore/TrollStore or I'm confident that I signed LiveContainer correctly with all required entitlements. ### Crash Log _No response_ ### Other info I even uninstalled the App Store version of StikDebug thinking it was the issue, nope Thought using StikDebug in windowed mode would fix the issue since no pip is present, app black screens instead

kerem

2026-03-03 15:37:22 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 15:37:23 +03:00

Author

Owner

@hugeBlack commented on GitHub (Dec 25, 2025):

StikDebug shows error code -1, msg Socket (Kind (ConnectionReset)) or Socket(Kind(BrokenPipe)) with older versions of StikDebug

That means stikdebug itself cannot communicate with your device. Not a LiveContainer issue.

@hugeBlack commented on GitHub (Dec 25, 2025): > StikDebug shows error code -1, msg Socket (Kind (ConnectionReset)) or Socket(Kind(BrokenPipe)) with older versions of StikDebug That means stikdebug itself cannot communicate with your device. Not a LiveContainer issue.