Unable to Verify App on iPhone — How to Tell What Broke

The app worked yesterday. Today it bounces off the home screen, and Settings says Not Verified. You tap Verify, and nothing completes.

The frustrating part is that this exact screen appears for at least four unrelated failures, and the fixes have nothing in common. People burn evenings trying random certificates when their problem was never the certificate. So before you try anything, work out which one you have — it takes about a minute.

First, answer two questions

How was the app signed? A free Apple ID (through AltStore, SideStore, Sideloadly with your own account) behaves completely differently from an enterprise certificate (ESign, KSign, Feather, a cert bought in a Telegram channel).

Did one app break, or all of them at once? One app is a problem with that install. All of them together is a problem with the thing that signed them.

Those two answers narrow it to one of four.

1. Free account, and it lasted about a week

Signs: signed with your own Apple ID, worked roughly seven days, all apps from that account died together.

Nothing broke — this is the design. A free Apple developer account signs apps for seven days, then the signature expires. Re-signing resets the clock, which is why the advice everywhere is “just refresh it.”

Fix: re-sign it. And accept it will happen again next week, because it will. We compared every way to get off that treadmill in how to stop refreshing sideloaded apps every 7 days.

2. Free account, and it lasted about a day

Signs: same free-account setup, but the app died in roughly 24 hours instead of seven days, and tapping Verify in Settings never finishes. Reported repeatedly on iOS 26.6, with both Sideloadly and SideStore, across unrelated IPAs.

This one is not expiry — the maths does not work. It behaves like the online verification step failing: when you first open a free-signed app, iOS checks the signing identity with Apple, and if that check cannot complete, the app is treated as unverified regardless of how much time is left.

What to check, in this order:

Any VPN or custom DNS off. Anti-revoke DNS setups are the single most common cause of a verification that hangs forever — they are specifically designed to block Apple’s checks, and they cannot tell your check from a revoke.
ppq.apple.com opens in Safari. That is the endpoint the check uses. If it does not load, nothing else you do matters.
Date and time set to automatic. A wrong clock invalidates the signature check.
Signed in to the Apple ID that signed the app, in Settings → General → VPN & Device Management.

If all four are clean and it still dies daily, you are looking at a platform-side problem, not something you misconfigured. Apple has not acknowledged an iOS 26.6 verification bug, so treat that as a known-unknown rather than a diagnosis — but do stop buying certificates to fix it, because a certificate is not what is failing.

3. Enterprise certificate, everything died at once

Signs: apps signed with a bought or shared certificate, all of them dead simultaneously, and — the giveaway — the same certificate still works on someone else’s phone.

That is a revoke. Apple disabled the enterprise certificate centrally; devices find out at their next check-in, which is why phones die at different moments and one friend is still playing while yours is bricked. Time left on the certificate is irrelevant — a certificate with sixty days remaining dies the same second as one with two.

Fix: there isn’t one on your side. A new certificate from the same reseller pool tends to get revoked in the same wave. The mechanics, and why chasing fresh certs is a losing game, are in why sideloaded apps get revoked on iPhone.

4. It broke right after a restart or an iOS update

Signs: everything worked, you rebooted or updated, now every sideloaded app shows the error at once — including ones signed by different certificates.

A restart forces iOS to re-validate every installed provisioning profile in one go. Anything that was already invalid but still running in memory surfaces at that moment. So the reboot did not break it; the reboot is when you found out.

Fix: work out what the underlying state actually was — free account past seven days is case 1, enterprise cert is case 3. The reboot is a symptom, never the cause.

Why the message is so unhelpful

iOS says “Unable to Verify App” for an expired signature, a revoked certificate, a blocked network check and a broken profile alike. It never tells you which. That single design choice is responsible for most of the wasted hours in this hobby: the error looks like a certificate problem, so people go buy another certificate, and half the time the certificate was fine.

The version where this stops happening

Every case above traces back to the same root: you are responsible for the signing, and the signing is fragile. Free certificates expire weekly. Enterprise certificates get revoked in waves. Both need Apple’s check to succeed on a network you do not control.

On builds.io the signing is not yours to maintain. Installs stay signed, and when a certificate goes down on our side it is our problem to solve rather than a message on your home screen. No jailbreak and no computer — you add a device once, Apple’s one-time processing step runs (usually within a day, sometimes up to three), and after that apps install in one tap.

That does not make Apple’s error message any clearer. It just stops you having to decode it.