help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

iOS sync frequency

‎09-09-2020 08:37

‎09-09-2020 08:37

Hi,

 

Project I'm working on seems to be experiencing an iOS-only issue. 

 

We're using the web API to pull in Fitbit data into our own app.  However it appears that the iOS version of the Fitbit app does not appear to reliably sync the wearable data with Fitbit. For example, there is sometimes a delay between waking up and sleep and heart rate data then appearing in our app via the Fitbit APIs.  Sometimes the data doesn't appear at all and only works after opening the iOS FitBit app, forcing it to sync.  This same behaviour does not seem to affect Android. 

 

So the questions I have are:

  • Does anyone know why this problem occurs?
  • Does the iOS App auto sync data between the app and wearable?
  • How often does the auto sync take place?
  • Is there anything that can prevent auto sync of the data or require manual sync by opening up app?
  • Is there a delay between the sleep data / heart rate data syncing and then appearing in the API?

Any help greatly appreciated. 

Best Answer
0 Votes
1 REPLY 1

‎09-10-2020 01:48

‎09-10-2020 01:48

More information, in case it helps:

 

Situation:

  • Our App and Fitbit App in memory
  • WiFi connected
  • Bluetooth turned on
  • Fitbit set within iphone settings to refresh in background
  • Time awake on day 1 and day 2: hours
  • Frequency with which we’re taking data from Fitbit APIs - every 5 mins

 

Result Day 1

  • All data in appeared in our app – as expected

 

Result Day 2

  • Nothing but steps data in our app 

 

Questions

  1. Is sync frequency dependent on device or age of device?
  2. Is sync frequency dependent on whether on a wifi or mobile data connection?
  3. Is sync frequency dependent how active you are?
  4. Is sync frequency dependent on phone os  / device type / some other user controllable configuration?
  5. Is sync frequency dependent on their being a min amount of data to sync to make it worth while?
  6. How long after data is synced from the phone to the Fitbit servers is the data available via the Fitbit Apis?
  7. What is the lag between when someone wakes up and when their sleep and resting heart rate data becomes available?
  8. Why would steps data be available but not heart and sleep?
  9. Any recommendations on how to overcome the above?
  10. Are there instructions we could include within our app to make sure the user do all they have to do to get it working?
Best Answer
0 Votes