[GH-ISSUE #400] [BUG] Launches apps before acquiring JIT with JITStreamer EB #366

Closed
opened 2026-03-03 15:33:01 +03:00 by kerem · 4 comments
Owner

Originally created by @0xC10 on GitHub (Mar 17, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/400

Describe the bug

Setup:
LiveContainer version 3.3.1 (main/92b68be), Sidestore version 0.6.0, JITless, JITstreamer EB

Upon enabling "launch with JIT" and having jitstreamer correctly set up, livecontainer ignores the JIT setup process and launches the app with JITless anyway. Apps that require JIT on the start will always fail. (It crashes after being on "checking mount status...")

This issue won't affect all apps but only rare ones which must have JIT upon launch or require JIT to run for "bypassing" codesigning.

Instructions to reproduce

Enable the JITStreamer config VPN, enable "Launch with JIT" in LiveContainer, launch the desired app (which requires JIT on launch), and it will fail.

What version of LiveContainer are you using?

3.3.1 (main/92b68be)

Other info

Launching LiveContainer with JIT beforehand might yield different results or fix this issue, but only in niche cases.

Originally created by @0xC10 on GitHub (Mar 17, 2025). Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/400 ### Describe the bug Setup: LiveContainer version 3.3.1 (main/92b68be), Sidestore version 0.6.0, JITless, JITstreamer EB Upon enabling "launch with JIT" and having jitstreamer correctly set up, livecontainer ignores the JIT setup process and launches the app with JITless anyway. Apps that require JIT on the start will always fail. (It crashes after being on "checking mount status...") This issue won't affect all apps but only rare ones which must have JIT upon launch or require JIT to run for "bypassing" codesigning. ### Instructions to reproduce Enable the JITStreamer config VPN, enable "Launch with JIT" in LiveContainer, launch the desired app (which requires JIT on launch), and it will fail. ### What version of LiveContainer are you using? 3.3.1 (main/92b68be) ### Other info Launching LiveContainer with JIT beforehand might yield different results or fix this issue, but only in niche cases.
kerem 2026-03-03 15:33:01 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@hugeBlack commented on GitHub (Mar 17, 2025):

I get your point. Due to changes in Jitstreamer 0.2.4, livecontainer cannot use the old way to enable jit so instead it enable it after app launches.

For now, you can

  1. Set the jit enabler to sidejitserver
  2. leave address and udid blank
  3. tap run, and the wait for jit dialog will appear
  4. use the jitstreamer shortcut to enable jit

Edit:
I made a new build so you can select "JitStresmer-EB (Relanch)" as the jit enabler to achieve this.

<!-- gh-comment-id:2730188810 --> @hugeBlack commented on GitHub (Mar 17, 2025): I get your point. Due to changes in Jitstreamer 0.2.4, livecontainer cannot use the old way to enable jit so instead it enable it after app launches. ~~For now, you can~~ 1. ~~Set the jit enabler to sidejitserver~~ 2. ~~leave address and udid blank~~ 3. ~~tap run, and the wait for jit dialog will appear~~ 4. ~~use the jitstreamer shortcut to enable jit~~ Edit: I made a new build so you can select "JitStresmer-EB (Relanch)" as the jit enabler to achieve this.
Author
Owner

@Awesome-guyy commented on GitHub (Mar 27, 2025):

This is is happening again with the newest release of JITStreamer.

<!-- gh-comment-id:2756084319 --> @Awesome-guyy commented on GitHub (Mar 27, 2025): This is is happening again with the newest release of JITStreamer.
Author
Owner

@hugeBlack commented on GitHub (Mar 27, 2025):

Download the latest nightly build and select jitstreamer eb (relaunch) https://nightly.link/hugeBlack/LiveContainer/workflows/build/main/com.kdt.livecontainer.ipa.zip

Edit: StikJIT support is now available, you may have a try.

<!-- gh-comment-id:2756086918 --> @hugeBlack commented on GitHub (Mar 27, 2025): Download the latest nightly build and select jitstreamer eb (relaunch) https://nightly.link/hugeBlack/LiveContainer/workflows/build/main/com.kdt.livecontainer.ipa.zip Edit: StikJIT support is now available, you may have a try.
Author
Owner

@Awesome-guyy commented on GitHub (Mar 30, 2025):

Edit: StikJIT support is now available, you may have a try.

It works! Thank you so much!
You need to set JIT mode to another livecontainer and make it a shared app. When LC2 boots you open stikjit and enable jit for LC1

<!-- gh-comment-id:2764656571 --> @Awesome-guyy commented on GitHub (Mar 30, 2025): > Edit: StikJIT support is now available, you may have a try. It works! Thank you so much! You need to set JIT mode to another livecontainer and make it a shared app. When LC2 boots you open stikjit and enable jit for LC1
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LiveContainer#366
No description provided.