LiveContainer has S2Arm, but no game resources

An advanced community route: check the IPA, guest directory, file picker and resource integrity without confusing sideloading with normal launcher installation.

Advanced community route. If you are starting for the first time without a specific sideloading requirement, use normal launcher installation. This page explains reported failure points and links to a community method; it is not a device-tested universal tutorial.

Why installing the IPA is not enough

The IPA supplies the app. Resources must also reach its correct data directory. S2Arm inside LiveContainer is a guest of the host app; a normal launcher looking up a system app by bundle ID may not find it.

The #469 reporter described success with one game using Windows 11, S2Arm v0.2.3 and LiveContainer 3.8.12. Other versions, hosts and games are not established by that report.

Check the IPA first

In v0.2.1 / v0.2.2, building did not directly provide an updated unified container IPA, creating a risk of using an old package. Starting with v0.2.3, the release notes say a successful iPhone build generates S2Arm.ipa in the library root, with a Show .ipa action. Use the output of the current build rather than mixing an old single-game package with new resources. #360

File picker failure or missing resources?

If import, export or cloud-save folder selection does nothing, the #469 reporter described an LC setting: long-press the S2Arm card → Settings → Fixes → Fix File Import, then exit and reopen the guest. Labels can vary with LC language. This addresses the reported file-picker behavior; it does not generate missing game resources. Reporter follow-up

romfs.img or error -8

Copying the computer's pack directory directly may not be enough. In the reported case, split resources and mappings needed a large image generated according to the package index before transfer. An interrupted multi-file copy can also fail integrity checks. Error -8 is not always the same cause.

What the community method adds

The full #469 method involves:

Identifying the host bundle ID after its actual signing, rather than assuming the original ID.
Finding this S2Arm guest's directory, without copying another person's UUID or device ID.
Using upstream tools for a read-only transfer plan to check the destination and index requirements.
Generating the required romfs.img from this resource package's own index, transferring it to the guest and verifying it.
Opening S2Arm inside LC, waiting for import and integrity checks, then launching.

Commands are in the reporter's original thread. Its paths, sizes, hashes and device parameters belong to that setup. If you cannot identify your guest target or package index, stop and ask for help with versions and an error summary. Reinstalling the IPA alone will not restore missing data.

The reporter also noted host-signing memory capabilities. App installation, resource completeness and runtime permissions are distinct. A memory-related exit after launch is not automatically a request to recopy resources. This guide does not instruct entitlement changes or validate signing-tool combinations.

Is a simpler export available?

In #502, the maintainer described work toward a small shell IPA and separate single-file game data export, without committing to a release. The reviewed v0.2.8 release does not confirm that delivery. Its empty-app installation fix concerns the normal Windows launcher flow, not proof of a new LiveContainer export feature. Do not treat a planned drag-in file workflow as an existing button.

Success check: Resources in the correct guest pass integrity checks and the game actually launches. Evidence is one user's reported environment and maintainer acknowledgment; this site has not reproduced it. Include host version, installation method and failure stage in a report.