Edits signs in with your Instagram account, so a login problem usually is not an Edits problem at all. It is a connection fault, a wrong account, a code that never arrives, or an account state that only Meta can change. The trick is telling those apart, because only the first three can be fixed from your phone.
Login trouble has a few shapes: the sign-in loops back to the start, the code never arrives, the app says the account does not exist, or you keep getting signed out. Each shape points at a different cause, and the fixes below are ordered so the quickest checks come first.
By Alex Carter, Editor · Published October 24, 2026 · Updated October 24, 2026
30-second answer: Retry on stable Wi-Fi, confirm you are signing in to the right Instagram account, and wait ten minutes for a code before resending it once. If sign-in fails on every device, the cause is usually a server fault or an account state only Meta can change, and no amount of reinstalling will fix it.
In this guide
- What you are seeing
- Likely causes, ranked
- Fixes, quickest first
- When it is a rollout or server problem
- Prevent it next time
- When the problem is the account, not the app
- Still stuck?
- Frequently asked questions
What you are seeing
The loop is the most common shape: you sign in, the app accepts it, and a moment later you are back at the sign-in screen. That usually means the session could not be saved, the connection dropped during the hand-off, or the app data was cleared between attempts. A code that never arrives is a different problem, and an account that the app says does not exist is usually a wrong-account problem, not a broken app.
Repeated sign-outs have their own cause: the phone is clearing app data, the app is being offloaded, or the account is being used on too many devices at once. Note which shape yours is, and note whether it fails on one device or every device, because that distinction decides whether the fix is on your phone or on the server.
Likely causes, ranked
- Unstable connection during sign-in. The sign-in hand-off needs a steady connection from start to finish. A drop halfway through looks like a loop or a failure.
- Wrong Instagram account. Many people have more than one Instagram account, and signing in to the wrong one, or mistyping the name, produces a confusing error.
- Code delivery delay or filtering. Codes can be delayed by minutes, filtered as spam, or sent to an old number or email still on the account.
- Repeated code requests. Requesting code after code can trigger rate limits that delay delivery further, so the fix becomes the problem.
- Outdated app or emulator. Old app versions and old emulator builds can fail sign-in checks that newer versions pass.
- Account state or server fault. A security hold, a locked account, or a server-side sign-in fault cannot be fixed from your phone, and no reinstall changes it.
Fixes, quickest first
- Retry on stable Wi-Fi. Switch to a steady connection, close the app fully, and sign in again from the start. Do not switch networks halfway through.
- Confirm the right account. Open the Instagram app and check which account is signed in there, then sign in to that exact account in Edits. A single wrong letter produces a confusing error.
- Wait ten minutes for a code, then resend once. Check spam and SMS filters, and confirm the number or email on the account is current. Do not hammer the resend button.
- Update the app. Check the store for an Edits update and install it, and update the emulator too if you are on a computer, since old builds fail sign-in checks.
- Restart the phone and clear the cache. Restart, then clear the cache on Android or offload on iPhone. Do not clear storage or data, which resets the app.
- Try another device. Sign in on a second phone or tablet. If it works there, the first device is the problem. If it fails everywhere, the cause is server or account state.
- Reinstall only as a last step. Export any finished work first, because drafts stored only on the device are at risk when the app is uninstalled.
When it is a rollout or server problem
Sign-in is a server-side process, so a server fault can block every account at once, and a staged change can break sign-in for some accounts while others work fine. The test is the second device: if sign-in fails on two devices on two networks, your phone is not the problem.
Check our updates page for the latest status, then wait and try again later. Reinstalling during a server fault fixes nothing and risks drafts, and requesting code after code during a rate limit only extends the wait.
Prevent it next time
Keep the recovery email and phone number on your Instagram account current, and keep the app updated, since most sign-in failures come from stale recovery details or old builds. If you use Edits on a computer, keep the emulator updated too: our PC guide and Mac guide cover emulator setup.
Avoid signing out and back in for fun, and avoid clearing app data, since both can strand drafts and trigger extra verification. Sign in once, on stable Wi-Fi, and leave the session alone.
When the problem is the account, not the app
Some sign-in failures are account states, not app bugs. A security hold after unusual activity, a locked account, or a password that was changed elsewhere can all block Edits sign-in while the app itself works perfectly. In those cases the fix lives in Instagram’s own account recovery flows, not in Edits, and no guide can shortcut it.
The honest test is Instagram itself: if you cannot sign in to the Instagram app either, the problem is the account, and Edits will not sign in until that is resolved. If Instagram signs in fine but Edits does not, the problem is Edits, the connection, or the server, and the fixes above apply.
Do not share your password with anyone claiming to fix the account, and do not pay anyone for account recovery. Real recovery happens through Instagram’s own in-app flows, and anyone asking for payment or a password is not helping.
Still stuck?
If the fixes above have not worked, gather three facts before trying anything else: when the problem started, which step fails, and whether it fails on a second device. Those three facts separate a phone problem from a server problem from an account problem, and they are exactly what any support flow will ask first.
Then stop and wait. Repeated sign-in attempts and code requests during a server fault or a rate limit only extend the lockout, and reinstalling in a loop risks drafts. One clean attempt on stable Wi-Fi, after a wait, beats ten frustrated attempts in a row.
Get the official app
If you are setting Edits up fresh, or you are still on an old version, get it from the official stores. It is free, and it is the only download we recommend.
Back to: Edits Help →
Frequently asked questions
Why does Edits keep asking me to sign in?
Usually the session expired, app data was cleared, or the account was switched. Sign in once on stable Wi-Fi and avoid clearing app data.
Why does my login code never arrive?
Delivery delays, SMS filters, or a wrong number or email on file are the usual causes. Wait ten minutes, check spam and filters, resend once, and confirm the contact on the account.
Why does Edits say my account does not exist?
Usually you are signing in to the wrong Instagram account, or there is a typo. Confirm the exact account in the Instagram app first.
Can I use Edits without signing in?
No, Edits needs an Instagram account to save projects and publish. There is no guest mode that keeps work reliably.
Why does sign-in work on my phone but not on an emulator?
Emulator network and clock issues, and outdated emulator builds, break sign-in. Update the emulator, check its time settings, and use stable Wi-Fi.
Should I keep requesting new codes?
No. Repeated requests can trigger rate limits and delay delivery further. Wait, then request once.
Edits for PC is an independent, unofficial guide. It is not affiliated with Meta Platforms, Inc. or Instagram.
Sign-in on a computer emulator
Sign-in inside an Android emulator has its own failure modes. Emulators can report the wrong time, route network traffic through a virtual adapter, or run an old system image that fails modern sign-in checks, and any of those produces a loop or an error that never appears on a real phone.
Start with the emulator itself: update it to the latest version, give it enough memory and processor cores, and check that its clock is set to automatic time. A clock that is minutes off breaks the security tokens sign-in depends on, and that is one of the few emulator problems with a one-setting fix.
Then sign in on a real phone first, if you can, and confirm the account works there. If the phone signs in and the emulator does not, the emulator configuration is the problem, not the account. Rebuild the emulator instance rather than hammering sign-in attempts, and keep the emulator’s own app updates current, since an outdated emulator app fails the same checks an outdated phone app does.
One clean sign-in attempt, step by step
When sign-in has failed several times, the most effective next move is a single clean attempt, not another rushed one. Connect to stable Wi-Fi, close Edits fully, restart the phone, and open only Edits. Sign in slowly, double-checking the account name character by character, and let the code arrive without requesting another one. A rushed attempt on a weak connection, with a second code requested halfway through, is how a small problem becomes a rate limit.
If the clean attempt fails, write down exactly where it failed: the loop point, the missing code, or the error wording. That note turns a vague problem into a diagnosable one, and it stops the cycle of repeating the same failing attempt and hoping for a different result. The note also tells you whether the next step is a wait, an account recovery flow, or a second-device test.