You've waited two minutes and the verification code still hasn't arrived, and the login page only gives you one chance to resend. At times like this, it's easy to keep tapping "Resend" and end up using up the request quota for a short period. Below, we break it down into three directions: network, number, and device. It's recommended to go from top to bottom, and after each step, wait 60 seconds before checking the result.
First, confirm your network and time—don't let the request get stuck halfway
The verification code request is sent from your device to the server, and then the server triggers the SMS channel. If any part is down, the symptom is "spinning and then nothing." Do a simple test first: open a browser and visit a commonly used website. If the webpage also won't load, it's a network problem itself, not a Potato problem.
- Switch networks: change Wi-Fi to mobile data, or vice versa. Some public Wi-Fi networks block overseas SMS interfaces.
- Turn off proxies and acceleration tools: proxies change the exit IP, and SMS requests may be flagged as coming from an abnormal source.
- Check the system time: if your phone time differs from standard time by more than a few minutes, request signatures can become invalid. Turn on "Set date and time automatically" in settings.
- Reset with airplane mode: turn on airplane mode for 10 seconds and then turn it off to force network re-registration.
If you use a dual-SIM phone, note that the SMS may have gone to the other card's inbox. On Android models such as Xiaomi and OPPO, you can check the "SIM 1/SIM 2" tabs in the SMS settings, while on iPhone you can switch number labels at the top of the Messages list.
Number format and SMS interception are the two most common pitfalls
When entering your number, make sure the country/region code is correct. For mainland China numbers, choose +86, then enter the 11-digit mobile number, and do not add a 0 in front. A format with 0 will be treated by the system as an invalid number. The page usually won't show an error; it will just quietly do nothing.
The number itself can also have status issues. Numbers that are suspended but retained, in arrears, or that have just completed mobile number portability may experience SMS channel delays of several hours. Virtual operator number ranges (such as those starting with 170 or 171) have lower delivery rates on some channels. If you fail to receive the code twice in a row, testing with a physical carrier number is the fastest way to determine the cause.
SMS interception happens more often than you might think. Check these locations:
- The "Spam" or "Junk" folder in the system SMS app.
- Interception records in phone manager apps (such as Tencent Mobile Manager or 360 Mobile Guard).
- Carrier-level SMS filtering services—call customer service to ask whether it is enabled.
- iPhone's "Filter Unknown Senders" feature, which folds messages from unknown numbers into a separate list.
If you can receive the code immediately after switching numbers, it means the original number is restricted by the channel. You can try again after 24 hours, or contact your carrier to confirm whether SMS functionality is working properly.
Cleanup actions at the device and app level
If the network and number are both fine, then look at the device. Potato's verification code request depends on the session between the app and the server. When the cache is corrupted, the symptom is "tapping and nothing happens." You can handle it in the following order:
- Fully exit the app (not just switch to the background), reopen it, and request again.
- Clear the app cache: on Android, go to "Settings → Apps → Potato → Storage → Clear cache"; on iOS, you need to uninstall and reinstall.
- Update to a newer version. Older versions may still be using discontinued interfaces. You can get the installation package from the Potato download and installation page, and be sure to verify the file source.
- Log in with the same number on another device. If the new device can receive it, the problem is with the original device's system or SMS permissions.
- Check whether SMS permission is disabled. Some Android systems disable app access to SMS by default. Although the verification code is in SMS form, the autofill feature will stop working.
There is another easily overlooked point: repeated requests within a short time will trigger rate limiting. Usually the quota recovers after waiting 10 to 30 minutes. During this period, do not keep tapping, otherwise the waiting time will be recalculated.
If you still don't receive it, you can continue like this
If you've done the three steps above and there is still no message, try again at a different time. SMS channels may back up during evening peak hours and holidays, and delivery is usually more stable in the early morning or on weekday mornings. If the number has previously been bound to another account, confirm that the verification code was not sent to an old device.
For content about the account's own security settings, login device management, and more, you can check the FAQ, which is categorized by scenarios such as login, verification, and notifications. If you are more concerned about how bots and automation features affect the verification process, the bot usage instructions explain the relevant configuration items. When you need to reinstall, go back to the download page and choose the version for your system. It is recommended to back up your chat history before installing.
Verification code problems are usually not caused by a single reason, but by a combination of network, number, and device. Troubleshoot in order, changing only one variable at each step. That makes it easier to pinpoint the problem than switching both the network and the number at the same time.
Continue reading: downloads and installation, accounts and verification codes, groups, channels, and bots, and privacy and security.
