Water log: always empty response

[Hielko]

With the water log request: /foods/log/water/date/......json

the response is always empty, while there is water data logged in the Fitbit app for the dates requested:

{

    "summary": {

        "water": 0.0

    },

    "water": []

}

We see this on our test devices and with users.

[EntropicMaximum]

I have a similiar issue. Issue with water logging - Fitbit Community

[GordonFitbit]

Thank you for reporting this problem.   It appears to be any water log recorded through the mobile app is not being returned through the Get Water Log endpoint.  If I create a water log using the Create Water Log, the values are returned by the Get Water Log endpoint.

I'm reporting this issue to engineering and will update this post when I get more information.

[Hielko]

Hi @GordonFitbit thanks for your analysis. This matches our experience: users who record their water intake with Fitbit complain that our app can't read the water intake data. We don't have complaints from users who push water intake data from our app to Fitbit.

I'm looking forward to a fix for this issue.

[GordonFitbit · Accepted solution]

Engineering rolled back the change. The water log recordings in the mobile app are not visible through the Get Water Log endpoint.

[bickster]

Hi @GordonFitbit Any update on this? Our users are still experiencing this issue with the water REST API. 

I keep seeing this in the forum but I'm not understand what it means?

Engineering rolled back the change. The water log recordings in the mobile app are not visible through the Get Water Log endpoint.

[Hielko]

Hi @bickster Are you sure? We receive the water log records created with the Fitbit app without problems after August 7.

[GordonFitbit]

@bickster 

I had a typo in my comment.  It should be "Engineering rolled back the change. The water log recordings in the mobile app are now visible through the Get Water Log endpoint."

I have tested this again today, and the water log created in the mobile app is being returned by the Get Water Log endpoint.  

[bickster]

Thanks for the reply. Our users are still still seeing an empty JSON response when calling Get Water Log from the API endpoint. Would sending users log files to you help?

[GordonFitbit]

Hi @bickster 

Yes, you can send log files to me.  Please send them through Issue Tracker so the information remains private.  

Thanks!

Gordon

[bickster]

We got a handful of log files from users yesterday. There's not much in them so I didn't create a ticket. The request is successful but the json doc is empty.  This has never occurred in the past. I don't know if there's not a water entry or if there is an issue. The original issue could be fixed but now we are seeing this issue.

@GordonFitbit To be more specific. We are using the  Get Nutrition Time Series by Date Range - GET https://api.fitbit.com/1/user/GGNJL9/foods/log/water/date/date1/date2.json

The response should look like this: https://dev.fitbit.com/build/reference/web-api/nutrition-timeseries/get-nutrition-timeseries-by-date...

Example response on the web page. Can't paste the json.

What we are seeing is:

{
}

[bickster]

Here's an image using the swagger UI at https://dev.fitbit.com/build/reference/web-api/explore/#/Nutrition%20Time%20Series/getFoodsByDateRan...

As you can see the json doc is empty.

For this date range the user (me) has water entries on eight thirteen but none on the other days in the date range.

[GordonFitbit]

@bickster 

Thanks for clarifying you are using the Nutrition Time Series endpoint.  I'm able to reproduce the issue you are experiencing with these endpoints.   On 8/17, you said you are still having the problem with Get Water Log endpoint after we rolled back the change.  I cannot reproduce the issue with Get Water Log.  Can you clarify if you are not receiving data with Get Water Log or did you mean the Nutrition Time Series endpoints?

Gordon

[bickster]

I meant the Nutrition Time Series endpoints. We don't use the Get Water Log for daily water entries. Sorry for the confusion. 

Chris

[bickster]

@GordonFitbit Do you have a timeline on when this will be fixed?

[bickster]

@GordonFitbit Just wanted to follow up with you on this issues. Our users are still experiencing this issue? Any timeline you can share on when this will be reolved?

Thanks.

[bickster]

@GordonFitbit 

Any update on when this will be fixed? Thanks.

[bickster]

@GordonFitbit Any word? I'm starting to get more and more emails from our users with how frustrated they are right now?!?!

[GordonFitbit]

Hi @bickster 

I don't have a solution yet, but I can tell you the engineering team has begun working on the problem.

[GordonFitbit]

Hi @bickster , @Hielko and @EntropicMaximum 

i've been working with engineering today to investigate this problem, and it seems the problem is fixed for me.   I was able to log new water data in the mobile app and it is coming through the Web API.  Also, the water I logged several months ago which I used to report the bug to engineering, is returned through the Web API.

The only thing that has changed in my environment is the Fitbit mobile app version.  There have been several updates/bug fixes released over the past month.  The mobile app version I have install is Fitbit mobile app v. 4.51 on iOS.

Would you please have your users update the Fitbit mobile app to the latest version, sync the app, and have you try calling the Get Nutrition Time Series endpoints again.

Let me know what your results are.