S2Arm game or keys import failed

Use the exact import error to distinguish missing base content, incomplete files, outdated keys, permissions and library index problems.

This page concerns Add Game or keys import on the computer. Building and phone-side resource import happen later and need different checks.

Open the result details first

Record whether the failed item is the base, an update or a DLC, and capture its error code. A partially successful batch does not mean every item succeeded. Work on the failed items first.

Error	Check	Next action
`input_base_missing`	Only an update / DLC was supplied	Add your own base game
`content_truncated`	Incomplete file content	Copy the complete file again from your own original source
`ticket_missing`	Required ticket missing from the input	Check that input's completeness; do not assume keys are invalid
`keys_missing` / `keys_invalid`	Complete valid keys not selected	Select your own complete `prod.keys`; do not hand-write key values
`keys_outdated`	Keys do not cover the content version	Prepare newer keys from your own device and retry
`permission_denied`	Selected location is inaccessible to the app	Allow the needed folder access in system permissions
`input_missing`	Original moved or storage disconnected	Reconnect storage and check the original location
`guest_isa_unsupported`	Unsupported game architecture	Check game support; repeated import will not add it

These distinctions come from v0.2.8 error handling. A generic content_unreadable message calls for checking the file and tickets; it does not automatically prove outdated keys.

An older message may blame keys for a file problem

In #115, an incomplete DLC led to misleading keys advice. #242 involved missing source tickets blocking otherwise valid keys. When the same keys read some content but not another file, inspect that failed file too.

Those discussions include merged fixes. We do not infer the first release from merge dates; the v0.2.8 rules distinguish these causes.

Changed library, but an old location blocks import

Check both the selected library and the original files. v0.2.4 lists the stale library record fix associated with #432. On an older version, update and try import again.

If the original really moved, updating cannot restore it. Restore access or import from its new location. Not every disconnected-location message is that historical bug.

Windows import immediately raises UnicodeDecodeError

The original #514 issue involved an index written using a non-UTF-8 Windows system encoding. v0.2.7 addressed that import failure, but its handling could leave existing game names garbled on affected systems. Use v0.2.8 and reopen the library before retrying import. Do not edit catalog.json manually.

Windows game names became garbled after updating

This is an index-display problem reported after upgrading to v0.2.7, especially on Chinese and other non-Western Windows installations. It is not the same as an unreadable NSP/XCI or invalid keys.

Finish active tasks, close S2Arm and update to the full v0.2.8 package.
Open your existing library once. The release notes say affected names are restored automatically, including a direct v0.2.6 → v0.2.8 upgrade.
Check the names and entries. The original index is backed up as catalog.json.<system encoding>.bak; leave that backup in place rather than rewriting or deleting records.

Upstream states that games, saves and game files are unaffected by this index repair. This site has not reproduced it with a real library. If names remain wrong, record the Windows display/system locale, previous and current S2Arm versions, and a redacted example for a report.

First Add Game says another task is running

On older Windows builds, extracting the launcher into the default game-library directory could prevent library setup and produce a misleading busy message before the first import. v0.2.8 chooses an unused empty library folder automatically in that case.

Update, reopen and retry Add Game. If library setup still fails, inspect the specific reason and use Try again or Choose another folder. Keep the library separate from launcher files. An actual ongoing build/import still needs to finish; this fix does not make concurrent tasks safe. Release and recovery controls

Success check: The game appears with the correct version and required content, and failed items have been addressed. Continue Windows build step 4, Mac phone build step 4, or Mac local build step 4.

Still failing? Share versions, file types and an error summary in a report, never game files or keys. This site has not tested conversion of real game files.