Google Play Services Error in Fitbit: Fixing the “Keeps Stopping” Loop on Wear OS

If your Wear OS watch keeps flashing a “Google Play services keeps stopping” popup every time you open Fitbit—or while Fitbit tries to sync in the background—you are dealing with a broken app-to-system handshake. Fitbit on Wear OS depends on Google Play Services for account sign-in, GPS location, and health data syncing. Clearing the cache on both apps and updating your watch services usually breaks the loop without erasing your watch.

Quick Answer

To stop the “Google Play services keeps stopping” loop in Fitbit on Wear OS, force-restart your watch to clear stuck popups, then open Watch Settings > Apps to clear the cache for both Fitbit and Google Play services. Next, open the Play Store directly on your watch to update all system and Fitbit packages.

What Is Actually Happening?

On Wear OS smartwatches like the Google Pixel Watch, Fitbit does not talk to Google’s servers directly. Instead, it routes your Google Account token, location requests, and Health Connect sync calls through Google Play services running quietly in the background.

When Google Play services updates silently in the background while Fitbit is still running an older build—or when a cached authentication token becomes corrupted—Fitbit sends a request that Play Services cannot understand. Play Services crashes, Wear OS automatically restarts it a second later, Fitbit retries the exact same call, and the error popup locks you into an endless loop.

What Can Cause the Loop?

  • Version mismatch between watch and phone: Google Play services updated on your phone or watch, while the Fitbit watch app stayed behind on an older version.
  • Corrupted cache after an OS or Play System update: Stale temporary files inside Google Play services or Fitbit break background sync handshakes.
  • Revoked background permissions or Google Account glitches: Missing Body Sensors, Physical Activity, or Nearby Devices permissions—or an unfinished Fitbit-to-Google migration—trigger repeated crashes.
  • Health Connect sync conflict on Android: Broken read/write permissions between Fitbit and Health Connect on your paired phone can bounce errors back to your watch.

What to Do: Breaking the Loop Step by Step

Step 1: Force-Restart the Watch to Regain Screen Control

If the popup appears every two seconds and blocks you from tapping anything:

  1. Press and hold the Crown and Side button together (or hold the Power/Crown button on single-button watches) for about 15 to 20 seconds until the watch shuts off and shows the boot logo.
  2. Release the buttons and wait for the watch to finish booting.
  3. If the popup returns immediately, wait a few seconds and tap App info directly on the crash dialog if that button appears, or swipe down quickly into Settings.

Step 2: Clear Cache on Both Fitbit and Google Play Services (Watch Side)

Clearing Cache is safe—it only deletes temporary files and will not erase your watch or remove your payment cards. (Do not tap “Clear all data” on Google Play services yet, as that resets Google Wallet cards and watch-to-phone pairing keys.)

  1. On your watch, open Settings > Apps & notifications > App info (or Settings > Apps > App list).
  2. Scroll to Fitbit (and Fitbit Exercise or Fitbit Today if listed separately), tap Storage & cache (or App info > Storage), and tap Clear cache.
  3. Go back to the full app list, scroll to the bottom and tap System apps (if hidden behind a toggle), then find Google Play services.
  4. Tap Storage & cache > Clear cache, then restart the watch once more.

Step 3: Update Everything in the Watch Play Store

Even if your phone’s Play Store shows no updates, your watch maintains its own separate Play Store queue:

  1. Make sure your watch is connected to Wi-Fi (or paired closely to your phone) and sitting on its charger if battery is low.
  2. Open the Google Play Store app directly on your watch screen.
  3. Scroll down to Manage apps and tap Update all so Fitbit, Google Play services, and Wear OS system components are all running matching builds.

Step 4: Fix Cache and Permissions on Your Paired Phone

If the watch still throws Play Services errors when opening Fitbit, the mismatch often sits on the Android phone side:

  1. On your phone, open Settings > Apps > See all apps.
  2. Tap Google Play services > Storage & cache > Clear cache.
  3. Open Fitbit > Storage & cache > Clear cache.
  4. Tap Fitbit > Permissions and verify Location, Nearby devices, Physical activity, and Notifications are all allowed.
  5. Open the Fitbit app on your phone and confirm you are signed in cleanly with your migrated Google Account. If you see account or sync blocks, review Fitbit “Syncing Unavailable” – The 2026 Google Account Migration Fix.

What to Check If the Error Still Loops

Check Health Connect and Play Services Communication

If Fitbit crashes right as it attempts to log a workout or sync daily steps to your phone, your phone’s middleware permissions may be stuck. Resetting permissions via How to Reset the “Health Connect” Permission Hub on Android 16 often stops the crash cycle immediately.

If you also see numeric Play Services error alerts or broader sync stalls, check Wear OS “Error 2001”: Fixing Google Play Services Communication or Troubleshooting Auto-Sync Failures on the Google Pixel Watch 4.

Uninstall and Reinstall Fitbit Updates (Or Clear Fitbit Storage)

On the watch under App info > Fitbit, tap Clear storage / Clear data (or uninstall updates in the watch Play Store and reinstall Fitbit). You will just need to sign back into Fitbit through your phone companion app afterward.

When You Should Reset the Watch

If Play Services crashes endlessly across every app—or comes paired with System UI crashes—a broken system update may have corrupted the shared Android framework. Check Wear OS 6: Fixing the “System UI Has Stopped” Persistent Error first, and if nothing clears it, perform a watch reset from your phone’s watch companion app (any workouts already synced to your Fitbit cloud account stay safe).

Bottom Line

A “Google Play services keeps stopping” loop inside Fitbit is almost always caused by corrupted temporary cache or mismatched app versions between Fitbit and Play Services on your watch. Force-reboot to regain control, clear the cache on both apps, and run Update all inside the watch’s own Play Store before resorting to a full watch reset.