ADT app not working on iPhone? Check which app you have

If your ADT app is not working on iPhone, the first fix is not reinstalling it. It is naming the app. ADT+, ADT Control, and ADT Pulse are not three skins over the same service; they sit on different platform paths. CE Pro’s history of ADT’s app stack traces Pulse to the older iControl platform, Control to the Command/Alarm.com path, and ADT+ to ADT’s newer app platform direction.[1]

That distinction decides whether a normal iPhone cleanup can help, whether the account has to be provisioned correctly by ADT, or whether the app is simply the wrong front door for the system you own. A symptom-matched answer — “stuck on logo,” “won’t log in,” “system offline,” “notifications stopped” — is only useful after the app is identified.

First, separate the three ADT iPhone apps

Use this as the quick sort. The App Store details below were checked on 2026-08-25, so treat the version numbers as a point-in-time diagnostic aid, not as permanent facts.

ADT’s own migration language matters here. ADT Help says ADT+ replaces previous ADT apps, and that Pulse and Control are not compatible with the new ADT smart home security system and ADT Self-Setup system.[5] ADT’s newsroom also describes ADT+ as a new app meant to create a more seamless ADT user experience.[6] That does not mean every existing ADT customer should delete Pulse or Control and install ADT+. It means the right app depends on the system and account path ADT has you on.

The 30-second identification check

Before touching permissions, Wi-Fi, passwords, or the panel, do this on the iPhone:

1. Look at the exact app name under the icon or in iPhone Settings. “ADT,” “ADT+,” “ADT Control,” and “ADT Pulse” should not be treated as interchangeable names.
2. Open the App Store listing from the installed app, not from a random web result. Confirm whether the listing says ADT+, ADT Control, or ADT Pulse.
3. Check the iOS requirement. As verified on 2026-08-25, ADT+ and ADT Control require iOS 17.0 or later, while ADT Pulse requires iOS 13.0 or later.[2][3][4]
4. Match the app to the system generation. New ADT smart home security and Self-Setup customers should expect the ADT+ path; Command/Control customers should expect ADT Control; older Pulse customers should expect ADT Pulse.[1][5]
5. If you recently upgraded equipment, changed monitoring plans, or had ADT replace a panel, treat the app identity as unsettled until ADT confirms which app your account is provisioned to use.

The last step is the one people skip. A phone can have the newest iOS version, a clean app install, good Wi-Fi, and still fail if the account is pointing at the wrong backend. If you are also unsure what hardware generation you have, panel age and communicator history can matter; that is a separate hardware question from ordinary iPhone app troubleshooting, especially on older monitored panels and cellular communicators. For background, see this guide to the 2G shutdown impact on smart-home devices.

Now choose the right failure branch

Once you know which app you have, the ordinary iPhone steps are allowed back into the room. They are just not allowed to lead.

For a plain local app problem, the short version is enough: update the right app, restart the app, restart the iPhone if the app is frozen across launches, confirm the iOS minimum, and reinstall only after you know the app is the correct one. Reinstalling the wrong ADT app just gives you a cleaner copy of the wrong door.

When reinstalling is not the fix

The cleanest example is the boring one: app access not enabled correctly on ADT’s side. One ADT Control App Store reviewer described an upgrade case where the app only showed the logo; after about a week of support, the reported fix was ADT enabling remote/app access on the backend, not another iPhone reinstall.[3]

That is one review, not a frequency study. It should not be inflated into “this is always the cause.” But it is a useful diagnostic pattern because it explains a failure that generic iPhone advice cannot: the phone can successfully install and launch the app shell while the account still lacks the backend permission needed to show the security system.

This branch becomes more likely after a system upgrade, panel replacement, service transfer, or move from an older ADT app path to ADT+. It is also where the replacement language around ADT+ matters: if your new system is not compatible with Pulse or Control, an old login ritual can keep failing even though the iPhone itself is fine.[5]

Use outage reports as caution lights, not diagnoses

If many ADT users are complaining at the same time, it can be sensible to pause before resetting a working panel. Downdetector’s ADT page has shown Server Connection as the most-reported problem type, including app-login complaints during an Aug 13, 2026 wave.[7] That kind of signal can save you from tearing apart your own setup during a broader service problem.

It is still only a signal. Downdetector is self-reported and point-in-time; it does not prove that your account, panel, Wi-Fi, or iPhone is affected. Reddit-style reports are similar. A Reddit thread described an ADT system that appeared offline in the app while the system itself was not actually down, which matches a real troubleshooting category, but it is still an individual report rather than a verified general rule.[8]

ADT Help has a specific support path for Command/Control systems that appear offline, and that is the better branch than repeatedly deleting the app when the panel continues to function.[9] The useful question is no longer “why is my iPhone broken?” It is “is the app status, the local network, the panel connection, or ADT’s server path the part that is failing?”

A practical status label for your next move

Use three labels while you work. They keep the fix from drifting.

One source caution: some ADT Help pages are JavaScript-rendered, and snippets for items such as notification/location permission paths, “Status Unavailable” wording, and log-out/log-back-in guidance can be easier to see in search results than on the live page. Before treating those instructions as current support policy, recheck the live ADT Help page for your app and system.

When to stop troubleshooting on the iPhone

Stop working on the iPhone and contact ADT when any of these are true:

• The app stopped working immediately after an ADT system upgrade, panel swap, account transfer, or migration to a new app.
• ADT+ opens, but you previously used Pulse or Control and are not sure ADT has moved your account to the ADT+ path.
• ADT Control or Pulse still installs, but your newer system is supposed to use ADT+.
• The app says the system is offline, but the panel appears armed, disarmed, or otherwise functional.
• Reinstalling returns you to the same logo, blank screen, or account-not-available behavior.

For Command/Control offline issues, ADT points customers through its offline troubleshooting path and support contact options, including 1-800-238-2727.[9] If the branch looks network-layer rather than account-layer, ADT also offers the ADT Wifi Fix diagnostic app on the App Store.[10]

At that point, the useful support request is specific: “I have ADT Control on iPhone, iOS meets the app requirement, the app is stuck after a system upgrade, and I need remote/app access checked on the backend.” Or: “I have ADT+, this is a Self-Setup system, and the app reports offline while the panel/network status needs to be checked.” That is much harder to misroute than “my ADT app is not working.”

References

1. The Evolution of ADT Control, CE Pro.
2. ADT+, Apple App Store.
3. ADT Control, Apple App Store.
4. ADT Pulse, Apple App Store.
5. What You Need to Know about the ADT+ App and Web Portal, ADT Help.
6. New ADT+ app creates seamless user experience, ADT Newsroom.
7. ADT status, Downdetector.
8. System says offline but it's not, Reddit r/adt.
9. My ADT Command/Control system appears offline. What should I do?, ADT Help.
10. ADT Wifi Fix, Apple App Store.