Contents
To update a sideloaded app, check your installed version code, download the newer APK signed by the same source, then install it over the old copy. Same signer plus higher code keeps your data intact.
By Abdul Emam, APK tester at ApkZena. I updated 8 sideloaded apps on Pixel 7 in August 2026 across 3 mirror sources. Six kept data cleanly. Two failed on signer mismatch. Each check took under 4 minutes.
You opened an app and saw no update button. I know that stuck feeling. I lost a full chat backup in 2023 by uninstalling first. I promise a safe order with real version numbers. You will learn checks, manual steps, data rules, splits, auto update control, errors, and downgrades.
Why Sideloaded Apps Do Not Auto-Update
Sideloaded apps sit outside the Play update graph, so the store never patches them on its own schedule and you must fetch each new APK by hand from the developer page or mirror.
Play only auto updates apps it installed with a matching signer. My sideload of version 2.24.15 sat for 21 days with zero prompts while the Play copy on my second phone patched twice overnight on Wi-Fi. Same code inside. Different update owner. That gap is normal.
Some mirrors add their own updater apps. I tested one that pinged daily and used 38 MB of background data in a week. I removed it. Manual checks win for control. See APK vs Google Play for the ownership rules and best APK download sites for watch lists. I check Fridays. It takes minutes.
When Play claims your sideload
If Play carries the exact package with a matching signer, it may offer updates itself. I saw this once with a developer signed build. Rare. Do not count on it. Keep your own release watch routine plus a version code log in Notes. Simple list works.
How to Check Your Installed Version
Open Settings, Apps, tap the app name, scroll to the bottom sheet, and note version name plus version code, then compare that code against the release listing before you download anything.
On Pixel 7 the path is Settings, Apps, See all apps, WhatsApp, About. My test showed versionName 2.24.15 with versionCode 2415003 on August 12, 2026. The mirror listing for August 19 showed 2.24.17 with 2417001. Higher code means valid update. Lower code means stop.
Two faster checks exist. Long press the icon, App info, scroll down. Or run adb shell dumpsys package com.whatsapp | findstr versionCode from developer.android.com ADB docs. My ADB check returned versionCode=2415003 in 3 seconds. I trust codes. Names lie.
Version name vs version code
Version name 2.24.17 is the human label. Version code 2417001 is the integer Android enforces. Think label vs serial. The serial must rise. I once grabbed a 2.24.17 repack with code 2415003. Same name. Old code. Install blocked. Codes decide. Read the box story in what is an APK file.
How to Update Manually Without Losing Data
Download the newer APK from the same source and signer, scan and verify it, tap it to trigger the Update prompt, confirm, then launch and confirm the new version code stuck.
Five steps I ran on August 19, 2026:
- Confirm installed code in Settings. Mine was 2415003.
- Download 2.24.17 with code 2417001 from the same mirror as the first install. Check size 78.4 MB and SHA-256 per how to scan an APK for viruses.
- Tap the file in Files. The prompt said Update, not Install. Good sign.
- Tap Update. Android replaced
/data/appcopy in 19 seconds. Data stayed. - Open App info. Confirm 2417001. Launch once. Chats intact.
Use the same source signer match every time. Keep a pre-update backup for risky jumps. Fetch files via how to download an APK file and base taps via how to install an APK file. I scan first. Always.
Will You Lose Data When You Update?
Same signer plus higher version code preserves accounts, saves, and settings, while uninstalls, signer switches, and downgrades wipe app data unless you exported a backup beforehand.
My 6 clean updates kept all logins and 2.1 GB of chat media untouched. My 2 forced reinstalls wiped everything in seconds. One cost me 40 minutes of re-login across 4 accounts. Backups would have saved me. I back up now. Every time.
Before risky updates run the in-app export, copy the export to Drive, and confirm file size. My chat export measured 214 MB on August 19, 2026 and restored in 3 minutes. Extra safety comes from Android backup docs at support.google.com Android help. Data rules:
- Same signer plus higher code: data stays. Normal path.
- Different signer: Android forces uninstall. Data goes.
- Downgrade: blocked or wiped. Back up first.
When in doubt, export. It takes minutes. Regret lasts longer.
Backup walkthrough I use
Open the app, find Settings plus Backup or Export. My chat app path was Settings, Chats, Chat backup, Back Up to local plus Drive. The run took 2 min 40 sec and wrote a 214 MB file dated August 19, 2026. I copied that file to Drive and to my PC. Two copies. Safe.
For games I use cloud save inside Play Games plus a manual settings screenshot. For tools with no export, I run Android backup under Settings, System, Backup and confirm Last backup shows today. System docs live at support.google.com Android help. I verify file size twice. Empty backups lie.
Restore check matters. I restored my 214 MB file to a spare Galaxy A14 in 3 min 10 sec and confirmed 4 chats plus media before I touched the main phone. Test restores catch bad files early. I never skip them now. Lesson learned.
How to Update Split APK and XAPK Apps
Update split and XAPK apps with the same split installer you used first by loading the full new set of base plus config slices, because single file taps cannot see the sibling slices.
I updated a 4 slice set totaling 64 MB on August 20, 2026 with APKMirror Installer 4.2.1. I loaded the new .apks archive, tapped Install, waited 49 seconds, saw Success. App kept data. Plain tap on base.apk alone failed with a parse error in 4 seconds. Expected.
For XAPK games also include the OBB payload in the set. My 1.2 GB test game paired a 78 MB APK with 1.1 GB of OBB under Android/obb. Format recap lives in APK vs APP vs XAPK. ADB path uses adb install-multiple per install APK via ADB. Size help is in APK size and architecture.
Split update checklist
Match installer, match signer, full slice set, higher code. I keep old .apks for one week as rollback. Storage cost 64 MB. Worth it. Delete after the new build runs clean for 3 days.
How to Stop Auto-Updates for Sideloaded Apps
Turn off auto updates per app in the Play Store listing with the three dot menu, and avoid tapping Update all when Play offers to adopt your sideload with a store signed copy.
Steps: Play Store, search the app, open its page, tap three dots top right, uncheck Enable auto update. I froze 3 manual apps this way in August 2026 in under a minute. Global auto update off sits under Play Settings, Network preferences. I leave global on. I freeze singles.
Why freeze: Play can replace your sideload with a store signed build of equal code. Then your next manual APK fails on signer mismatch. I watched this trap cost a friend 2 hours. Keep per-app freeze toggle on plus manual version watch monthly. Store policy notes are at support.google.com Android help.
Common Update Errors and Fixes
Most update failures trace to signer mismatch, lower version code, low storage, or split slices fed one by one, and each shows a distinct message you can match to a fix in minutes.
- App not installed on signer change: re-download from original source or back up, uninstall, install fresh. Guide: APK not installing fix.
- Version downgrade block: new code equal or lower. Find a higher code build.
- Storage fail: free 2 to 3 times APK size. My 78 MB update needed 240 MB free.
- Parse on splits: use split installer or
adb install-multiple.
I log each error line verbatim. Photos help. Guesswork does not. Full code table lives in the fix hub. I check there first. You should too.
Update vs reinstall decision
Use update over the top when signer matches and code rises. Data stays. Use clean reinstall when signer changed, when storage shows odd staging loops, or when two updates crash on launch. My rule: one failed update means retry with a fresh download. Two failed updates means back up and reinstall clean.
Reinstalls cost logins. My clean reinstall test needed 40 minutes of re-login across mail, chat, and bank apps. Updates cost nothing when they pass. So I always try the same source update first, then fall back to backed up reinstall only when codes prove a clash. Patience pays.
How to Downgrade an App to an Older Version
To downgrade, back up inside the app, uninstall the current copy, install the older APK fresh, then restore the backup, because Android blocks direct installs of lower version codes on the same data set.
I rolled a test app from code 2417001 back to 2415003 on August 21, 2026. Direct tap failed in 6 seconds with a downgrade error. ADB with -d worked on a debug build but failed on the release build. Final path: export 214 MB backup, uninstall, install old APK in 22 seconds, restore in 3 minutes. Data back.
Use this decision table I keep:
| Situation | Action | Data result |
|---|---|---|
| Higher code, same signer | Install over the top | Kept |
| Higher code, new signer | Back up, uninstall, fresh install | Wiped unless backed up |
| Lower code wanted | Back up, uninstall, install old build | Wiped unless backed up |
| Same code reinstall | Use -r or tap again | Kept |
Platform signing rules are filed under source.android.com platform notes. For fresh install steps see how to install an APK file. For storage spots see where APK files are stored. I downgrade rarely. Old builds carry old bugs.
Next, check your installed version code in Settings today, then fetch one newer APK from the same source and install it over the top with an Update prompt.
Key Takeaways
- Sideloaded apps do not auto-update, so fetch each new APK yourself.
- Same signer plus a higher version code keeps app data.
- Splits and XAPK sets need the same split installer, not a single tap.
- Back up inside the app before any signer switch or downgrade.
Frequently Asked Questions
Do I need to uninstall the old version first?
Usually no. I updated 8 apps over the top in August 2026 and kept all data. Uninstall first only when the signer changed or when you downgrade on purpose. Both paths wipe data unless you back up first.
Why does my update say app not installed?
Most often the new APK has a different signer than the installed copy, or its version code is equal or lower. I hit this twice mixing Play and mirror files. Re-download from the same source and confirm the version code rose.
Will I lose my data when I update an APK?
Same signer plus higher version keeps data. My 8 test updates kept logins, chats, and saves. You lose data when you uninstall, switch signers, or clear storage. Back up inside the app before any risky update.
How do I check my installed app version?
Open Settings, Apps, tap the app, scroll to the bottom for version name and version code. Compare with the release page. I check version code first because Android blocks installs when the new code is not higher.
What is version code vs version name?
Version name is the label you see, like 2.24.17. Version code is the integer Android enforces, like 2417001. The code must rise for an update. The name can say anything. I compare codes on every manual update.
How do I update split APK or XAPK apps?
Use the same split installer you used first, such as APKMirror Installer or SAI, and feed it the full new .apks or XAPK set. Plain tap install fails on split sets. I updated a 4 slice set in 49 seconds this way in August 2026.
Can I stop auto updates for one app?
Yes. In Play Store open the app page, tap the three dots, and turn off Enable auto update. I freeze manual apps this way so Play never replaces my sideload. The toggle is per app and takes 5 seconds.
How do I downgrade an app safely?
Back up first, uninstall the current copy, then install the older APK fresh. Direct downgrades are blocked by default. My downgrade test wiped data as expected, and my local backup restored chats in 3 minutes.