LNPANDY/NX2Apple

选用指南

AI 根据 README 整理 · 2026/10/24 21:56:30

适用场景

适用于希望将自有的Switch游戏转制到iPhone/iPad上游玩的场景，特别是大型游戏因文件过多导致安装失败的问题。

查看 README 依据

# NX2Apple **Play your own Nintendo Switch games on an iPhone or iPad.** Point a macOS app at your own game dumps and it runs the whole pipeline: unpack, rewrite the game's code for Apple silicon, translate its shaders to Metal, and pack a slim IPA plus a sharded RomFS archive that a phone can actually install — then tells you the three steps to get it onto the device. <img src="frontend/screenshots/main-window-en.png" width="620" alt="NS Port Builder"> The project is based on **[nxnative](https://github.com/seedds/nxnative)** — the NSO rewriter, the

- **The IPA does not install.** A 16.6 GB package with 372,660 entries fails on iOS with `PackageExtractionFailed (Could not extract archive)`. The install daemon's extractor gives up — one directory holds 75,941 files and the ZIP64 central directory starts at 17.8 GB. - **Copying the tree to the phone takes hours.** The Files app and Finder do one round trip per file. 300,000 small files also produce roughly 1 GB of filesystem block overhead. Packing the tree into ~100 shard files solves both: the package stays small, and the game files move to the phone as one folder of large files.

目标用户

面向不熟悉命令行、希望用图形界面完成整个转制过程的用户。

查看 README 依据

Horizon host, the NVN-on-Metal layer and the per-game profiles are upstream work, and this fork follows upstream automatically. What it adds: - **A GUI app for everyone.** [NS Port Builder](frontend/README.md) walks a first-time user through the whole build: four inputs picked separately (or one folder for all), device dependencies detected and installed with one click, progress from the build's own stages, and an install guide with Reveal-in-Finder buttons at the end. English by default; Chinese on Chinese devices.

使用方式

提供macOS图形界面（NS Port Builder）和命令行两种使用方式，图形界面引导用户完成构建，命令行脚本可单独使用。

查看 README 依据

Horizon host, the NVN-on-Metal layer and the per-game profiles are upstream work, and this fork follows upstream automatically. What it adds: - **A GUI app for everyone.** [NS Port Builder](frontend/README.md) walks a first-time user through the whole build: four inputs picked separately (or one folder for all), device dependencies detected and installed with one click, progress from the build's own stages, and an install guide with Reveal-in-Finder buttons at the end. English by default; Chinese on Chinese devices.

DLC, `prod.keys`), a dependency panel that detects and installs what is missing, the script's real stage list with live percentages, and the archive shards produced at the end. <details> <summary>界面截图（点开）</summary> <img src="frontend/screenshots/main-window.png" width="620" alt="NS Port Builder"> </details> ```bash cd frontend && swift run # or double-click frontend/NS Port Builder.app ``` The interface is bilingual: it follows the device (Chinese for any Chinese variant, **English for everything else**) and the `中文` / `EN` button in the title bar switches at any time.

部署要求

需要macOS环境、Xcode、Homebrew工具、Python包，以及从自己主机导出的prod.keys和游戏NSP文件。

查看 README 依据

[README](https://github.com/seedds/nxnative) to install Xcode, Homebrew tools and the Python packages, then pack an IPA. ```bash git clone https://github.com/<you>/NX2Apple.git cd NX2Apple brew install xcodegen zstd spirv-cross brew install --cask dotnet-sdk python3 -m pip install lz4 capstone fonttools backports.zstd ``` ### 2. What you need on disk Three things, none of which ship with the repository: | What | Where it comes from | Used by | |---|---|---| | **`prod.keys`** | dumped from **your own console** (see below) | the extractor, to decrypt your game |

| **The game's NSPs** | dumped from your own cartridge or eShop purchases | the extractor | | **Xcode + iOS SDK** | the App Store | the app build | `prod.keys` is the console's key set — a text file of `name = hex value` lines (~230 entries: `master_key_xx`, `titlekek_xx`, `header_key`, `key_area_key_application_xx`, …). Every Switch homebrew tool reads this format. It is **not** tied to a specific game: one `prod.keys` decrypts any of your games. The only requirement is that the file contains keys for the key generation

已知限制

归档只读，不支持写入；查找区分大小写；索引保存在内存中；无去重或压缩。

查看 README 依据

**Sideloadly** does not. See [dm/ios/ENTITLEMENTS.md](dm/ios/ENTITLEMENTS.md) for the steps and how to tell from `Documents/log.txt` (resident + headroom: ~3,375 MB = not in effect, 6–8 GB = it is). ## Limitations - **Read-only.** The archive is never written; saves and temp data go to their own mounts as before. - **Case-sensitive lookup.** Names are stored as the source tree had them, so the host's case-insensitive alias machinery (for APFS) is bypassed for archive entries. - **Symlinks are followed at pack time.** No supported game's RomFS has any.

- **The index is held in memory.** 28 MB for Tears of the Kingdom (17.9 MB of it names). Shards are not. - **No dedup or compression.** Shards are the source bytes verbatim, so `verify` is a plain comparison and a repack is deterministic. ## Credits All of the emulation work is other people's. This repository adds the archive subsystem on top: - **[nxnative](https://github.com/seedds/nxnative)** (MIT) — the native-execution toolchain this repository is built from: the NSO rewriter, the Horizon host layer, NVN-on-Metal, the per-game profiles and the iOS shell.