A clearer message for Apple's certificate limit (#14). This release changes one error message and nothing else.
What was wrong. On a free Apple ID that already holds development certificates made by other tools, Apple refuses to issue one more for iPASide with error 7460: "You already have a current iOS Development certificate or a pending certificate request." That sentence reads as if iPASide had made the existing certificate, so the person is left to guess.
What changed. The message now names the other certificates (for example iloader), says that iPASide never revokes a certificate it did not create (doing so stops every app that certificate signed from opening, in a tool iPASide has no part in), and says how to continue: open the Account page, revoke one of them, and try again. It also says what revoking costs: the apps that certificate signed stop opening until the tool that made it signs them again. Nothing is revoked automatically, as before.
Verified. 733 engine tests pass (7 of them new, for this message), and each of 11 deliberate breaks of the new logic was caught by a test. The installer was built clean and verified itself when installed.
Not verified. Against a real account at Apple's limit: I have none, so the message was tested against a fake developer portal that raises the same error text as in the report. Whether revoking one of the other certificates then lets the install through is up to the reporter to confirm. No app was sideloaded with this build.
The installer is unsigned, so SmartScreen will warn — the SHA-256 is in SHA256SUMS.txt.