Apple ID sign-in works again. Since 2026-10-12 Apple's sign-in server has refused iPASide (and AltStore, SideStore and iloader) with Apple error -80045: This action cannot be completed at this time. for every account.
Two things changed on Apple's side, and iPASide now handles both:
- The device identity. iPASide's anisette data comes from Apple's Android libraries, but it reported a Mac. Apple now rejects that at the first request. iPASide now sends one Windows identity to every Apple service (sign-in, two-factor, developer services).
- Two-factor. Apple now pushes the verification code during the second sign-in request and flags it with
hsc 409, instead of naming the second factor. iPASide missed that, asked for the final tokens straight away, and got-22411while your phone showed a code. It now asks for the code Apple already sent.
Also new: %LOCALAPPDATA%\iPASide\gsa-trace.log records one line per Apple sign-in request (step, HTTP status, Apple's error code), and never a password, token or response body. If sign-in fails, attach it to your report.
Verified: a live sign-in with a trusted-device 2FA account, end to end (password, code, tokens), and Apple's developer services read back the team, certificates and App IDs. 576 engine tests and 789 app tests pass; CI built the installer on a clean machine; the installed app starts, keeps the account, and closes with exit code 0 and no process left behind.
Not verified: installing an app after this change (certificate creation, signing and install were not re-run). Apple has changed this rule several times since 2026-10-12, so it may need further updates.
The installer is unsigned, so SmartScreen will warn — the SHA-256 is in SHA256SUMS.txt.