Updates are supposed to be the boring part of using an app. Most of the time they are: a new version arrives, it installs overnight, and you notice a new button or a smoother timeline. But sometimes an update refuses to install, sometimes it installs and something that worked yesterday stops working, and sometimes everyone else seems to have a feature that your phone does not. All three feel like the same problem, but they have different causes and different fixes.
Edits Guide is an independent, unofficial guide. It is not affiliated with Meta or Instagram, and this page describes what you can check and fix yourself — not promises about any particular release.
The symptom, precisely
“Update problems” covers four situations, and naming yours narrows the fix immediately. First, the update will not download or install: it stalls, errors, or the store says there is not enough space. Second, the update installed but something broke: a feature misbehaves, the app crashes more, or a project looks wrong. Third, the update is nowhere to be found: the store shows no new version and a feature other people are talking about is missing from your app. Fourth, the update installed but nothing visibly changed, which is often not a problem at all — many updates are small fixes behind the scenes.
If the app has started crashing after an update, also work through App Crashing or Won’t Open and Not Enough Storage, because an update needs free space both to install and to run.
Likely causes, ranked
- Staged rollout. The new version has not reached your phone, account, or region yet. This is the most common reason a feature is “missing,” and it needs patience, not repairs.
- Not enough free storage. An update downloads a whole new package and needs working room. A nearly full phone stalls or refuses the install.
- Weak or interrupted connection. A large download on a patchy connection stalls, corrupts, or restarts repeatedly.
- A phone or store setting blocking updates. Auto-update turned off, a data-saver mode, or a pending phone-system update can all hold an app update back.
- A genuine bug in the new version. Sometimes the update itself is the problem: a feature regresses, crashes increase, or an export behaves differently. This is the least common cause but the one people remember.
- A device too old for the new version. Eventually an app requires a newer phone system than an older phone runs. When that happens, no fix on the phone will make the update appear.
Fixes in order, quickest first
1. Check the official store listing. Open the Edits listing on Google Play or the App Store and look for an Update button. If the listing shows only Open, you already have the latest version your phone has been offered — and the missing feature is a rollout question, not a fault. Always update from the official listing, never from a file downloaded elsewhere.
2. Free up storage before retrying. Updates fail silently on full phones. Clear space using Not Enough Storage — delete duplicate exports, back up the camera roll, clear caches — then try the install again. A few hundred megabytes of headroom makes a surprising difference.
3. Switch to strong, stable Wi-Fi. Pause the download, connect to reliable Wi-Fi, and start it again. Avoid installing a large update over a weak mobile signal or a public hotspot that drops connections.
4. Restart the phone, then retry. A restart clears stuck download states and temporary store glitches. After the phone comes back up, open the store listing and try the update once more before attempting anything deeper.
5. Check auto-update and data-saver settings. If the store is set to update apps only on Wi-Fi, or data saving is blocking background downloads, the update may sit queued for days. Turn auto-update on for Edits, allow updates on Wi-Fi, and check that no data-saver or battery-saver mode is pausing the store.
6. Update the phone’s system first, if one is waiting. Some app updates require a minimum phone-system version. If a system update is pending, install it, restart, and then check the Edits listing again.
7. Clear the store app’s cache — not Edits’ data. If the store itself is stuck showing an old version, clearing the store app’s cache can refresh its listings. Do not clear Edits’ data: that wipes drafts. This step is about the store, not the editor.
8. Reinstall only as a last resort, and only after exporting. If an update has genuinely corrupted the app, uninstalling and reinstalling from the official listing gives you a clean copy — but it deletes on-device drafts. Export every finished project first, accept that unfinished drafts will be lost, and treat this as the final step, not the first.
When an update breaks something that worked
A new version can introduce a bug, and the signs are distinctive: the problem starts the same day as the update, it affects a specific feature, and other people report the same thing. First, confirm the timing — did the problem really start with the update, or did it coincide with a full phone or a changed setting? Then try the lightest remedies: force-close and reopen, clear Edits’ cache, and test the feature on a short new project. If the breakage is real and widespread, the honest fix is usually to wait for a follow-up release, which typically arrives quickly for a serious regression. Downgrading by sideloading an older file is not a safe workaround — it bypasses the store’s checks and can introduce worse problems.
When a feature everyone else has is missing from your app
This is almost always a staged rollout. New features reach phones in waves over days or weeks, and the order is decided by the developer, not by anything you can change on your device. Checking the store listing confirms whether a newer version exists at all; if it does and your phone is still on an older one, work through the install fixes above. If the listing shows you are up to date, the feature simply has not reached your account yet. Reinstalling will not summon it, and neither will logging out and back in — those steps risk your drafts for no gain.
How to tell when it is a rollout or a server problem
Three signs point away from your phone. First, the store shows no update at all while other people describe one — that is a rollout in progress. Second, the problem started everywhere at once, for many users, with no change on your device — that smells like a server-side issue or a bad release. Third, the app’s features that need a connection fail together while offline editing still works — that points to the service, not your install. In all three cases the genuine fix is to check the updates page for what is known, keep the app as it is, and wait. Repeated reinstalls during a server problem only add risk to your drafts.
Keeping updates painless afterwards
Turn auto-updates on for Edits and let them happen overnight on Wi-Fi, so you never install a large update in a hurry before a shoot. Keep a little free storage at all times, export finished projects promptly, and read what a new version changes before you depend on it for an important edit. A calm update routine is the cheapest insurance against every problem on this page.
Frequently asked questions
Why does my friend have a feature I do not?
Features roll out in stages. If your store listing shows you are up to date, the feature has not reached your phone yet. It usually arrives within days or weeks, with no action needed from you.
The update keeps failing. What is the first thing to check?
Free storage. A nearly full phone is the most common reason an update stalls or refuses to install, and it is also the easiest to fix.
Should I reinstall Edits to get the new version?
No — not to chase an update. Reinstalling deletes on-device drafts and does not speed up a staged rollout. Reinstall only when the app itself is genuinely broken, and only after exporting everything important.
Can I download an update file from another site?
Do not. Files from outside the official stores can be altered, outdated, or bundled with malware, and they bypass the checks that keep your phone safe. Update only from Google Play or the App Store.
An update broke a feature I rely on. What now?
Confirm the problem started with the update, try the light remedies — force-close, clear cache, test on a short new project — and then wait for a follow-up release. Serious regressions are usually fixed quickly, and meanwhile you can export existing work or use the feature’s closest alternative.
Get Edits on Google Play Get Edits on the App Store
Next: Edits Not Available → · All help guides →
Most update trouble is not trouble at all — it is a rollout in progress or a phone that needs a little room and a stable connection. Work through the fixes in order, resist the urge to reinstall, and remember that waiting is a legitimate fix when the problem sits on the developer’s side of the fence.
What to do while you wait for a fix
Waiting for a rollout or a follow-up release does not have to stall your editing. Keep working on the version you have: export finished projects, back up important drafts, and note exactly which feature misbehaves so you can test it the moment the new version arrives. If a broken feature blocks a deadline, consider whether an older project can be finished with a different tool on this site — the tutorials cover workarounds for most features — rather than risking your drafts on an unofficial download.
When the phone itself is the limit
If no update is offered because the phone’s system is too old, check whether a system update is available in the phone’s settings. If the phone no longer receives system updates, it has reached the end of its supported life for newer apps — a hard truth, but a useful one. In that case, keeping the current version of Edits working, exporting regularly, and planning a move to a supported device beats chasing updates that will never arrive.