Getting an “Incorrect PIN or Passkey” message while setting up a smartwatch, smart ring, or fitness tracker almost never means you typed the wrong digits. In most cases, your phone’s Bluetooth system and your wearable fell out of sync during the encrypted handshake—either because a timeout expired, you started pairing from the phone’s Bluetooth menu instead of the companion app, or stale pairing keys from an older session caused a mismatch.
Quick Answer: How to Fix “Incorrect PIN or Passkey” Errors
Cancel setup, forget the wearable in your phone’s Bluetooth settings, and turn Bluetooth off on any nearby old phone. Toggle Bluetooth off on your phone for 10 seconds, restart both your phone and wearable, and start setup strictly inside the official companion app—confirming the pairing popup immediately before it expires.
Device & Signal Snapshot
- Affected Devices: Android and iOS phones pairing with Wear OS, Garmin, Fitbit, Oura Ring, WHOOP, and Bluetooth accessories
- Cause: Expired pairing prompt, stale Bluetooth bonding keys, manual system-level pairing instead of in-app pairing, or hidden confirmation popups
- Data Risk: Safe to retry; only requires resetting the watch if it still holds a half-finished bond to an old phone
What Is Actually Happening?
Modern wearables pair using Bluetooth Low Energy Secure Simple Pairing. Instead of having you memorize a static PIN like 0000, the phone and wearable negotiate a temporary encrypted 6-digit passkey behind the scenes and ask you to confirm that both screens match.
If your phone still holds an outdated encryption key for that device name, if the companion app isn’t managing the handshake, or if the confirmation popup sits unanswered for too many seconds, the security check aborts. Android and iOS then display a generic “Couldn’t pair because of an incorrect PIN or passkey” error—even when you never typed a PIN at all.
How to Tell Which Problem You Have
- Error appears instantly with no 6-digit code shown: You tapped the wearable in Settings > Bluetooth rather than inside the official app, or stale Bluetooth cache keys rejected the bond immediately.
- A 6-digit code shows up, and the error hits after tapping Pair: Either the prompt timed out, another app/overlay blocked the confirmation packet, or the wearable itself still holds an old phone bond.
- The screen specifically asks you to type a code: On some trackers and accessories that display a rotating code on-screen (or require manual entry when auto-detect fails), look closely at the wearable’s display before typing, or check How to Manually Enter a Pairing Code When Auto-Detect Fails.
What to Do: Fix the Passkey Handshake
Step 1: Clear Old Bonds and Reset Bluetooth Timing
- Cancel any active setup screen and force-close the wearable’s companion app.
- Open your phone’s Settings > Bluetooth, locate every listing for the wearable, and tap Forget / Unpair.
- If the wearable was ever connected to an old phone, tablet, or computer in the same house, turn Bluetooth OFF on those extra devices (or forget the wearable there too).
- Toggle Bluetooth OFF on your current phone for 10 full seconds, then back ON—see The “10-Second Toggle” Protocol: Fixing Stuck Bluetooth Handshakes.
- Restart both your phone and the wearable.
Step 2: Clear the Bluetooth System Cache (Android)
On Android phones, clearing the Bluetooth app’s cached key table stops repeated passkey rejections immediately. Follow How to Clear the Bluetooth System Cache on Android 16 (The “Clean Slate” Fix) (try Clear cache first, and Clear storage if rejections continue).
Step 3: Pair Only Inside the Official App (and Catch Popups Fast)
- Open the wearable’s official app (Garmin Connect, Galaxy Wearable, Pixel Watch, Fitbit, Oura, WHOOP, or Meta View/AI)—never Android or iOS Bluetooth settings.
- Temporarily turn off any VPN or battery saver and keep the wearable inches from your phone.
- Watch your notification shade as soon as setup starts. Sometimes Android tucks the Bluetooth “Pair” confirmation into your top notification bar instead of popping it up on screen—if you don’t tap Pair within several seconds, it times out with “Incorrect PIN or passkey.”
What to Check If That Doesn’t Work
Factory Reset the Wearable to Clear Its Side of the Key
If your phone’s cache is clean and the passkey still fails, the wearable itself is likely rejecting the new encryption key because it still remembers an old phone or an interrupted first setup. Perform a factory reset directly on the watch or ring so it boots fresh without old pairing keys, then restart the app setup.
Brand-Specific Pairing Rejections
- Garmin on iPhone: Check Fixing the “Pairing Failed” Message on Garmin Connect for iPhone.
- Samsung phones rejecting handshakes: Follow Fixing “Bluetooth Pairing Rejected” Errors on Samsung Galaxy S26.
- Oura Ring or WHOOP: Run How to Force a Bluetooth “Bonding” Reset for Oura and WHOOP.
- App loops back to the welcome screen: Check Fixing Setup Loops: When the App Returns to the “Start” Screen After Pairing.
When It’s Actually a Hardware Problem
Seek support or an exchange if:
- Two-phone failure after a factory reset: After factory resetting the wearable and forgetting all old listings, two separate updated phones both fail with “Incorrect PIN or passkey” the instant the encrypted handshake begins.
- Screen displays garbled characters or dead radio: The wearable fails to generate a readable pairing prompt or drops power during every Bluetooth exchange.
Never pair through your phone’s Bluetooth settings menu—clear old bonds on both devices, reboot, and confirm the in-app pairing prompt the moment it appears.