First-time setup

Install path

1. 01

   Open and wizard

   Launch NX2Apple and complete the first-run wizard.

2. 02

   Tools / Xcode

   Let the dependency page install what it can. Use a suitable Xcode + iOS SDK; some NVN titles need a specific Apple download build.

3. 03

   Keys

   Add your prod.keys. Same keys open every title you own. Never email keys here.

4. 04

   Dumps

   Add base NSP/XCI, matching update, and DLC. Update display version must match the profile in GAMES.md.

5. 05

   Build and play

   Choose This Mac or iPhone / iPad → Build → Play (or sideload).

Why order matters

Building before keys exist fails loudly. Building with the wrong update version fails in ways that look like engine bugs. Building under the wrong Xcode generation fails in shader or Metal stages that are hard to read if you skip the dependency page. The wizard exists to linearize those prerequisites. When GitHub is slow, follow the in-app manual ZIP route instead of inventing your own clone flags. Newer releases may no longer need a repository download at all — if an old app insists on a missing repository, update first. Stopped builds can resume; do not delete the work folder mid-flight unless Troubleshoot tells you the cache is corrupt.

Keys and dumps without the illegal bits

This guide will not explain how to obtain prod.keys or commercial dumps from the internet. It will say where the app expects you to point at files you already have. Use the same keys for every title you dumped from your own console when that is how your dump toolchain works. Match update NSP display versions to the profile table in GAMES.md; mismatches are a leading cause of “it must be broken” reports. DLC belongs with the title that expects it; random shared folders of unrelated NSPs confuse selection UIs. Never paste keys into Discord screenshots, GitHub issues, or email to support@nx2apple.online.

This site is not official. We do not host installers, prod.keys, firmware, or game dumps. Downloads go to GitHub Releases. Bring your own legally obtained dumps and keys.

After the first successful game

Per-game launch options such as frame rate, docked versus handheld style modes, render scale, and language can persist across rebuilds. Mac saves and logs may live beside the app or under Application Support depending on library layout. On iPhone, check the Files app under the app name for save and log folders. Use Settings → Copy diagnostics when filing GitHub issues, and attach logs without keys or dumps. Language overrides via env.txt are documented upstream for advanced cases; prefer the in-app Game language row when it exists. Personal backup and circumvention rules differ by country. You are responsible for knowing the law where you live. Never distribute dumps, keys, firmware, or the packages you build. If you enjoy a game, buy it from legitimate storefronts. This independent guide does not provide a ROM search, key database, or firmware mirror.

• App ships many tools; .NET SDK 10 may still install on demand
• Stopped builds can resume where they left off
• Copy diagnostics for issues — never attach keys or dumps

FAQ

The wizard asks for a repository and fails.

Update to a current release first. Older builds expected a clone path that newer packaging removed.

Build says the update version is wrong.

Compare your update NSP display version with GAMES.md for that title and supply the matching update.

Where do keys go?

Use the in-app key prompts or documented paths inside the launcher. We do not host example key files.

Can I build two games at once?

Prefer one build at a time on a machine with limited disk and memory; finish or stop cleanly before starting another.