iPASide 1.1.2
Fixed
Signing IPAs larger than about 2 GB
Big apps — a 4 GB game, for instance — failed the moment signing started, with "Unzip failed!". The bundled signer read archives through a 32‑bit file layer on Windows and couldn't reach the index of an IPA over 2 GB. It now uses 64‑bit file access for both reading and repacking. Proven by signing a real 4.19 GB IPA end to end and installing it on a phone. Apps under 2 GB were never affected — which is why most apps signed fine.
Signing in could get stuck on a cryptic archive error
If the one‑time download of Apple's provisioning libraries was blocked (a proxy or error page arriving instead of the file), or a first run was interrupted and left a half‑written cache, every later launch failed with a raw "not a gzip/bzip2/xz/tar file" error — and the only way out was to find and delete a file by hand. iPASide now discards an unusable cache and rebuilds it, checks the download really is the library archive (and retries), and shows a clear "the provisioning server may be down or your network is blocking it" message instead.
If you're already stuck on that error on 1.1.1 or earlier, deleting %LOCALAPPDATA%\iPASide\anisette\anisette.bin and signing in again clears it.
Verified end to end on a physical iPhone: a 4.19 GB IPA provisioned, signed, and installed (0→100%). The installer is unsigned, so SmartScreen will warn — the SHA‑256 is in SHA256SUMS.txt, and the in‑app updater checks it automatically.