[GH-ISSUE #58] [BUG][Feature Request] App Signatures expire after 7 days even if LiveContainer itself is refreshed #49

Closed
opened 2026-03-03 15:30:01 +03:00 by kerem · 2 comments
Owner

Originally created by @hugeBlack on GitHub (May 7, 2024).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/58

Describe the bug

I installed several apps inside LiveContainer in JIT-Less mode a week ago and they worked fine until today. The error said that the code signature is no longer valid. What's more, newly installed apps didn't work too. I had to delete and reinstall LiveContainer, then these apps again to make them run again.

This may indicate that LiveContainer still uses the certificate issued by SideStore 7 days ago. So I think it's reasonable for LiveContainer to auto detect the expiration of code signature and sign it again before running an app.

Instructions to reproduce

  • Enable JIT-Less mode
  • Install any app inside LiveContainer
  • Wait 7 days
  • Run the app again
  • See the 'Invalid signature' error

What version of LiveContainer are you using?

main/2d7bbe4

Other info

No response

Originally created by @hugeBlack on GitHub (May 7, 2024). Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/58 ### Describe the bug I installed several apps inside LiveContainer in JIT-Less mode a week ago and they worked fine until today. The error said that the code signature is no longer valid. What's more, newly installed apps didn't work too. I had to delete and reinstall LiveContainer, then these apps again to make them run again. This may indicate that LiveContainer still uses the certificate issued by SideStore 7 days ago. So I think it's reasonable for LiveContainer to auto detect the expiration of code signature and sign it again before running an app. ### Instructions to reproduce - Enable JIT-Less mode - Install any app inside LiveContainer - Wait 7 days - Run the app again - See the 'Invalid signature' error ### What version of LiveContainer are you using? main/2d7bbe4 ### Other info _No response_
kerem 2026-03-03 15:30:01 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@khanhduytran0 commented on GitHub (May 14, 2024):

Strange bug. The thing that actually expires after 7 days is supposed to be provisioning profile, which apps signed inside LiveContainer don’t use; cert should usually lasts 1 year.

<!-- gh-comment-id:2110254197 --> @khanhduytran0 commented on GitHub (May 14, 2024): Strange bug. The thing that actually expires after 7 days is supposed to be provisioning profile, which apps signed inside LiveContainer don’t use; cert should usually lasts 1 year.
Author
Owner

@hugeBlack commented on GitHub (May 14, 2024):

Strange bug. The thing that actually expires after 7 days is supposed to be provisioning profile, which apps signed inside LiveContainer don’t use; cert should usually lasts 1 year.

I found the reason. I used a same Apple ID in 2 devices which caused the provisioning profile to expire. I've created another Apple ID and LiveContainer worked fine now on these 2 devices. I'll reopen this issue if this happens again after 7 days.

<!-- gh-comment-id:2110261214 --> @hugeBlack commented on GitHub (May 14, 2024): > Strange bug. The thing that actually expires after 7 days is supposed to be provisioning profile, which apps signed inside LiveContainer don’t use; cert should usually lasts 1 year. I found the reason. I used a same Apple ID in 2 devices which caused the provisioning profile to expire. I've created another Apple ID and LiveContainer worked fine now on these 2 devices. I'll reopen this issue if this happens again after 7 days.
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#49
No description provided.