Help for owners
My app broke after phones got a new Android version
Short answer
Each Android release changes how apps may behave, and some changes affect every app, whatever it targets. An app that was not updated can then show broken screens, lose a feature or crash. Note which Android version and phone are affected, tell whoever maintains the app, and have it tested and updated rather than waiting for a fix to appear.
Does this sound like your situation?
- Customers say the app stopped working after their phone updated Android.
- The screens look cut off, stretched or overlapped on the newest phones.
- A feature that ran in the background, such as syncing or reminders, stopped.
- The app works on older Android versions and fails on the newest one.
- A warning appears when the app opens saying it is not compatible or not optimised.
Why does this happen?
Android changes behaviour with every release
Google publishes lists of behaviour changes for each release. One list applies to all apps running on the new version regardless of the target level the developer chose, so an app that was never touched can still be affected.
Confirmed by developer.android.com
Background work gets stricter limits
The all-apps list describes changes to how the system schedules background jobs and the quota they get. Apps that rely on timed background tasks can behave differently.
Confirmed by developer.android.com
Old internals can stop working
Google states that libraries and app code that rely on internal structures of the Android Runtime might not work correctly on the new version, and that such changes can also reach earlier Android versions through system updates.
Confirmed by developer.android.com
Memory page size changed on some devices
Google describes a compatibility mode for apps built for 4 KB memory pages on devices configured for 16 KB, with a dialog shown to the user, and says apps should still be 16 KB aligned for best performance and stability.
Confirmed by developer.android.comTechnical detail: Google Play says the app does not support 16 KB memory pages
Raising the target changes more
A further set of changes applies only when the app is updated to target the new level, such as edge-to-edge screens, back navigation and ignoring orientation limits on large screens. They arrive when the app is brought up to date, so each needs testing.
Confirmed by developer.android.comTechnical detail: Play Console will not accept the release because of its target API level
What can I do about it today?
- Ask three affected users for detailsPhone make and model, Android version, app version and what they were doing. Screenshots help. Put the answers in one note.
- Check whether older phones are fineIf the app works on an older Android version and not on the new one, say so clearly. That points at the system update.
- Do not tell users to reinstall repeatedlyReinstalling can lose local data and rarely fixes a system-level change. Ask them to wait for your update instead.
- Look in the Play ConsoleAndroid vitals can break crashes down by Android version and device model, so open it and see whether one version stands out.
- Tell your customers a fix is comingA short, honest notice on your site or social page avoids a flood of bad reviews.
- Contact whoever maintains the app todayIf nobody does, that is the real problem. An app needs someone assigned to keep up with each Android release.
When should I bring someone in?
- A large share of customers on the newest Android version cannot use the app.
- You have no developer, or the one who built it no longer answers.
- The app takes payments or bookings and each hour of failure costs you business.
How do I handle it?
- Reproduce on the new Android versionI run the live build on a matching device or emulator and compare it with the previous version.
- Match the failure to the documented changeI check the failure against Google's lists of behaviour changes, so I fix the true cause.
- Update and testI update the affected parts, raise the target level where needed and test main journeys on several Android versions and screen sizes.
- Back up, then release in stagesCode and signing details are saved first. The update goes to a test track, then to production, with a tested rollback.
- Make it a routineI propose checking your app against each new Android version as part of ongoing care, so the next release is not a surprise.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is it Google's fault?
The change comes from Android, but the app has to be updated to match, as with every release. Google documents what changed so that developers can adapt.
Will the app fix itself?
No. A repair means a new version of the app, tested and released to the store.
Why does it work on some phones?
The change applies to the new Android version, and phone makers roll updates out at different times. Phones on older versions are unaffected.
Can customers do anything in the meantime?
Check that the app is up to date in the store. If the problem remains, wait for the fix instead of clearing the app's data, which can delete information stored on the phone.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Play Console warning that app updates must support 16 KB memory page sizesGoogle Play says the app does not support 16 KB memory pagesPlay Console blocks submitting a release whose app bundle targets an API level below 36Play Console will not accept the release because of its target API levelDependency 'androidx.core:core:1.x.x' requires libraries and applications that depend on it to compile against version 34 or later of the Android APIs.A library needs a higher compileSdk than your module sets