NX2Apple: Mac GUI & iOS IPA guide

What NX2Apple does

NX2Apple is a community GUI fork of nxnative. Its launcher organizes build stages and a game library; the engine and per-game work come from nxnative plus the fork’s patch queue. It can target This Mac or iPhone / iPad. It is a separate project with its own releases, setup and storage rules, rather than an official seedds/nxnative distribution.

This guide checks the README at 68eba1d and release v0.7.2 on 30 October 2026. We read these sources; we have not installed the launcher, built a game or tested gameplay.

NX2Apple download and prerequisites

Download the maintainer-recommended NX2Apple-macOS-arm64.zip for v0.7.2 from GitHub Releases, then unzip it and follow that release’s installation steps. Version note: the pinned README still names NS-Port-Builder-macOS-arm64.zip; use the v0.7.2 release instructions.

Checkpoint	Checked requirement	What it establishes
Open the launcher	Apple silicon Mac, macOS 13+	The launcher can open; this does not make the build toolchain available.
Build an NVN game	Xcode 27.1 on macOS 26.6+, with the required SDKs	The documented build route; do not treat an older launcher’s successful start as passing it.
Python and build tools	Included in the packaged app	Do not repeat the upstream CLI Homebrew/Python installation inside this app’s environment.
.NET	Dependency page checks .NET SDK 10 and can install it	Bundled Python does not remove this dependency check.
Build for iPhone/iPad	Xcode’s iOS SDK, plus the target device requirements	An iOS output remains subject to signing, device and game-version conditions.
Inputs	Your own game files and prod.keys	The launcher does not supply them. The key file is not a purchased app activation code.

The fork README describes iOS 26+ and a recent iPhone, with older devices untested. Separately, the upstream nxnative hardware route documents iOS/iPadOS 26+, an appropriate A17 Pro-or-later iPhone chip, or an M1-or-later iPad. These are attributed requirements, not evidence that NX2Apple has tested every matching device. Use the device checker for the stated upstream prerequisites and then check the fork’s release and game profile.

First setup and build checkpoints

1. Download and unzip the maintainer’s arm64 release. Follow its first-open instructions; the checked README describes right-click Open because the launcher lacks a paid developer signature.
2. In setup, use Download repository. The README describes a shallow project checkout under ~/NX2Apple and offers a manual ZIP route if GitHub is slow. The app manages this checkout; you do not need to substitute a terminal clone from another workflow.
3. Review the dependency page, including Xcode, the iOS SDK and .NET SDK 10. Keep a failed check and its actual message rather than skipping compiler checks.
4. Select your own one-game folder, or the base/update/DLC inputs and your own prod.keys. Match the game update to the selected profile. Do not upload these files to this site or an issue.
5. Select This Mac or iPhone / iPad, then build. Watch the actual stage and keep the first failure. A progress badge or detected title is not proof that the final app works.
6. For Mac, inspect the resulting library entry and test the specific launch, controls and save checkpoints yourself. For iPhone/iPad, continue to IPA signing and installation. The checked README says iPhone builds are unsigned; generating an IPA does not complete signing or installation.

Use the existing signing guide for the conditions of each route. Do not assume all signing tools preserve the same entitlements, or that a launcher removes a game’s memory and hardware requirements.

Current RomFS format and older installs

At the checked revision, the fork writes one romfs.img. Its earlier romfs.idx shard archives are no longer read. If an iPhone still holds that older archive, the README says to send the game data again through the launcher in the current single-image format.

Follow the NX2Apple build’s own transfer instructions. Do not substitute an upstream CLI device path, mix data from another build, or assume that an old shard archive and the new image are interchangeable. Before replacing an app or data, back up existing saves. The fork documents its own library-relative and fallback save/log locations; an upstream path is not automatically the right destination here.

Black screens and a useful error report

The v0.7.2 author release notes describe a repair for some Mac games opening to a black screen: pipeline archives are generated for the build Mac’s OS version rather than the SDK version, avoiding the reported first-launch recompilation case. This is a release-author claim about that failure path, not our reproduction, a universal black-screen fix or a frame-rate guarantee. Preserve the release and full error if your symptoms differ.

For help, collect the actual NX2Apple release, engine revision if shown, game/title ID and update, Mac system, target device/system, first failed stage, Settings > Copy diagnostics, and the game log. Review diagnostics and logs for private identifiers before sharing. The README identifies log.txt on iPhone and platform-specific Mac log locations. Use the maintainer’s issue forms; never attach keys, game files or extracted game content.

NX2Apple or the upstream command line?

Prefer	NX2Apple GUI route	Upstream CLI route
Setup style	Wizard and packaged Python/build tools; its dependency page manages checks	Prepare the interpreter and dependencies documented at your checkout.
Build selection	Pick This Mac or iPhone/iPad in the launcher	Use the target and options documented for that upstream script.
Transfer and saves	Follow this fork’s launcher and current image format	Follow the actual build’s printed command and upstream storage instructions.
Diagnosing a failure	Include the GUI release, stage and diagnostics	Include the commit, command target and first traceback.

Choose based on the workflow you want to maintain, not an assumed compatibility advantage. Read the Mac build and troubleshooting guide for the upstream route, iOS installation guide for signing checkpoints, or nx2android for the separate Windows-to-Android project. Our player tools generate local text and check stated conditions; they do not run NX2Apple or verify a game’s performance.