You updated an app, or updated the phone itself, and now the store or the app throws up a wall: your device is not supported. It stings because the thing worked fine a day ago, and nothing about your phone physically changed. Here is the reassuring part. That message is a compatibility gate, not a verdict that your phone is broken, and it almost always traces to one of a handful of concrete reasons. The new build may require a newer operating system than you run, it may have dropped the chip architecture your phone uses, your device may have failed a security or certification check, or the update may simply have not reached your model yet. This guide walks those causes in the order worth checking on Android 15 and 16 and on iOS 19, so within a few minutes you can tell whether the fix is yours to make, the developer’s, or a sign the phone has aged past this app.

First, What the Block Actually Means: “device not supported” is the store or the app refusing to run a build your phone does not meet the requirements for, and it comes in two flavors. Either your phone is missing something the new version needs, such as a newer OS, a 64-bit processor, or a passing integrity check, or the app is fine and the block is temporary because a staged rollout or a stale store cache is filtering you out for now. Start by ruling out the reversible causes, then work down the list of hard requirements. If your phone genuinely falls below a hard requirement, no setting fixes that, and the honest move is to keep the last compatible version or plan a device upgrade.

The message is a filter, not a diagnosis. When you tap install or open an updated app, the store compares a list of requirements the developer declared against a profile of your phone: its OS version, screen, chip architecture, required hardware features, and certification status. If any single item fails, you get blocked, even when the app would otherwise run. That is why the exact wording matters as your first clue. “This app isn’t compatible with your device anymore,” “This app isn’t available for your device because it was made for an older version of Android,” “Not compatible with this iPhone,” and “Your device isn’t supported” each point at a different cause. Read the phrase you actually got before you start changing settings, because it usually narrows the problem to one of the four causes below.

A surprising share of these blocks are soft, meaning they clear on their own with a nudge. On Android, open Google Play and make sure both the Play Store app and Google Play services are current, then clear the store cache under Settings, Apps, Google Play Store, Storage, Clear cache. Confirm you are signed into the Google account and region tied to the app, and restart the phone. A phantom incompatibility often disappears after that. If you recently moved to Android 16 and other things also feel off, unrelated post-update gremlins can pile on, and our guide to Android 16 battery drain fixes after updating covers those. On iOS, check Settings, General, Software Update for a pending point release, since an app can require the newest one, then confirm your Apple ID region, restart, and try offloading and reinstalling the app. If the block survives all of that, you are looking at a hard requirement, and the next four sections tell you which.

This is the most common reason by a wide margin. Developers raise the minimum OS their app supports, so the new version refuses to install on an older release. On Android you might see a straightforward “requires Android 14” style note, or the reverse case, “made for an older version of Android,” which means the app itself is too old for current store rules. Google Play enforces a target API level requirement that pushes developers to keep apps current, and outdated apps get hidden from devices that no longer match, as spelled out in the Play target API level policy. To check your side, compare your Android version under Settings, About phone against the app’s “About this app” section on its Play listing. On iOS, the App Store shows “Requires iOS 19.0 or later,” but you can usually still grab the last version that ran on your current iOS by tapping the download icon and accepting the older-version prompt. As one Android user put it after a failed install, most of the time the device simply does not support the required API level.

Apps ship separate native code for different chip architectures, and a mismatch there produces a hard block. If your phone is 32-bit only, on the older armeabi-v7a architecture, and the new build is 64-bit only, on arm64-v8a, it will not install. Experienced users on Android forums specifically advise matching the arm64-v8a build to your hardware rather than grabbing whatever downloads. The fresh 2026 wrinkle is memory page size. Android 15 added support for 16 KB memory pages, and since November 2025 Google Play requires new apps and updates that target Android 15 and later to support 16 KB pages on 64-bit devices, as described in Android’s 16 KB page size guide. Apps whose native libraries were not recompiled for 16 KB alignment can crash or get blocked on newer 16 KB-page phones, which is a developer fix, not yours. If your problem is an installation failure rather than a compatibility gate, the architecture and signature angle is worth a closer look, and our walkthrough of the Android “app not installed” error covers it step by step.

Some apps refuse to run on devices that fail a trust check, even when the hardware is perfectly capable. On Android this is Play Protect certification and the Play Integrity check. A device running a custom ROM, a rooted phone, one with a modified bootloader, or a gray-market handset that was never certified can be marked incompatible for many apps, with banking, streaming, and some games enforcing it hardest. Verify your status in the Play Store under your profile, Settings, About, Play Protect certification, and Google explains what that state means in its Play Protect certification help page. Occasionally an out-of-date Google Play services makes a genuinely certified device fail temporarily, which loops back to the 60-second checks. For the full integrity-specific walkthrough, including which cases are not fixable from the user side, see our guide to the Play Integrity “device not compatible” error. The iOS parallel is a jailbroken device or one failing attestation, which security-sensitive apps will block the same way.

