Install on iPhone or iPad

Before building the IPA

First complete the device and tool checklist. You need a build Mac, your own game files and keys, and a target device that meets nxnative’s documented requirements. Check the game’s profile for the version and platform evidence. If replacing an app, copy its saves outside the app first.

This page follows nxnative’s command-line workflow. A graphical community fork has its own setup and output conventions; do not mix instructions from separate projects halfway through a build.

Stage 1: Prepare the project and tools

The upstream README’s Pack an IPA section is the current setup reference. If starting from a new checkout, its repository is:

git clone https://github.com/seedds/nxnative.git
cd nxnative

Complete the upstream Xcode, Homebrew and dependency setup before the next stage. Note the checkout revision. The examples here are instructions to read and adapt on your own machine; this website does not execute them.

Stage 2: Build from one game folder

Use a folder containing that game’s base files and the matching updates or DLC you intend to include. Run from the nxnative checkout. Replace both example paths with your actual locations:

python3 scripts/build_ipa_from_nsp.py   "/path/to/game-folder"   -k "/path/to/prod.keys"

Checkpoint: the script finishes without a build error and reports an IPA output. Use the actual generated filename; it is game-specific. Keep the terminal output and any companion build index for the next build. A file that merely exists after an interrupted build is not a success check.

If the script fails, record the first failed stage and error before changing inputs. Recheck missing dependencies or a game/version mismatch. Do not jump to signing until packaging has succeeded.

Stage 3: Sign and install

The generated IPA is unsigned. The README lists tools such as AltStore, Sideloadly and LiveContainer; follow the current instructions and eligibility requirements for the one you choose. An alternative Xcode device workflow is documented upstream with --prepare-xcode and an Apple developer account.

Check whether your signing method supports the upstream-recommended Increased Memory Limit capability. Do not assume every tool or account configuration can apply it. If the installation tool reports a signing failure, save that error and resolve it in that tool before investigating in-game rendering.

Checkpoint: the installation tool reports success and the expected game app appears on the target device. This establishes installation, not gameplay compatibility.

Stage 4: Check the first launch

1. Open the app and note whether it closes before settings, during loading or after entering the game.
2. Where offered, begin with the game’s tested default settings. The upstream settings guide explains the available controls; options differ by game.
3. Check input and reach a point where you can verify progress. Record what you actually reached, not a general “works” result.
4. Keep a copy of the log if a problem occurs. Do not reinstall repeatedly before protecting the existing data.

Match the failure to the next step

First failed stage	What to keep	Next step
Build or packaging	Command, revision, first terminal error	Recheck upstream setup and game profile
Signing or installation	Tool version and exact error	Consult that tool’s installation documentation
Launch or game loading	Device, OS, game version and app log	iPhone crash checks
Save missing after replacement	Old backup, title and container information	Save backup and restore

This site supplies no IPA, game data or keys. The procedure is documentation-based and is not a claim that we have installed or played the game on your device.