When setting up or reconnecting a Fitbit Versa 4 with an Android smartphone, Google Fast Pair is designed to display an automatic setup card the moment the watch is near the phone. When the process fails, the Fast Pair card either freezes on “Connecting…”, throws an “Unable to pair” error, or disappears entirely without linking the watch. This issue happens when the Google Play Services Bluetooth cache becomes out of sync with the watch’s Low Energy advertising beacon, or when an incomplete pairing key blocks the handshake.
Quick Answer
Open your phone’s Settings > Google > Devices & sharing > Devices > Saved devices and remove any listed Fitbit Versa 4 entries. Turn Bluetooth off for 10 seconds, turn it back on, and restart both your phone and your watch. Skip the system pop-up and complete the pairing process directly inside the official Fitbit app.
Device & Signal Snapshot
- Model: Fitbit Versa 4
- Protocol: Google Fast Pair Service (GFPS) over Bluetooth Low Energy (BLE)
- Host OS: Android 11 through Android 16+
- Primary Symptoms: “Connecting…” screen spins endlessly, “Pairing Failed” alert, or the Fast Pair half-sheet pop-up never triggers
- Data Risk: None (applies only to initial pairing or reconnecting an unlinked device)
What Is Actually Happening?
Google Fast Pair relies on a three-way cryptographic handshake between the Fitbit hardware, your phone’s Google Play Services framework, and your Google Account cloud identity:
Google Fast Pair Architecture:
[Versa 4] ──(BLE Broadcast Beacon)──> [Android System: Fast Pair Pop-Up]
│
(Queries Google Account)
│
▼
[Fitbit App Setup] <──(Transfers Auth Key)── [Google Play Services]
When you put the Versa 4 into pairing mode, it continuously broadcasts a unique Fast Pair Model ID via BLE advertising packets. If your Android phone has Bluetooth and Location services enabled, the operating system catches this packet, matches it against Google’s device repository, and shows the slide-up notification card.
When Fast Pair fails, the communication chain is typically broken at one of these stages:
- The Stale Cloud Key: Your Google Account has an incomplete cryptographic token saved from a previous pairing attempt. The phone attempts to use the saved key, while the watch expects a fresh handshake.
- Google Play Services BLE Cache Lock: The background process handling GFPS encounters a socket timeout, blocking other apps from using that specific Bluetooth profile.
- App Permission Conflicts: Android’s strict Nearby Devices permission model blocks the Fitbit app from taking over the connection from the OS-level Fast Pair card.
Step-by-Step Diagnostic & Resolution Protocol
Step 1: Clear the Stale Fast Pair Cloud Token
If your Google Account has saved a partial pairing attempt, the Fast Pair service will repeatedly push an invalid authentication key to the watch.
- On your Android phone, open the main system Settings.
- Scroll down and tap Google (or Connected devices > Google depending on your phone’s menu layout).
- Select Devices & sharing > Devices.
- Tap Saved devices.
- Look for Fitbit Versa 4 in the list. If it appears, tap the gear icon next to it and select Forget or Remove.
- This purges the invalid security key from your Google Account across all devices.
Step 2: Clear the Android Bluetooth and Play Services Caches
Stale system processes often prevent the phone from completing new Bluetooth handshakes.
- Go to Settings > Apps > See all apps.
- Tap the three dots in the upper-right corner and choose Show system.
- Locate Bluetooth (or Bluetooth Legacy) and tap it.
- Select Storage & cache, then tap Clear Cache. For a deeper walk-through on resetting Android’s wireless engine, review How to Clear the Bluetooth System Cache on Android 16 (The “Clean Slate” Fix).
- Return to the app list, locate Google Play Services, tap Storage & cache, and select Clear Cache (do not clear data).
- Turn off Bluetooth for 10 seconds and turn it back on. For details on why this delay is necessary, see The “10-Second Toggle” Protocol: Fixing Stuck Bluetooth Handshakes.
Step 3: Reset the Versa 4 Pairing State
A watch stuck in a half-paired state will refuse incoming connection attempts.
- On the Versa 4, press and hold the physical side button for approximately 10 seconds until the Fitbit logo appears on the screen, then release it to perform a soft reboot.
- If the watch has already completed initial onboarding, swipe to Settings > About Versa 4.
- If you are moving the watch from an older phone, select Factory Reset. (Note: This erases data on the watch, but anything previously synced to your account remains safe).
- When the watch reboots, it should display the setup prompt showing the Fitbit logo and a phone icon.
Diagnostic Pairing Decision Tree:
[Fast Pair Pop-Up Appears] ──> Fails on "Connecting"?
│
┌──────────────────┴──────────────────┐
▼ ▼
[Clear Google Saved Devices] [Dismiss Pop-Up Entirely]
│ │
[Re-attempt Fast Pair Flow] [Pair Directly in Fitbit App]
Step 4: Bypass Fast Pair and Connect via the Fitbit App
If Fast Pair continues to hang, bypass the Google system pop-up entirely and connect using the manual in-app protocol.
- When the Fast Pair slide-up card appears on your Android screen, swipe it down or tap Cancel to dismiss it.
- Open the Fitbit app on your phone.
- Tap the Devices icon in the upper-left corner of the Today tab.
- Select Add a device (or Set Up a Device).
- Choose Versa 4 from the product list and tap Set Up.
- Follow the in-app pairing instructions. When the watch displays a 4-digit code, enter it directly into the Fitbit app prompt. For troubleshooting manual pairing drops, see “Device Not Found”: Troubleshooting Initial Pairing for New Smartwatches.
What to Check If Pairing Still Won’t Complete
- Audit Android Nearby Devices Permissions: Make sure the Fitbit app has permission to find nearby hardware. Go to Settings > Apps > Fitbit > Permissions, select Nearby Devices, and ensure it is set to Allow. If set to “Don’t Allow,” Android will block the connection. See The “Bluetooth Permission” Prompt: Why “Don’t Allow” Bricks Your Initial Setup.
- Google Account Migration Conflict: If you are transitioning from an older legacy Fitbit login to a Google Account, sync servers can occasionally freeze the profile handoff. Resolve migration blocks using Fitbit “Syncing Unavailable” — The 2026 Google Account Migration Fix.
The Bottom Line
Fast Pair failures are almost always caused by stale cloud tokens or cached Bluetooth errors in Google Play Services. Remove the Versa 4 from your Google “Saved Devices” menu, restart both devices, and complete the connection through the Fitbit app rather than the system pop-up.