mirror of
https://github.com/LiveContainer/LiveContainer.git
synced 2026-04-25 17:15:50 +03:00
[GH-ISSUE #469] Issues enabling JIT when installed with AltStore Classic via AltStore PAL #429
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#429
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 @David-mca on GitHub (Apr 23, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/469
Describe the bug
So i just switched from normal AltStore to AltStore Classic that i downloaded from AltStore PAL
After installing Live Container and trying to patch AltStore i get "Error The File "com.rileytestut.AltStore" couldnt be opened because there is no such file".
Instructions to reproduce
Try to patch AltStore Classic installed from AltStore PAL.
What version of LiveContainer are you using?
3.4.0-release
Other info
No response
@hugeBlack commented on GitHub (Apr 24, 2025):
Altstore issue. We are trying to talk to riley to add the same import certificate feature, no eta.
@JonRevo commented on GitHub (May 13, 2025):
Altstore classic has just received an update to 2.2.1 (48). Can anyone test if this is fixed?
@apfelbasti commented on GitHub (May 14, 2025):
No, I think, it‘s not fixed.
@hugeBlack commented on GitHub (May 16, 2025):
2.2.1 implemented export certificate feature. You can now use "Import Certificate From AltStore".
@tristan-k commented on GitHub (May 17, 2025):
@hugeBlack Tapping the
Import Certificate From AltStoreopensAltStore PALrather thanAltStore Classic.https://github.com/user-attachments/assets/e9716a2f-4f87-42de-8136-c08bc2b8f62e
@hugeBlack commented on GitHub (May 17, 2025):
@tristan-k we are already aware with this issue and it will be fixed in the next release. For now please temporarily hide Altstore PAL with password and unhide it after the certificate is imported.
@ginkogruen commented on GitHub (May 17, 2025):
Should it also say "Patch detected" when the certificate is imported? For me the Patch is not detected and testing leads to "Unsupported installation method" even though I did install LiveContainer through AltStore.
@tristan-k commented on GitHub (May 17, 2025):
I dont think so. Patching is a seperate process which is only required if you want to run apps with jit. That being sad I'm unable to patch
AltStore Classicbecause I'm getting another error after tappingAltStore patchen.@hugeBlack commented on GitHub (May 17, 2025):
@tristan-k You cannot patch Altstore classic installed by altstore pal. The only way to enable jitless mode is to import certificate.
@tristan-k commented on GitHub (May 17, 2025):
Thanks. Now I am confused 😵💫 I already imported the altstore cert via
Import Certificate From AltStore.EDIT:
I got it working. You proably meant to write
.mobiledevicepairingfile.I was able to follow the instructions at faq.altstore.io and import the
.mobiledevicepairingfile in StikDebug.