Signing in to Gmail from abroad: when the text message code does not arrive

When signing in from a new country or a new device, Google often asks for extra confirmation. If it then waits for a text message code, signing in can easily get stuck while travelling: the foreign network delivers the message late or not at all, or the home SIM card is not in the phone. Fortunately, a text message is only one of the possible methods, and several others do not need a mobile network at all.

Why does Google ask for confirmation abroad?

Google pays attention to where and from which device a sign-in comes. If the request comes from another country, a new computer, a hotel or internet café computer, or through a VPN, Google's help says it uses an extra step to check that it really is the owner signing in. This can happen even if 2-Step Verification is not turned on. On an already signed-in phone or laptop of one's own, Gmail usually keeps working abroad without problems, so signing out while travelling is rarely a good idea.

Symptoms, causes and fixes

• The text message is late or never arrives. Cause: delivery depends on the carrier and the country, and is often slower when roaming; according to Google, sending text messages may even be blocked for an unusual sign-in. Fix: request a new code only once, and always enter the latest one; requesting it repeatedly can slow things down further. Choosing another method is better.
• The home SIM is not in the phone, or roaming is turned off. Cause: when a local or travel SIM or a data-only eSIM is used, text messages to the home number do not reach the device. Fix: in a dual-SIM phone, the home SIM can be left on (data can stay on the local card), or a verification method without text messages can be chosen.
• Google wants to call, but the call cannot be answered. Cause: without signal, the code may go to voicemail as a voice message. Fix: choose another verification method.
• The Google prompt does not arrive on the phone. Cause: the phone has no internet, “Do Not Disturb” is on, or the account is not signed in on the phone. Fix: connect to Wi-Fi, turn off “Do Not Disturb”, then choose “Resend it” on the device being signed in.
• Google says it cannot verify that the account belongs to the user. Cause: too many new circumstances at once (new country, new device, new network). Fix: try from an already signed-in device of your own, without a VPN; if none is at hand, it is easiest after returning home, from a familiar place.

Verification methods without text messages

On the sign-in screen, “Try another way” shows which methods are available for the account. Only the methods the owner set up earlier appear.

• Google prompt: answer “Yes” to the question that appears on the signed-in phone; for a sign-in from an unusual place, Google may also ask for a number to be matched between the two screens. No mobile network is needed, only internet, so hotel Wi-Fi is enough.
• Passkey: a key stored on the phone or laptop, unlocked with a fingerprint, face or PIN. On someone else's computer, after “Try another way” and using a passkey, scan the QR code that appears with the phone; Bluetooth is needed on both devices.
• Google Authenticator app: the phone generates the codes itself, even without a network. It only works with 2-Step Verification on, and must be set up before leaving.
• Backup codes: ten eight-digit codes, each usable once, which can travel on paper or in a secure file. With 2-Step Verification on, they can be created in the account's security settings.
• Security key: a physical USB or NFC key, which also does not need a mobile network.
• Recovery email address: for some checks, Google may also send a code there, if another mailbox is accessible.

Checklist before leaving

Most problems abroad can be prevented by setting things up before the trip, at home, on a familiar device. According to Google's help, changes to recovery and sign-in details can take up to seven days to apply in every situation, so it is best to start at least a week before leaving.

1. At myaccount.google.com/security, check that the phone number and recovery email address are correct and reachable.
2. Sign in to the Google Account on the phone (on Android in the system, on iPhone in the Gmail or Google app), and test whether the Google prompt arrives.
3. Create a passkey at myaccount.google.com/signinoptions/passkeys.
4. With 2-Step Verification on, download or print the backup codes and keep them separately from the phone.
5. If a local SIM card will be in the phone during the trip, also set up the Google Authenticator app.
6. Ask the mobile carrier whether roaming and receiving text messages work in the destination country.
7. Sign in at home on the devices that will be used on the way (laptop, tablet).

Google Play App Store

On someone else's computer and public Wi-Fi

• On a hotel or internet café computer, use a private (incognito) window and do not save the password.
• If the browser offers it, do not mark the computer as trusted (“Don't ask again on this computer”).
• Sign out after use; if that was forgotten, the other computer can be signed out remotely from the Google Account device list on your own phone.
• With a VPN, the sign-in location can look even more unusual. If confirmation gets stuck, turn off the VPN while signing in.
• Some “security alert” emails received while travelling are scams. How to recognize them: Common scam emails in Gmail and how to spot them.

If signing in is completely stuck

Google cannot make an exception by phone or email, and does not offer account recovery by phone. If none of the verification methods works, go through the recovery that starts at accounts.google.com/signin/recovery: Resetting a forgotten Gmail password. This is harder from abroad, because Google also takes the familiar device and location into account; in many cases it works after returning home. If a phone was stolen or lost, the account's security also needs attention: Hacked Gmail account: first steps.