Your iPhone shows as «ineligible» when you try to add it to a sideloading service, and nothing installs. Unlike the «processing» state, this is not a wait you sit through once — it is a temporary lock Apple places on a device after a certificate it was on gets revoked. The lock lasts 14 days, or in some cases 30. Here is what triggers it, how long it really lasts, and what you can and cannot do about it.
What «ineligible» means
«Ineligible» means Apple has temporarily blocked your device from being registered to a signing certificate. It is a flag on the device itself, set on Apple’s side — so it applies across every sideloading service at once, not just the one you were using. While the flag is active, no tool or store can add your device or sign apps to it.
What sets it off: a revoke
The ineligible state is the aftermath of a certificate revoke. When Apple revokes a developer certificate it believes was used for large-scale sideloading, the devices registered on that certificate are put on a cooldown before they can move to a new one. If you were sideloading through a service whose certificate got revoked, your device can land in ineligible even though you did nothing wrong.
How long: 14 days, sometimes 30
The cooldown is fixed and non-negotiable. In most cases it is 14 days. For devices caught in repeat revokes, or certificates Apple flags more harshly, it can stretch to 30 days. There is no way to shorten it — no setting, VPN, DNS trick, or paid tier removes an Apple-side device flag. It clears on its own when the period ends.
What to do while you wait
- Wait it out. Count 14 (or 30) days from when the revoke hit. When the flag clears, you can sideload again.
- Do not keep retrying. Re-adding the device during the cooldown does nothing — it resets your patience, not the timer.
- It is not your account. Ineligible is tied to the device and the revoked certificate, not to your Apple ID being banned.
- If your apps vanished but the device is not locked, that is a plain revoke — see why sideloaded apps get revoked.
How builds.io handles it
No service can lift Apple’s cooldown, but it should not cost you paid time. On builds.io, if a revoke puts your device in ineligible, the downtime is credited back as free time on your plan — so a wait you did not choose does not eat into what you paid for. The bigger win is avoiding revokes in the first place: builds.io uses managed signing built to be stable, not the grey-market shared certificates that trigger the revoke-and-cooldown cycle.
Short version: «ineligible» is a 14-day (sometimes 30-day) device cooldown after a certificate revoke. It hits every service at once, it cannot be sped up, and it clears on its own. Wait it out — and to stop it recurring, sideload through a service that does not get revoked.
