Help for owners
My app breaks on the new Android beta or preview
Short answer
If your app breaks on a pre-release Android version, a behaviour change in the new release is the likely cause. Google publishes lists of behaviour changes for all apps and for apps targeting the new version, and recommends testing on an emulator or device image. Find the failing screen first.
Does this sound like your situation?
- Customers or testers on a pre-release Android say the app crashes or looks wrong.
- A feature that worked on every older phone fails on the new version.
- I read that a new Android version is coming and have heard nothing from my developer.
- I need to know whether the public release will break my app.
- The problem appears only on one phone brand running the beta.
Why does this happen?
Android changes some behaviours for every app
Google publishes 'behavior changes that affect all apps' for each release. Those apply as soon as the app runs on that version, whatever the app targets.
Confirmed by developer.android.com
More changes apply once the app targets the new version
Google lists a separate set of changes that affect only apps that target the new version, so your app meets them when it is updated, not when the phone is.
Confirmed by developer.android.com
A bug in the beta image
Google's page on getting the beta says system images can be used to discover and report OS and framework issues, so some failures are the system's.
Confirmed by developer.android.com
Nobody tested before the release
Google offers the emulator, supported Pixel phones, partner devices and generic system images for testing ahead of launch.
Confirmed by developer.android.com
What can I do about it today?
- Find out which version and phoneAsk the user for the Android version and phone model. If the beta is a partner phone, Google says each partner has its own channel for reporting device-specific bugs.
- Do not tell customers to install the betaPre-release builds can lose data. Google recommends backing up before installing.
- Pause any rushed updateDo not push a fix to the store until the failing screen is known.
- Keep the evidenceSave the screen, steps and crash text for the developer.
- Check your Play ConsoleAsk whoever holds it whether crash reports show a rise on the new version.
When should I bring someone in?
- The app crashes on launch.
- The problem also appears on the public Android release.
- Nobody on your side can run the emulator or a test phone.
How do I handle it?
- Install the pre-release on a test setupI use the emulator and, where possible, a supported physical device, and compare with the last stable Android.
- Read the behaviour-change lists against the appEach documented change is checked against what your app does: notifications, background work, permissions.
- Fix and retest on both versionsThe fix has to work on the beta and on older Android.
- Release carefullyUpdates go through a staged rollout so a problem reaches few users first.
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?
Does the beta decide what my customers see?
Only customers who installed it. Most users get the public release, so this is early warning.
Should I raise the target version now?
That depends on Google's deadlines and your testing. See the Play target level fix page.
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.