The @fitbit app is now showing up in #HealthConnect but no app-side activation, so I'm not seeing it read/write in Health Connect's side. Similar to @MyFitnessPal
and #HealthSync.
The only ones actually doing R/W are #GoogleFit, #SamsungHealth, #SleepForAndroid, & #HealthMate.
and #HealthSync.
The only ones actually doing R/W are #GoogleFit, #SamsungHealth, #SleepForAndroid, & #HealthMate.
@fitbit @MyFitnessPal Based on my tests, even if you turn-on all permissions on #HealthConnect's side; if the detected app itself does not have its own HC activation setting, then there will be no R/W at all.
It's why #MyFitnessPal, #Fitbit, #HealthSync are not working.
It's why #MyFitnessPal, #Fitbit, #HealthSync are not working.
Look at #GoogleFit, #SleepForAndroid, #SamsungHealth, and #HealthMate. They all have an app-side activation, it's why we can see Read/Write to #HealthConnect from those 4 apps.
Oh, to make @Withings' #HealthMate work with #HealthConnect, you have to install the old version with Health Connect activation. If you install the current version, they removed their app-side activation, turning-on features on HC's side is an incomplete process.
#HealthConect integration is a two-step process: (1) app-side activation; and (2) HC-side permissions.
Based on the 7 apps shown in the screengrab above, that's how it currently works. Turning-on the permissions on the side of Health Connect is not enough to make it work.
Based on the 7 apps shown in the screengrab above, that's how it currently works. Turning-on the permissions on the side of Health Connect is not enough to make it work.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
