You've switched to a new phone, the old device has been factory reset or passed on, and you open Potato only to get stuck on the login page—the verification code doesn't arrive, it keeps spinning, or it says verification failed. Most of these problems aren't because the account is "gone," but because some step in the migration process broke. The checklist below is ordered from easiest to hardest; go through it item by item, and don't just retry repeatedly right away.
First, confirm: which step are you stuck on?
Potato login failures usually fall into three types, each handled completely differently. The first is not receiving the verification code after entering your phone number; the second is getting an error or timeout after entering the code; the third is being able to enter the interface but getting logged out immediately. Figure out which one you're dealing with first, then proceed—it can save you half of the ineffective actions.
One more reminder: if you're still logged in on the old phone, don't rush to log out. When the old device is online, many verification steps go much more smoothly. You can first use the old device to confirm the account status, then deal with the new phone.
Verification code not received: troubleshoot in this order
- Wait a full 60 seconds before tapping resend. Making consecutive requests in a short time can easily trigger a temporary limit—the more you tap, the less likely you are to receive it.
- Check SMS interception. Many Android models (such as some Xiaomi and Huawei systems) by default sort unknown numbers into the "Blocked messages" folder—go look there.
- Confirm the number format. If you entered the old number after switching, the verification code naturally won't reach the new SIM card.
- Switch networks. Switch from Wi-Fi to mobile data, or vice versa, and request again.
- Try another verification method. If the interface offers voice call or a backup verification entry, you can try it.
A real scenario: after a user migrated all data from an old iPhone to a new iPhone, SMS messages were forwarded to the number bound to the old device, and the new phone never received them. The solution is to first confirm on the carrier side which device receives SMS, then request again. This kind of problem has nothing to do with Potato itself, but it's easily mistaken for a login failure.
Code is correct but rejected: check time and device
Verification codes have an expiration time, usually only a few minutes. If the phone's system time deviates too much from network time, validation will fail directly. Go to settings, turn on "Set date and time automatically," and try again.
Device count limits are also a common cause. If the same account stays logged in on too many devices, the new device may be blocked. In this case, on a device you can still use, go to settings, clear login sessions you no longer use, then return to the new phone and try again. For the relevant operation paths, see the account and login section in the FAQ.
There's also a hidden case: the new phone has a modified installation package from an unknown source installed. Such versions may alter the login process and cause verification anomalies. It's recommended to get the installation file from the Potato download and installation page, uninstall the old package, and then install.
If it still fails, protect your account first, then ask for help
If it fails more than five or six times in a row, it's best to stop. Continuing to try may trigger a longer cooldown. At this point, prioritize three things: confirm the bound phone number is still in your hands; check whether two-step verification is enabled and you forgot; and check on a device where you're still logged in for any abnormal login records.
For specific options on account security settings, you can read the privacy and security settings guide, which explains the practical use of two-step verification, login alerts, and session management. If the account has ever been bound to automation tools, also pay attention to the authorization scope mentioned in the bot feature description, to avoid handing login credentials to untrusted third-party scripts.
Prevent pitfalls the next time you switch phones
Do two things before switching phones to avoid most trouble: first, confirm the account is bound to a usable phone number and remember the two-step verification password; second, keep the old device for at least a week, and only deal with it after the new phone is fully working. After migration is complete, check the logged-in device list and remove any sessions you don't recognize.
If there's still no progress after troubleshooting, you can browse the news and announcements section to see whether there are any service status notes related to login. Most phone-switch login problems can be pinpointed within half an hour using the steps above—the key is not to keep stubbornly retrying the same step.
Continue reading: downloads and installation, accounts and verification codes, groups, channels, and bots, and privacy and security.
