Question 1

How to fix 'Application verification failed: Failed to verify code signature' error 0xe8008015 when sideloading apps with iloader?

Accepted Answer

This error (0xe8008015: A valid provisioning profile for this executable was not found) usually occurs because Apple's device registration is not instantaneous. After adding a device to your Apple Developer account, it takes 24–72 hours to become fully active, and apps signed under that account cannot be installed until registration completes.

Fix:
1. Wait 24–72 hours after your first failed attempt, then try installing again.
2. If you have a paid developer account, check the Apple Developer portal (Certificates, Identifiers & Profiles > Devices): unregistered devices show a `Pending` tag in the status column. Once the pending status clears, sideloading should succeed.

No changes to iloader, iTunes, or your signing setup are needed—this is purely a waiting period on Apple's side.

Question 2

How to fix iloader Apple ID login error -20970 'Your account information was entered incorrectly'?

Accepted Answer

Error -20970 (GrandSlam auth error) during iloader login is often caused by the anisette server, not wrong credentials. Fix: switch the anisette server to "jkcoxson (mac)" in iloader settings and retry the login — you may need to attempt it several times before it succeeds. Also double-check your Apple ID email/password and ensure 2FA is handled via a trusted device.

Question 3

How to fix 'SMS 2FA request failed with http status 403' login error in iloader?

Accepted Answer

This 403 error during Apple ID login is usually caused by account mismatches or iCloud security settings. Try these fixes in order: 1) Open the App Store on your iPhone, tap the profile icon (top right), and verify the email shown exactly matches the Apple ID email you entered in iloader. 2) Make sure you are signed into iCloud with the same Apple ID on BOTH your computer and your iPhone. 3) Disable Advanced Data Protection: go to Settings → [your name] → iCloud → Advanced Data Protection and turn it off, then retry login. Note: disabling Advanced Data Protection reduces iCloud encryption security, so re-enable it after signing in if desired.

Question 4

How to fix iloader Apple ID login error -22406 or 'SMS 2FA request failed with http status 403'?

Accepted Answer

Error -22406 means the password was rejected by Apple's servers: re-enter your Apple ID password carefully (copy-paste to avoid typos, and test a password without special characters like `$` which may be mishandled). If you then hit 'Failed to complete SMS 2FA ... http status 403', note that SMS-based 2FA is currently broken in iloader. Switch your Apple Account's two-factor authentication to a Trusted Device instead of SMS, then retry the login.

Question 5

How to fix iloader 'Failed to get anisette data for login' error (502 Bad Gateway)?

Accepted Answer

This error is a server-side outage, not a problem with your PC or iPhone. iloader contacts the default anisette server (https://mac-ani.jkcoxson.com) to generate anisette data required for Apple ID login, and that server returned HTTP 502 Bad Gateway, meaning it was temporarily down. Fixes: 1) Wait and retry the login later — the anisette server typically recovers on its own. 2) Check the iloader GitHub issues page or Discord to confirm whether an outage is in progress before changing anything locally. 3) If iloader supports it, switch to an alternative or self-hosted anisette server instead of the default mac-ani.jkcoxson.com endpoint. Do not reinstall iTunes, re-pair your device, or change developer mode settings — the failure happens during Apple ID authentication, before any device communication, so local configuration is not the cause.

iloader

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects