Thumbnail of Facebook logo on inKin social fitness
Thumbnail of Twitter logo on inKin social fitness
Thumbnail of Google+ logo on inKin social fitness
Thumbnail of Instagram logo on inKin social fitness
Image of Pinterest logo on inKin Social Fitness
Log in Sign up
Image of New Pop on inKin Social Fitness
inKin Social Fitness Platform
install
inKin Social Fitness Platform
install
By Jeff Lawrence
5 months ago
Steps from google fit disappearing at ~7 days of age
By Jeff Lawrence 5 months ago
My steps beyond 7 or 8 days are slowly dropping, they still show the same in google fit but in inkin they are dropping daily. It was noticed by others in a contest as others saw my totals dropping.
Comparing day by day anything over ~ a week is not correct, for instance on 6/28 - Google fit is currently (and Inkin was) showing 10027 - but as of today it is in the 700s. The 27'th is showing 19k in Google fit (and was correct in inkin) but as of today shows ~9k. All the totals have been fine over the last couple days (I joined on the 27'th) so it may have something to do with that as well.
Replies (4)
By rob
4 months ago
By rob 4 months ago
Jeff, the synchronization period with Google fit changed. Now it's 3 days. Google was changing old data by itself.
I advise you to reconnect your device, to work correctly with Inkin.
By Jeff Lawrence
4 months ago
By Jeff Lawrence 4 months ago
Any potential fix for this? In another competition now where it continues to happen on the sliding window. 7/11 for example was correct but now shows 105 steps (google fit ( the source) still shows 3,136). I assume like last time- soon 7/12 will drop and my total will continue to go backwards.
By Jeff Lawrence
5 months ago
By Jeff Lawrence 5 months ago
It continues - The 29'th went down last night, seems some sort of rolling window. Oddly the days don't go down to zero there are steps remaining but they are significantly reduced.
By rob
5 months ago
By rob 5 months ago
THx for your report Jeff.
By Jeff Lawrence
5 months ago
By Jeff Lawrence 5 months ago
If you are tracking this bug - see update on the drop again last night on data from 6/29
feedback