Skip to Content
s2arm.online

TROUBLESHOOTING

S2Arm signing fails with Apple error 9401

Distinguish Apple error 9401 from an expired Windows sign-in (1100), device connection failures and signing limits.

Source baseline v0.2.8Source review 2026-11-11Not device-tested by this site
On this page

Use this for Developer API error 9401 or an unavailable App ID / Identifier during signing or installation. Password failures, disconnected devices and crashes after launch are different problems.

What the documented fix covers

An older Windows version changed bundle-identifier capitalization, conflicting with records on Apple's side. v0.2.3 fixed that case, and the #408 reporter confirmed installation after updating. That fix itself does not require rebuilding the game.

Work through these checks

  1. Check the computer launcher version. If earlier than v0.2.3, back up saves and get a stable release containing the fix from the official releases.
  2. Check the signing account. In Impactor on Windows or Xcode on Mac, use the same personal account that installed the app. Changing accounts changes signing identity and is not the first troubleshooting step.
  3. Retry normal installation of the existing game. Let the newer launcher handle the old identifier. Do not manually rename the bundle or delete developer records.
  4. Follow the new result. If installation passes, finish resource import. If it still reports 9401, record the current version and exact error for #408.

Similar signing errors are different

MessageMeaning to investigate
device_not_connected / device_lockedConnection or locked device; see device detection
free_appid_limit / Apple 9120Account identifier registration limit; deleting a phone app does not directly restore that allocation
free_app_limitSelf-signed app slots on the device, not necessarily an identifier conflict
apple_session_expired / Apple 1100 on WindowsRenew the saved Impactor sign-in using the steps below; this is not the 9401 identifier conflict
Login or verification-code failureFinish account verification; rebuilding a game does not repair account access

The baseline S2Arm design uses one app for the game library. Do not apply the old assumption that every additional game takes another app slot. Architecture source

Success check: Signing and installation pass. Resource import and actual launch remain separate. A later launch problem in the same issue thread does not make every crash a 9401 problem.

Evidence: maintainer release notes and the original reporter's installation confirmation; not device-tested by this site.

Windows Apple error 1100: sign-in expired

v0.2.8 identifies an expired saved Apple login as Apple ID sign-in expired (apple_session_expired, Apple 1100). An earlier generic installation failure may have hidden this cause. Use Open Impactor to sign in again in the Windows installation flow.

  1. In Impactor, open Settings and select the same Apple ID used for this installation.
  2. Remove its saved account entry there, then add that same account again. This renews its login; it does not mean deleting your Apple account or uninstalling the phone app.
  3. Complete email, password and device verification-code prompts inside Impactor. Follow its input guidance, including switching to an English input method if needed. Do not enter the password into S2Arm or this website.
  4. Return to S2Arm and retry installation. Check that signing passes before continuing resource transfer.

This recovery is for Windows Impactor. On Mac, follow the Xcode account check instead. Do not rebuild games or change keys to fix an expired login. If 1100 remains, preserve the current error summary without account secrets. v0.2.8 release · Versioned recovery rules

On this page