Google Authenticator Preps Old-Code Import: Import, Wait, or Discard [APK Teardown]

Contents hide

What to know
Google Authenticator may prompt you to import old-device codes
Discarding codes gets a confirmation step
The build also includes Google logo path strings

What to know

Google Authenticator is working on a staged import flow for authentication codes from an old device.
The flow lets you import the codes now, defer the prompt, or discard the detected codes.
This is dormant text in Google Authenticator v7.2 code, and the flow is not available to users yet.

Google Authenticator is getting a cleaner way to handle authentication codes left over from an old device. Moving 2FA codes is one of the more sensitive parts of changing phones, so the app needs to make clear what is being brought over and what happens if you decline.

Google Authenticator v7.2 includes code for a staged import prompt that detects old-device codes and asks whether you want to import, postpone, or discard them.

About unreleased app code — Reading not-yet-shipped code inside a beta build can show features a developer is preparing before they’re announced. Work-in-progress code can still change, stay hidden behind a server-side flag, or be scrapped before it ever reaches your phone.

Google Authenticator may prompt you to import old-device codes

The flow starts with a direct message: Google Authenticator has found codes from your old device. The dialog title asks whether you want to import authentication codes, while the three buttons give you clear choices: import, not now, or discard.

KEY!That points to a staged handoff rather than a silent migration. If this ships, Authenticator will give users a safer pause point during setup, especially when old 2FA codes are detected but the user is not ready to make a final decision.

staged_import_dialog_message = “We found codes from your old device”

staged_import_dialog_title = “Import authentication codes?”

staged_import_dialog_positive_button = “Import”

staged_import_dialog_neutral_button = “Not Now”

staged_import_dialog_negative_button = “Discard”

Discarding codes gets a confirmation step

The code also includes a second confirmation dialog for discarding authentication codes. The warning says the action cannot be undone, and the buttons give users a chance to cancel before confirming the discard.

Google Authenticator also has success messages for both outcomes: codes imported successfully, and codes discarded. A partial success message is present too, with two placeholders that can be filled by the app.

staged_import_confirm_discard_title = “Discard authentication codes?”

staged_import_confirm_discard_message = “This can’t be undone”

staged_import_confirm_discard_negative_button = “Cancel”

staged_import_confirm_discard_positive_button = “Discard”

staged_import_success_message = “Codes imported successfully.”

staged_import_discard_message = “Codes discarded.”

staged_import_partial_success_message = “%1$s. %2$s.”

The build also includes Google logo path strings

Alongside the staged import text, Google Authenticator v7.2 includes two vector path strings for a Google “G” asset. These strings do not show a separate new user-facing Authenticator feature, but they are part of the same code set.

super_g_path_cover_24 = “M12,14.26V10H22.36C22.49,10.72 22.56,11.47 22.56,12.25C22.56,12.943 22.509,13.614 22.409,14.26H17.92H12Z”

super_g_path_main_24 = “M12,18.63C15.23,18.63 17.45,16.79 17.92,14.26L20,12L22.409,14.26C21.604,19.462 17.649,23 12,23C5.92,23 1,18.08 1,12C1,5.92 5.92,1 12,1C14.97,1 17.45,2.09 19.36,3.87L16.21,7.02C15.06,5.94 13.62,5.38 12,5.38C8.41,5.38 5.49,8.43 5.49,12.01C5.49,15.59 8.41,18.63 12,18.63Z”

KEY!The staged import flow is not available to users yet, but the strings in Google Authenticator v7.2 show Google is preparing a more deliberate old-device code import experience.

Related guides