Fitbit data not syncing on Android: the real cause (and the fix)

When Fitbit data isn't showing up in Android apps, the fix is almost always a missing permission in Health Connect, not a Fitbit problem. I've seen this situation dozens of times: the Fitbit app works perfectly, the wearable syncs, but a third-party app sees nothing. It's not Fitbit's fault. Fitbit already did its part.

Why it happens: how data exchange works on Android

On Android, Fitbit doesn't share data directly with other apps. It drops data into Health Connect, a local database on your phone that acts as an intermediary. Think of Health Connect like a shared mailbox: Fitbit drops your steps, heart rate, and sleep data inside. Other apps can read that mail, but only if they have a key to open the mailbox. If an app doesn't have that explicit permission, it sees nothing. And Fitbit has no way of knowing the mail wasn't picked up.

The mechanism is intentional: Health Connect is designed to give users granular control over who reads what. But that granularity creates an extra configuration point that most people don't know exists. Result: the user sees an app that 'doesn't work', when really it's simply missing a read permission.

The step-by-step fix

1. Open the Fitbit app on your phone. Go to Account Settings (profile icon, top left) → App Settings → Health Connect. Here you'll find the toggle to enable writing data to Health Connect. If it's off, enable it. This step is missing from almost every guide online.
2. Open Health Connect (find it in Android Settings → Privacy → Health Connect, or search 'Health Connect' in the app drawer). Go to App permissions.
3. Find the app that isn't receiving Fitbit data (e.g. FitMesh Sync, or whatever app you're using). Open it and verify that the data types you need (steps, heart rate, sleep, etc.) are enabled for Read.
4. Back in the main App permissions list, also find Fitbit. Verify that Fitbit has Write permission for those data types. Without Fitbit writing, there's nothing to read.
5. If all permissions were already active but data still isn't showing, try revoking and re-enabling the read permission in the destination app. On some devices, refreshing permissions unblocks a stuck initialization.

Common gotchas that trip people up

• •Health Connect does NOT retroactively sync data. If you authorize an app today, it will only see Fitbit data written from that moment onwards. Last month's data, last year's data: it will never see it via Health Connect. This is a design choice, not a bug. If you need historical data, you must export it directly from the Fitbit app (Account Settings → Export Account Data).
• •Writing to Health Connect is not active by default in Fitbit. Unlike Samsung Health (which on many devices asks you to configure Health Connect during setup), Fitbit requires an explicit manual activation in the app's settings section. If you've never touched it, it's almost certainly off.
• •The Fitbit-Google relationship is complicated. Google acquired Fitbit in 2021. Some older Fitbit models write to Google Fit but not Health Connect, depending on firmware version. If you have an older Fitbit and don't see the Health Connect option in the app, verify that firmware is up to date. Alternatively, it may simply not be supported.
• •The third-party app's read permission is separate from Fitbit's write permission. Many people think: 'I authorized Fitbit, so the other app must see the data.' No: the two permissions are completely independent. Fitbit writes, the third-party app reads, but reading requires an explicit permission granted to the third-party app. Both must be active.

In summary

• •Fitbit writes data to Health Connect only if you enable it manually: Fitbit app → Settings → Health Connect → enable writing.
• •The app you want to use needs its own read permission in Health Connect, separate and independent from Fitbit's permission.
• •Health Connect never syncs past data: only from the moment of authorization onwards.
• •Some older Fitbit models write to Google Fit, not Health Connect. Update the firmware or check your model's compatibility.