Sources checked: 2026-11-11. Tested on a device by staff: not yet. This is compiled from the vendors' own pages, not from running it on a phone.
- 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 tied to a wrong date and time. Set the correct time on the computer and the device.
- "Failed to obtain anisette: 500 INTERNAL SERVER ERROR". A server error on the Remote Anisette option. Try later, or switch to Local Anisette under Advanced Settings.
- "Your maximum App ID limit has been reached". An Apple limit on free accounts, not a login fault. See "What are the 7-day, 3-app and 10 App ID limits?".
- Windows: iTunes and iCloud. If iTunes came from the Microsoft Store, uninstall it and install the standalone version from Apple, connect the device, sync once, then open Sideloadly. The same applies to "NP_E_CONN_FAILED" and "AFC_E_MUX_ERROR".
- "error 'machineName'". A few members reported that changing the computer's name fixed it.
- Community report, not official. Several people on an iOSGods thread say authorizing the computer in iTunes (Account, Authorize This Computer) and reinstalling Sideloadly fixed a sign-in failure. We have not tested it.
If you see a "session expired" or "possible environment mismatch" message, Sideloadly's FAQ points to a fix on its subreddit that we could not read, so we do not repeat it.
This guide does not cover two-factor codes that never arrive or locked Apple IDs. Those are Apple's to resolve.
If you see error -80046 on Sideloadly v0.71.1, that is a reported but unverified issue; see https://nabzclan.vip/threads/69/.
Full guide: https://nabzclan.vip/threads/58/
These steps can stop working when Apple or the tools change. The forum thread linked above is kept up to date; check it for the latest.