Sometimes nothing is wrong with your phone and the block is purely a matter of timing. Developers roll updates out to a percentage of devices at a time, exclude specific models with known bugs through the Play Console device catalog, or limit availability by country. One player described a game that installed fine on a cheaper phone but showed “not compatible” on a more expensive one, which is the signature of a model allowlist or regional gate rather than a real capability gap. The move here is patience: wait 24 to 72 hours and check whether the app appears, confirm your account region matches where the app is offered, and only consider the developer’s own download if you trust the source and it matches your architecture. This category is temporary and out of your hands, so resist the urge to reset or sideload while a rollout is still in progress.

When the message appears, this quick reference points you at the likely cause and who owns the fix, so you are not guessing.

iOS tends to handle this more gracefully than Android. When an app’s newest version needs iOS 19 and you are on iOS 17 or 18, the App Store will usually offer the last version that ran on your iOS: tap the download cloud, and confirm the prompt to install the older compatible build. Apple documents the broader download and update troubleshooting flow in its support article on what to do when you can’t download or update apps. Two iOS-specific gates cause the block. The first is the minimum iOS version, which you can often work around with the older build. The second is a hardware feature requirement, where an app that depends on newer chips or on Apple Intelligence features drops older iPhones even if those phones can technically run iOS 19. If a feature tied to Apple Intelligence is missing rather than an app itself, that is usually hardware gating by model, and our note on Apple Intelligence not showing on your iPhone explains which models qualify. Beyond that, confirm your Apple ID region, restart, and offload and reinstall to clear a corrupted install.

The cleanest test is a cross-check. Does the same app install on a friend’s newer phone or a spare device? Look at the developer’s changelog or support notes for a line about dropping support for a given Android or iOS version, since responsible developers announce it. Search the app’s community for the version number you need. If you are shopping and worried a new phone or laptop will not run a must-have app, checking compatibility before you buy beats returning it later, and while our guide on the Snapdragon Copilot+ PC app compatibility check is written for laptops, the same before-you-buy habit applies to phones. When several hard requirements point the same direction, an OS that cannot update, a 32-bit chip, an uncertified state, the phone has genuinely aged out of this app. Your best options then are to keep the last compatible version installed, since you may not get it back once removed, use a web version if the service offers one, or plan an upgrade. If you do upgrade and move your line, our checklist for upgrading Android with eSIM and RCS covers the transfer steps worth doing first. Whatever you do, avoid random third-party APK mirrors for banking or payment apps, because the security risk outweighs the convenience.

The new version raised a requirement your phone does not meet, most often a newer OS, a 64-bit-only build, or 16 KB page-size support on Android 15 and 16. The older phone gets filtered out even though it ran the previous version fine.

It depends on the cause. Updating your OS, updating Play services, clearing the store cache, and fixing certification are on you. A too-old target level or missing 16 KB support is the developer’s to fix, and there is no setting on your end that changes it.

Only from a source you trust, and only after matching your architecture and OS version. For banking, payment, or work apps, do not, because installing a modified build off an unofficial mirror is a common way to pick up malware or fail an integrity check.

The latest version now requires a newer iOS or newer hardware. Tap the download icon in the App Store to grab the last version that ran on your iOS, or update iOS if an update is available for your model.

Rarely. A reset can clear a corrupted install or bad cache, but it will not add a newer OS, change your chip, or certify an uncertified device, so it does nothing for hard-requirement blocks. Try the reversible checks first.

• Read the exact wording of the block first, because it usually names the cause.
• Do the reversible checks: update the store and Play services, clear the store cache, confirm account and region, restart.
• Compare your OS version against the app’s required version, and update the OS if you can.
• Confirm your phone is 64-bit, and on Android 15 or 16, whether the app supports 16 KB page sizes.
• Verify Play Protect certification on Android, or that an iPhone is not jailbroken, before assuming a hardware limit.
• If everything checks out, assume a staged or regional rollout and wait 24 to 72 hours.
• When several hard requirements fail together, keep the last compatible version and plan an upgrade instead of sideloading risky APKs.

Almost every “device not supported” message is a mismatch between what the new build asks for and what your phone reports, and the right fix follows directly from which requirement failed. The reversible causes clear in minutes, and the hard requirements tell you honestly whether to wait on the developer or move to a newer device. Read the message, work down the list in order, and you will rarely be left guessing about whether the problem is the app, the store, or the phone in your hand.