mirror of
https://github.com/LiveContainer/LiveContainer.git
synced 2026-04-25 09:05:53 +03:00
[GH-ISSUE #918] [BUG] JIT activation with StikDebug sometimes doesn’t open PiP #819
Labels
No labels
bug
compatibility
enhancement
multitasking
pull-request
safe area
status: broken
status: usable
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LiveContainer#819
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mak448a on GitHub (Oct 20, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/918
Describe the bug
When launching an app with JIT, the StikDebug PiP never shows up.
Instructions to reproduce
After setting up with utmjit.js in the settings for an app, launch it.
https://github.com/StephenDev0/StikDebug/issues/279
What version of LiveContainer and iOS are you using?
3.6.55-Release (main/2b020ad)
Other info
No response
@hugeBlack commented on GitHub (Oct 20, 2025):
@Vishram1123 I can also confirm this issue. Please take a look and see if you can fix it.
@CelloSerenity commented on GitHub (Oct 20, 2025):
Whew, I thought I was the only one. @mak448a, which StikDebug version are you on? Does it have the new logo?
@mak448a commented on GitHub (Oct 20, 2025):
Yes, it’s the one with the new logo.
As a workaround, you can side load any app that requires JIT outside LiveContainer, activate JIT, then switch back to the app you needed in LiveContainer.
@Vishram1123 commented on GitHub (Oct 20, 2025):
From what I'm seeing in the StikDebug codebase, there don't appear to be meaningful changes to the URL parser, so this most likely isn't that. I will investigate later today into what is happening
@Vishram1123 commented on GitHub (Oct 21, 2025):
Looks like https://github.com/StephenDev0/StikDebug/issues/283 is related to this. This seems to happen when just launching an app with a script using the stikjit:// url scheme.
Edit: TLDR it seems to be a race condition with the app being launched before the developer disk image is mounted, specifically when using the url scheme
Edit 2: It seems like it is with the heartbeat, not the developer disk image
@burneracct07 commented on GitHub (Oct 21, 2025):
I don’t know what this PiP stuff is, but I do know that StikDebug has enabled JIT for me even when I had to wait for the heartbeat upon app launch.
@Vishram1123 commented on GitHub (Oct 22, 2025):
If you aren't on a TXM-enabled device, you don't need PiP to activate JIT. Also the problem is that StikDebug doesn't wait for the heartbeat before switching to the other app.
@StephenDev0 commented on GitHub (Oct 22, 2025):
It does wait for the heartbeat because an active heartbeat is needed to launch an app.
@Vishram1123 commented on GitHub (Oct 22, 2025):
Is it perhaps not waiting for the PiP to initialize? I see that in the code there is a hardcoded 0.5s wait time; maybe this isn't long enough for initialization?
@CelloSerenity commented on GitHub (Oct 25, 2025):
It just started working for me again with the latest LC nightly, interesting…
@Vishram1123 commented on GitHub (Oct 25, 2025):
No, it doesn't seem to work for me. Tested with UTM and Amethyst
@jaden465 commented on GitHub (Oct 28, 2025):
Yeah hasn’t worked for me on Dolphin,MeloNX, Amethyst, really anything that’s needed JIT with this new pip thing.
@Vishram1123 commented on GitHub (Oct 28, 2025):
As an alternative, you can launch LiveContainer through StikDebug, then launch your requested app while keeping the StikDebug PiP window open.
@jaden465 commented on GitHub (Oct 28, 2025):
Hmm, did I do something wrong here? I did it off camera with dolphin but does the same thing, just instant crash. GitHub was being stupid so had to upload video on catbox
https://files.catbox.moe/6x74mp.mp4
@Vishram1123 commented on GitHub (Oct 31, 2025):
Did you close the PiP window manually? Or did it close itself?
@jaden465 commented on GitHub (Oct 31, 2025):
It closed by itself
@CelloSerenity commented on GitHub (Nov 10, 2025):
Closed by StephenDev0/StikDebug#288