Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-4-20250514· AnthropicHugging Face LMArena Human Preference 140K

What would cause an Android phone to give the error "Devices couldn't connect Make sure…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Geminigemini-2.5-flash-preview-04-17’s answer.
  1. User

    What would cause an Android phone to give the error "Devices couldn't connect Make sure your devices are nearby one another and try again" when attempting to retrieve a passkey, even though the devices are very close together and Bluetooth file transfer works between them?

  2. Claude Assistant

    This error typically occurs when there's an issue with the passkey authentication process between your devices. Here are the most common causes:

    Bluetooth version mismatch: Passkey authentication often requires Bluetooth LE (Low Energy) support on both devices. Even if regular Bluetooth file transfer works, one device might lack BLE support or have it disabled.

    Different Google account issues: Make sure you're signed into the same Google account on both devices. Passkeys are often tied to your Google account, and mismatched accounts will prevent the connection.

    Google Play Services problems: The passkey system relies heavily on Google Play Services. Try:

    • Clearing the cache and data for Google Play Services
    • Ensuring it's fully updated on both devices
    • Checking that it has all necessary permissions

    WebAuthn/FIDO2 compatibility: Some older Android devices or apps might not fully support the WebAuthn standard used for passkeys. Check if your devices meet the minimum requirements (typically Android 7.0+ with updated Chrome/WebView).

    Interference from other apps: VPNs, ad blockers, or security apps can sometimes interfere with the passkey handshake process. Try temporarily disabling these.

    Corrupted passkey data: The stored passkey information might be corrupted. Try removing and re-adding the passkey.

    To troubleshoot, I'd suggest starting with clearing Google Play Services cache, ensuring both devices are on the same Google account, and checking that Bluetooth LE is enabled in your developer options (if available).

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.