Sources checked: 2026-11-11. Tested on a device by staff: not yet. Staff have no iPhone, so this is checked against the official pages linked at the bottom, not run on hardware. If you try it, reply with your device, iOS version and what happened, and I will add it here with the date.
Sideloadly's own FAQ lists the login and signing errors below. Work down the list; stop when it works.
1. Check the clock. "The identity used to sign the executable is no longer valid" and "A valid provisioning profile for this executable was not found" are both tied to wrong date and time. Set the correct time on both the computer and the iPhone or iPad, then retry.
2. "Your session has expired. Please log in." or "possible environment mismatch". The FAQ points to a fix posted on the r/Sideloadly subreddit rather than giving steps itself. We have not been able to read that post, so we do not repeat it here.
3. "Failed to obtain anisette: 500 INTERNAL SERVER ERROR". This is a server error on the Remote Anisette option. Try again later, or switch to the Local Anisette option under Advanced Settings.
4. "Your maximum App ID limit has been reached. You may create up to 10 App IDs every 7 days." This is an Apple limit on free accounts, not a login fault. Wait a few days or use a different Apple ID. See our guide on the 3-app and 10 App ID limits.
5. Windows: iTunes and iCloud. If you installed iTunes from the Microsoft Store, uninstall it and install the standalone version from Apple, then connect the device, sync once, and open Sideloadly. The same applies to the "NP_E_CONN_FAILED" and "AFC_E_MUX_ERROR" errors.
6. "error 'machineName'". A few members reported that changing the computer's name fixed it.
7. Community report, not official. An iOSGods support thread has several people saying that authorizing the computer in iTunes (Account, then Authorize This Computer, signing in with the Apple ID) and then reinstalling Sideloadly fixed a sign-in failure, including with two-factor authentication on. We have not tested this. Treat it as a thing to try, not a guarantee.
Reported right now, unverified: a post on r/Sideloadly describes Sideloadly v0.71.1 failing Apple login with error -80046. We only saw the post title in search, so we do not know the cause or whether it is fixed. The current version shown on sideloadly.io on 2026-11-11 is v0.71.0.
What this guide does not cover: two-factor codes that never arrive, locked Apple IDs, and anything that needs Apple's account recovery. Those are Apple's to resolve.
Sources
This may break. Apple, the tools and their servers change without notice. If a step here fails for you, say so in this thread and the correction will go in the same place as the error.
Which error text do you see, and on which OS? Post it exactly.
- Marlow, Editorial
Sideloadly's own FAQ lists the login and signing errors below. Work down the list; stop when it works.
1. Check the clock. "The identity used to sign the executable is no longer valid" and "A valid provisioning profile for this executable was not found" are both tied to wrong date and time. Set the correct time on both the computer and the iPhone or iPad, then retry.
2. "Your session has expired. Please log in." or "possible environment mismatch". The FAQ points to a fix posted on the r/Sideloadly subreddit rather than giving steps itself. We have not been able to read that post, so we do not repeat it here.
3. "Failed to obtain anisette: 500 INTERNAL SERVER ERROR". This is a server error on the Remote Anisette option. Try again later, or switch to the Local Anisette option under Advanced Settings.
4. "Your maximum App ID limit has been reached. You may create up to 10 App IDs every 7 days." This is an Apple limit on free accounts, not a login fault. Wait a few days or use a different Apple ID. See our guide on the 3-app and 10 App ID limits.
5. Windows: iTunes and iCloud. If you installed iTunes from the Microsoft Store, uninstall it and install the standalone version from Apple, then connect the device, sync once, and open Sideloadly. The same applies to the "NP_E_CONN_FAILED" and "AFC_E_MUX_ERROR" errors.
6. "error 'machineName'". A few members reported that changing the computer's name fixed it.
7. Community report, not official. An iOSGods support thread has several people saying that authorizing the computer in iTunes (Account, then Authorize This Computer, signing in with the Apple ID) and then reinstalling Sideloadly fixed a sign-in failure, including with two-factor authentication on. We have not tested this. Treat it as a thing to try, not a guarantee.
Reported right now, unverified: a post on r/Sideloadly describes Sideloadly v0.71.1 failing Apple login with error -80046. We only saw the post title in search, so we do not know the cause or whether it is fixed. The current version shown on sideloadly.io on 2026-11-11 is v0.71.0.
What this guide does not cover: two-factor codes that never arrive, locked Apple IDs, and anything that needs Apple's account recovery. Those are Apple's to resolve.
Sources
- Sideloadly FAQ (errors section)
- sideloadly.io (version shown)
- iOSGods thread: community reports on iTunes authorization (unofficial)
- r/Sideloadly (error -80046 post, title only)
This may break. Apple, the tools and their servers change without notice. If a step here fails for you, say so in this thread and the correction will go in the same place as the error.
Which error text do you see, and on which OS? Post it exactly.
- Marlow, Editorial
Last edited: