Google Fit: Troubleshooting Connection and Data Issues
- Updated
Occasionally, expected Google Fit data does not display for users in MyDataHelps or within a MyDataHelps Designer participant's chart on the Google Fit tab. This article provides an overview of the Google Fit sync behavior and a series of steps to diagnose data synchronization issues.
Table of Contents
Sync Behavior Overview
Triggering a Sync
Google Fit data is automatically sent to MyDataHelps Designer in the background and does not require the device to be unlocked. A sync may be triggered when a Dashboard tab is loaded or refreshed, provided that MyDataHelps has not sent Google Fit data to MyDataHelps Designer recently.
Background Sync Frequency
A scheduled job polls for new Google Fit data every four hours. This schedule is only approximate, as Android defers and batches background work to reduce battery usage.
Diagnosing Google Fit Sync Issues for a Participant
Google Fit data flows through several different applications before it appears in MyDataHelps Designer:
Wearable > Third Party App > Google Fit > MyDataHelps App > MyDataHelps Designer
A misconfiguration or connection issue at any stage can prevent data from appearing in MyDataHelps Designer. The troubleshooting steps below should aid in determining where the issue is occurring and how it may be resolved.
Check Google Fit Configuration in MyDataHelps
Confirm that the participant has enabled the data type in question:
- Have the participant open the Google Fit configuration screen in MyDataHelps. Note that this screen is only available in the MyDataHelps Android app.
- Confirm that the data type you are investigating is enabled.
- Ask the participant when the data type was last shared. This information appears directly under the data type name. It will say “No data available” if it was never synchronized with MyDataHelps Designer.
Check Google Fit Connected Apps
Unlike Apple Health, which stores data entirely on a participant’s device, Google Fit is a cloud service. It is possible that MyDataHelps and the third-party app are connected to different Google accounts.
Have the participant review their connected apps and confirm that both MyDataHelps and the third-party app are connected to the same Google account. Open the Settings app on their device, then navigate to:
Google > Settings for Google apps > Google Fit > Connected apps and devices
It is possible to configure multiple Google accounts on a single device. Check all of the accounts listed on this screen and confirm that both apps are connected to the same account. Any app that is not listed is not connected to Google Fit.
If the third-party app (Heart Rate Monitor in the example screenshot above) is not listed, the participant will need to connect the third-party app to Google Fit:
- Confirm that the current version supports Google Fit.
- Consult any help or documentation provided by the developer for further guidance.
If MyDataHelps is not listed:
- Have the participant return to the MyDataHelps app and open the Google Fit configuration screen.
- If no data types are enabled:
- Enable all desired data types.
- When prompted to select a Google account, choose the same one the third-party app is connected to.
- If one or more data types are enabled:
- Disable all enabled data types.
- Enable all desired data types.
- When prompted to select a Google account, choose the same one the third-party app is connected to.
If MyDataHelps is connected to the wrong Google account:
- Disconnect MyDataHelps from Google Fit.
- Follow the steps above ("If MyDataHelps is not listed:") now that MyDataHelps is no longer associated with the incorrect account.
If both apps are connected to the same Google account, please see below (check for data in Google Fit).
Check for Data in Google Fit
Have the participant open the Google Fit app and check for the data in question:
- If the data does not exist in Google Fit, there may be an issue with the third-party app.
- If the data does exist in Google Fit, and it’s at least 30 minutes old, and MyDataHelps is connected to the correct Google account, there may be a synchronization issue.
Please contact us if the steps outlined above do not resolve your issue.
Was this article helpful?