Current Scarlet Status
Certificate status can change without warning because Apple can revoke the enterprise certificates Scarlet relies on. We check and update this page when install methods change. For the very latest status, also check the official Scarlet website.
Status last checked: 22 October 2026 — all fix guides on this page re-verified.
Why Scarlet Stops Working
Scarlet is installed through enterprise certificates rather than the App Store. When Apple revokes one of those certificates, every app signed with it stops opening until a new certificate is used. Other common causes are an expired profile, a recent iOS update, or an incomplete install. Scarlet also uses a profile that you have to trust in Settings before the app will open; if a profile will not verify on your device, Apple Support has guidance on profiles and device management.
Symptoms: How to Tell It’s a Certificate Problem
- The app icon is greyed out, or the app closes instantly when you try to open it
- You see an “Unable to Verify App” message
- You see an “App integrity could not be verified” message
- Scarlet itself will not open, even though it was working fine before
Fixes to Try (In Order)
- Work through the full fix guide — Scarlet iOS Is Not Working
- Fix the verification error — Scarlet Is Unable to Verify Apps
- Fix the “app integrity could not be verified” error — How to Fix “App Integrity Could Not Be Verified” on iPhone
- Reinstall using the custom certificate method — Install Scarlet Using the Custom Certificate
- Update Scarlet to the latest version — How to Update the Scarlet iOS App
- Try the DNS AntiCert sideload method — Sideload iOS Apps with DNS AntiCert
- Full install from scratch — How to Install Scarlet iOS on iPhone or iPad
If Nothing Works
If the certificate is revoked, there is no user-side fix until a new one is available. In the meantime, these alternatives work in much the same way — see Best Scarlet iOS Alternatives.
The Fix Pathway, In Short
Short on time? This is the whole recovery route in five steps, in the order that solves the problem fastest. Each step links to the full guide if you need the detail.
- Check the current status first. Most Scarlet outages are certificate events, not faults on your phone, so start on this certificate status and fixes page to see whether a revoke is in progress before you change anything on your device.
- Trust and verify the developer profile. If the certificate is fine but apps still will not open, re-trust the profile under Settings → General → VPN & Device Management, and work through our guide to fixing “unable to verify app” errors.
- Fix integrity errors. If iOS says the app’s integrity could not be verified, the signature on the app itself has failed, and trust settings will not cure it. Follow the dedicated guide to fixing “app integrity could not be verified” — a clean reinstall or a fresh download usually solves it.
- Set up anti-revoke protection. Once everything works again, protect it before the next revoke wave: our Scarlet anti-revoke guide explains the DNS method and why signing with your own certificate is the only lasting defence.
- If nothing works, use an alternative. When a certificate is dead, no setting on your phone brings it back. The best Scarlet alternatives keep you sideloading until a fresh certificate appears.
Work through the steps in order and stop as soon as your apps open again — most people never need to go past step two. If you do reach step five, the status section at the top of this page will tell you when the situation changes.
FAQ
Does Scarlet not working mean my iPhone is broken?
No. It is almost always the certificate, not your device.
Will reinstalling Scarlet delete my apps’ data?
Apps signed with a revoked certificate stop opening. Reinstalling with a fresh certificate usually restores access, but data inside sideloaded apps is not guaranteed, so back up anything important first.
How often does Scarlet get revoked?
It varies and cannot be predicted. That is exactly why status pages like this one exist, so bookmark this page and check back.
Why does Scarlet stop working overnight?
Because the change happens on Apple’s side, not on your phone. When Apple revokes the enterprise certificate Scarlet is signed with, iOS finds out during its regular online status checks — often while the phone sits idle overnight — and every app signed with that certificate stops opening at once. Nothing on your device changed, which is why it feels so sudden. There is no setting that reverses a revocation; the fix is to reinstall under a certificate that is still valid, which is what the guides on this page walk through.
How do I know if it is a certificate problem?
The signs are consistent: apps that worked yesterday close instantly or sit greyed out, Scarlet itself will not open, or you see messages such as “Unable to Verify App” or “App integrity could not be verified”. If several sideloaded apps fail at the same time, it is almost certainly the shared certificate rather than any single app. App Store apps still working normally is another clue — they do not depend on the certificate, so they are unaffected. The symptoms list near the top of this page covers the full set.
Will reinstalling fix it?
Only if what you reinstall under is valid. Reinstalling Scarlet with the same revoked certificate changes nothing — the new copy fails for exactly the same reason. Reinstalling once a fresh certificate is available, or signing with your own certificate through the custom certificate method linked above, does fix it, and it is usually the fastest route back. Bear in mind that reinstalling can lose data stored inside sideloaded apps, so back up anything important first, and try the less drastic fixes in the list above before you delete anything.
What does ‘integrity could not be verified’ mean?
It means iOS checked the app’s code signature and the signature did not validate. Every app carries cryptographic proof of who signed it and that its contents have not changed since signing; if the certificate behind that proof is revoked, or the IPA file was corrupted or modified after signing, the check fails and iOS refuses to run the app. It is a different problem from “Unable to Verify App”, which is about the online trust check. Our step-by-step guide to fixing “app integrity could not be verified” covers the causes and the fixes in order.
How can I stop this happening again?
You cannot make a shared certificate revoke-proof, but you can make revokes matter far less. The strongest setup is signing Scarlet and the apps you depend on with your own certificate, because a private certificate is not caught in the public revoke waves. The DNS method in our anti-revoke guide can also shield apps that are still working, as long as it is in place before a revoke lands. Beyond that, keep Scarlet updated, back up important app data regularly, and check this status page first whenever something stops working.
