Test your app update: install the old version first
· 7 min read
Most beta tests install your newest build on a clean phone. That is a fresh install, and it hides a whole class of bugs. The people who already have version 1 never get a fresh install. They get an update, with their old database, their old settings and their old login still on the phone. I read the vendor pages below in November 2026, and I quote them as they are written. Where a page says nothing, I say so.
Update bugs are things like a database change that wipes data, a renamed storage key, a changed login token, or a new permission nobody asked for. You will not see any of them if you only test fresh installs.
Short answer: install the old version first, sign in, make some real data, then update to the new build without uninstalling. Check that the data, the login and the settings survived. Then do a fresh install as well.
Android: version codes and signing
Google's Version your app page says versionCode helps "determine whether one version is more recent than another, with higher numbers indicating more recent versions". It also says the system protects against downgrades "by preventing users from installing an APK with a lower versionCode than the version currently installed on their device". And Play will not take a build "with a versionCode you have already used for a previous version". So every build you upload needs a higher number than the last one.
The second thing is the signing key. The app signing page says "When the system is installing an update to an app, it compares the certificate(s) in the new version with those in the existing version. The system allows the update if the certificates match." So an update build signed with a different key will not install over the old one. That matters for test builds, as I explain below.
Does an update keep the app's data? Android itself does: the adb page describes the package manager's -r install option as "Reinstall an existing app, keeping its data". What breaks data is usually your own new code meeting the old data, which is exactly what the test plan below checks on a real phone.
Testing the update path with Google Play
Google's page on open, closed and internal tests says devices get the version that "Contains the highest version code compatible with the device". It also says that after a test ends "the app will remain installed on their device". It does not say anything about data surviving an update. For the three tracks themselves, see internal, closed and open testing.
Internal app sharing is quick, but note this line: "They're automatically re-signed with an Internal App Sharing key." So keep both versions on the same route. Google's guide to testing in-app updates does exactly that: the old version on the test device must have been "installed using an internal app sharing URL", and the new upload needs "a version code that is higher than the one you already have installed on the test device." If an update will not install, a different signing key is the first thing I would check.
On your own phone you can skip the store. Install the old APK, use it, then install the new APK over it. The adb page's package manager table lists install with -r: "Reinstall an existing app, keeping its data." That is the update path in one command: adb shell pm install -r with the path of the new APK on the phone (copy it there first with adb push). Both APKs need the same signing key.
If your app uses Room
The Room migration page says "Migrations are often complex, and an incorrectly defined migration can cause your app to crash." It points to the MigrationTestHelper class for tests, and says you "must first export your database's schema". It also warns that if Room finds no migration path, an IllegalStateException occurs. With fallbackToDestructiveMigration, Room "permanently deletes all data".
iOS: build numbers and TestFlight
Apple's CFBundleVersion page calls it "The version of the build that identifies an iteration of the bundle" and says it is "one to three period-separated integers". It says to increment it for macOS apps. I did not find an iOS sentence on that page, so I treat it as a habit: a new number for every upload. App Store Connect's upload builds page says "The build string is used to uniquely identify the build throughout the system."
What happens when a TestFlight build is installed over an App Store version? I checked Apple's TestFlight overview. It says "You can test a build for up to 90 days", but it does not say whether data is kept when a build replaces an installed one. So I will not guess. Try it yourself on a spare iPhone with the old version installed. For TestFlight links, see TestFlight external testers and the public link.
If you use Core Data, Apple's page on migrating your data model automatically says "Core Data can typically perform an automatic data migration, referred to as lightweight migration." Typically is not always.
Expo and React Native: over the air updates
Expo's EAS Update introduction says an app can update "its own non-native pieces (such as JS, styling, and images) over-the-air". Its table marks "Change to native code or native dependencies" as not suitable for that.
The runtime versions page explains why: "Runtime versions are a property that guarantees compatibility between a build's native code and an update." It adds that "any time native code is updated, we're required to make a new build before publishing an update." So test with an old build installed.
Forced updates: test the "please update" screen too
Google's in-app updates page describes two flows. "Flexible updates provide background download and installation with graceful state monitoring." And "Immediate updates are fullscreen UX flows that require the user to update and restart the app in order to continue using it." If you use either, test it. The testing guide says to "Upload a version of your app that uses a version code that is higher than the one you already have installed on the test device." It also says the test app must have "the same application ID and signing key as the version available from Google Play", and that "Google Play can only update an app to a higher version code."
A test plan a tester can follow
This is the plan I would paste into a test task:
- Install the current store or production version of the app. Do not install the new build yet.
- Sign in with the test login.
- Create real data: add two or three items, change a setting, turn notifications on, and finish any onboarding.
- Update to the new build. Do not uninstall the old one first.
- Open the app. Note whether it crashes or shows a blank screen on the first open.
- Check that you are still signed in, that your items are still there, that your settings are kept and that notifications are still on.
- Then delete the app, install the new build fresh, and run through sign up again.
- Tell me the phone, the OS version, the old version number and the new one.
For how to word a task like this, see how to write a test task. If something does crash on first open, a crash report helps a lot: crash reports before launch.
Where TestSwap fits
TestSwap is a free app testing exchange. Makers post web, iOS and Android apps with a link testers can open or install, like a TestFlight link or a Google Play testing link. A test login can be added that only signed-in testers see, so use a throwaway account. Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1. The maker can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.
Testers on other phones can try the update path for you if your task asks for it. The one thing to spell out is the order: install your current store version first, use it for a few minutes, and only then open your test link. Put that in step one of the task, or testers will do a fresh install out of habit. TestSwap is not affiliated with Apple or Google.
The update checklist
- Is the new Android
versionCodehigher than the one in production? - Is the update signed with the same key as the installed app?
- Did you test with the old version installed and real data in it?
- Does the user stay signed in after the update?
- Is there any crash or blank screen on the first open?
- If you use Room or Core Data, did you test the migration with old data?
- On Expo, does an old build match the runtime version of the update?
- If you ask people to update, did you test that screen?
- Did you also test a fresh install?
Pick one old version, one phone and ten minutes. Then post your task on TestSwap, and review someone else's app first to see how it feels. Tell me what's missing or broken (@dizid on X).