“Untrusted Enterprise Developer” on iPhone: Fix It Fast
You installed Scarlet, tapped its icon, and iOS answered with a grey screen: “Untrusted Enterprise Developer” — and a note that the developer has not been trusted on this iPhone. Nothing is broken, nothing is dangerous, and you have not done anything wrong. This message is iOS doing exactly what Apple designed it to do with enterprise-signed apps, and the fix takes under a minute once you know where the trust control lives. This guide walks the fix step by step, then covers the cases where the message keeps coming back — because those mean something different.
Why iOS Shows “Untrusted Enterprise Developer”
Apps from the App Store arrive pre-approved by Apple. Apps installed with an enterprise certificate — Scarlet’s method — arrive with a signer Apple has not vouched for in the consumer sense, so iOS refuses to run them until you explicitly vouch for the developer profile on your device. The “Untrusted Enterprise Developer” message is that checkpoint. It appears the first time you open any app signed by a certificate whose profile you have not yet trusted, and it is a one-time decision per certificate: trust the profile once, and every app signed by that certificate opens normally afterwards.
This is also why the message reliably appears right after two events: a fresh Scarlet install, and a certificate change — when Scarlet’s shared certificate gets revoked and replaced, the new certificate is a new “developer” as far as iOS is concerned, and it starts untrusted. The certificate behaviour behind that cycle is what our Scarlet certificate status hub exists to track.
The Fix: Trust the Developer Profile (Step by Step)
- Open Settings on your iPhone or iPad.
- Go to General → VPN & Device Management. (On older iOS versions this section is labelled Profiles & Device Management or Device Management.)
- Under the Enterprise App heading, tap the developer name shown — it will match the organisation name on the certificate Scarlet was installed with, which is often a company name you do not recognise. That is normal for shared certificates.
- Tap Trust “[developer name]”.
- Confirm by tapping Trust (on newer iOS versions, Allow & Restart or a verification prompt may appear — complete it).
- Go back and open Scarlet. It should launch normally now.
That is the entire fix for the standard case. Apple’s own support documentation describes this same flow for manually installed enterprise apps, because it is the intended, supported way to run them — you are not using a loophole, you are completing the install.
When the Error Keeps Coming Back
If you trust the profile and the message returns — or the trust option itself is missing — you are looking at a different problem wearing the same clothes:
| Symptom | What it really means | What to do |
|---|---|---|
| No developer profile listed under VPN & Device Management | The install did not complete, or the profile was removed | Reinstall Scarlet, then trust immediately after installing, before opening it |
| You tap Trust, but the app still shows the message or crashes instantly | The certificate has been revoked — iOS will not let a revoked developer stay trusted | There is no trust fix for a dead certificate. Reinstall Scarlet with a working certificate; if certificates keep dying, import your own — see our certificate import guide |
| The message returns every few days or weeks | Scarlet’s shared certificate is being rotated after revokes; each new certificate needs a fresh trust | Expected behaviour with shared certificates. Trust the new profile each time, or move to your own certificate for stability |
| “Unable to verify” appears after trusting | iOS could not reach Apple’s verification servers, or the certificate status check failed | Check your connection, disable VPN/DNS filters temporarily, and work through our unable to verify app guide |
| Trust button works, app opens, but closes immediately | Not a trust issue — the app itself is failing (revoked mid-session, corrupted install, or an iOS version conflict) | Reinstall the app; if it is Scarlet itself, check the fixes in the iOS 26 install steps in our Scarlet on iOS 26 guide |
Is It Safe to Trust an Enterprise Developer?
A fair question, because the warning is worded to make you pause. Trusting a profile means apps signed by that certificate can run on your device with the permissions iOS grants them. It does not give the developer access to your Apple ID, your other apps’ data, or your phone’s contents — iOS sandboxing still applies to enterprise apps exactly as it does to App Store apps. The realistic risk sits in which apps you install afterwards: a trusted certificate plus a maliciously modified IPA is a bad combination, while a trusted certificate plus apps from reputable repos is the normal sideloading arrangement millions of people use. Our overview of whether Scarlet is safe goes through that risk picture in full. The sensible rule: trust the profile you deliberately installed, and never trust a profile a random website or pop-up asks you to install out of nowhere.
A Note for Managed and School/Work iPhones
If your iPhone is managed by an employer or school (look for a management profile and “this device is managed” wording in Settings), your organisation controls which enterprise developers may be trusted, and the Trust option may be hidden or blocked entirely. That is policy, not a fault — and there is no legitimate way around an MDM restriction. Sideloading belongs on a device you personally control.
How This Differs From the “Integrity Could Not Be Verified” Error
These two messages are cousins and are constantly confused. The untrusted-developer message is a permission checkpoint: iOS knows what the app is, has not been told to trust its signer yet, and the fix is entirely in your hands in Settings. The integrity error is a verification failure: iOS tried to validate the app or its certificate and could not — because the certificate is revoked, the profile is mismatched, or the check itself failed. As a rule, if you have not yet trusted the profile, you will meet this message first; if you have trusted it and things still fail, you are in integrity territory and should switch guides. Diagnosing which of the two you are actually seeing is the whole game — the fixes share no steps.
FAQ
What does “Untrusted Enterprise Developer” mean?
It means the app you are opening was signed with an enterprise certificate whose developer profile you have not yet approved on this device. iOS blocks the app until you trust that profile in Settings → General → VPN & Device Management.
Why does the message appear again after I already trusted it?
Because the certificate changed. Trust is granted per certificate, not to Scarlet as an app — when Scarlet is reinstalled with a new certificate (usually after the old one was revoked), the new developer profile starts untrusted and you must approve it again.
There is no Trust button. What now?
Either the install did not finish (reinstall Scarlet and look for the profile immediately), the profile name differs from what you expect (check every entry under the Enterprise App heading), or the device is organisation-managed and trust is blocked by policy.
Is trusting an enterprise developer dangerous?
Trusting itself is a normal, Apple-supported step for running enterprise-signed apps, and sandboxing still limits what those apps can do. The real risk is installing untrustworthy apps afterwards — stick to reputable sources and never trust profiles that websites push on you unexpectedly.
Do I need to trust the developer for every app Scarlet installs?
No. You trust the certificate’s profile once, and all apps signed with that same certificate open without asking again. You only repeat the process when the certificate changes — for example after a revoke and reinstall, or when you import a different certificate of your own.
