Symptoms
Google account security lists a passkey but the login browser never proposes it. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: Google account security lists a passkey but the login browser never proposes it.
- Control test: Compare sign-in on the passkey-holding device with a different device using the same account.
- A confirmed correction must meet this outcome: The expected passkey appears and completes sign-in on the intended device.
A working state in another app or device is a useful control only when the account, source material and operating conditions are comparable. If they differ, that comparison may produce a misleading conclusion.
Why It Happens
A credential prompt is a security boundary, not merely a convenience screen. A successful unlock of a local password vault does not establish that the website or app can safely receive an autofill suggestion. Account recovery, passkey location and sign-in policy must be evaluated separately.
The symptom alone cannot distinguish device screen lock disabled from passkey stored on another credential provider. Evidence related to unsupported cross-device flow changes the next action, so record the comparison before applying a fix.
Three competing explanations
- Device screen lock disabled.
- Passkey stored on another credential provider.
- Unsupported cross-device flow.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports device screen lock disabled does not automatically exclude passkey stored on another credential provider; the comparison needs to separate them.
Before Making Changes
Keep another legitimate sign-in route available and never disclose active codes, recovery material or vault exports to anyone. Do not delete the only recovery method or bypass account security.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare sign-in on the passkey-holding device with a different device using the same account. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Device screen lock disabled | If the failing state changes under the comparison, device screen lock disabled is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Passkey stored on another credential provider | If the first change has no effect but a supported configuration differs, passkey stored on another credential provider moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Unsupported cross-device flow | If both earlier paths are contradicted, investigate whether unsupported cross-device flow accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Turn on a supported screen lock, sign in on the device holding the passkey, and use Try another way if blocked. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Verify the affected workflow
Google account security lists a passkey but the login browser never proposes it. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare sign-in on the passkey-holding device with a different device using the same account. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Try the smallest safe intervention
Turn on a supported screen lock, sign in on the device holding the passkey, and use Try another way if blocked. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
The expected passkey appears and completes sign-in on the intended device. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for device screen lock disabled, passkey stored on another credential provider and unsupported cross-device flow separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Check the responsible subsystem
Review the account passkey inventory and remove only a confirmed lost-device credential after retaining another sign-in method. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Validate the unaffected path
Revisit the comparison: Compare sign-in on the passkey-holding device with a different device using the same account. If the first suspected cause is not supported, compare the behavior predicted by passkey stored on another credential provider with the behavior predicted by unsupported cross-device flow. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: The expected passkey appears and completes sign-in on the intended device. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the identity provider or password manager's official account-recovery support. Safety boundary: Do not delete the only recovery method or bypass account security.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming device screen lock disabled is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare sign-in on the passkey-holding device with a different device using the same account.
- Skipping this safety boundary: Do not delete the only recovery method or bypass account security.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: The expected passkey appears and completes sign-in on the intended device. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare sign-in on the passkey-holding device with a different device using the same account.
- Check the stated pass result: The expected passkey appears and completes sign-in on the intended device.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Review the account passkey inventory and remove only a confirmed lost-device credential after retaining another sign-in method. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the identity provider or password manager's official account-recovery support, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether device screen lock disabled, passkey stored on another credential provider and unsupported cross-device flow were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: The expected passkey appears and completes sign-in on the intended device. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: Google account security lists a passkey but the login browser never proposes it. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
Official Resources
- Google Account Help: Sign in with a passkey instead of a password – vendor documentation specifically relevant to this workflow.
FAQ
How can I tell whether device screen lock disabled is responsible?
Run the controlled comparison: Compare sign-in on the passkey-holding device with a different device using the same account. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is passkey stored on another credential provider rather than device screen lock disabled?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Review the account passkey inventory and remove only a confirmed lost-device credential after retaining another sign-in method. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: The expected passkey appears and completes sign-in on the intended device. If it fails after the normal workflow is repeated, document whether unsupported cross-device flow still explains the remaining behavior and escalate with non-sensitive observations.