[GH-ISSUE #782] [Feature Request] Add ability to export installed apps in LiveContainer as IPA files #705

New issue

Closed

opened 2026-03-03 15:35:44 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 15:35:44 +03:00

Owner

Originally created by @monsm on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/782

Hello LiveContainer team! First, thank you for developing such a useful tool for managing and isolating apps—it’s been incredibly helpful for testing and multi-account scenarios.

I’d like to propose a new feature: adding an option to export/backup installed apps within LiveContainer as IPA files. Here’s why this would be valuable:

Current Pain Point

Currently, LiveContainer relies on users retaining the original IPA files to reimport apps. If the original IPA is lost (e.g., deleted from local storage, expired TestFlight links, or inaccessible enterprise distribution), there’s no straightforward way to recover the app from the container. This forces users to go through complex workarounds (like extracting from device backups via third-party tools) which are often unreliable or require technical expertise.

Use Cases for This Feature

1.	Backup and Recovery: Users could easily backup apps installed in LiveContainer to avoid losing access if the original IPA is unavailable.

2.	Migration: Exported IPAs could be shared between devices (with proper re-signing) or reimported into LiveContainer on other devices.

3.	Preserving Modified Versions: If an app in LiveContainer has been modified (e.g., via tweaks or custom configurations), exporting it as an IPA would preserve those changes for later use.

Proposed Functionality

•	Add an "Export as IPA" button in the app’s details page within LiveContainer.

•	When triggered, the app’s containerized files (binary, resources, and modified configurations) would be packaged into a valid IPA.

•	Handle signing considerations: The exported IPA could retain the original signing identity (if possible) or prompt the user to re-sign it with a local certificate (to ensure installability on other devices).

Additional Notes

I understand that containerized apps may have modified file structures or injected code, but even a "snapshot" IPA that retains the app’s current state would be extremely useful. This feature would significantly improve LiveContainer’s utility as a backup and migration tool.

Thank you for considering this request! Let me know if you need more details or testing help.

Best regards,
Monsm D

Originally created by @monsm on GitHub (Aug 21, 2025). Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/782 Hello LiveContainer team! First, thank you for developing such a useful tool for managing and isolating apps—it’s been incredibly helpful for testing and multi-account scenarios. I’d like to propose a new feature: adding an option to export/backup installed apps within LiveContainer as IPA files. Here’s why this would be valuable: Current Pain Point Currently, LiveContainer relies on users retaining the original IPA files to reimport apps. If the original IPA is lost (e.g., deleted from local storage, expired TestFlight links, or inaccessible enterprise distribution), there’s no straightforward way to recover the app from the container. This forces users to go through complex workarounds (like extracting from device backups via third-party tools) which are often unreliable or require technical expertise. Use Cases for This Feature 1. Backup and Recovery: Users could easily backup apps installed in LiveContainer to avoid losing access if the original IPA is unavailable. 2. Migration: Exported IPAs could be shared between devices (with proper re-signing) or reimported into LiveContainer on other devices. 3. Preserving Modified Versions: If an app in LiveContainer has been modified (e.g., via tweaks or custom configurations), exporting it as an IPA would preserve those changes for later use. Proposed Functionality • Add an "Export as IPA" button in the app’s details page within LiveContainer. • When triggered, the app’s containerized files (binary, resources, and modified configurations) would be packaged into a valid IPA. • Handle signing considerations: The exported IPA could retain the original signing identity (if possible) or prompt the user to re-sign it with a local certificate (to ensure installability on other devices). Additional Notes I understand that containerized apps may have modified file structures or injected code, but even a "snapshot" IPA that retains the app’s current state would be extremely useful. This feature would significantly improve LiveContainer’s utility as a backup and migration tool. Thank you for considering this request! Let me know if you need more details or testing help. Best regards, Monsm D

kerem closed this issue

2026-03-03 15:35:44 +03:00

kerem commented

2026-03-03 15:35:45 +03:00

Author

Owner

@hugeBlack commented on GitHub (Aug 21, 2025):

We are actual human, do not use ChatGPT
The app itself, its data and tweaks are available in LiveContainer's folder, you can save them in whatever way you like.
LiveContainer cannot help you to save enterprise/TestFlight apps.

@hugeBlack commented on GitHub (Aug 21, 2025): 1. We are actual human, do not use ChatGPT 2. The app itself, its data and tweaks are available in LiveContainer's folder, you can save them in whatever way you like. 3. LiveContainer cannot help you to save enterprise/TestFlight apps.