Bug Report: Weight log tile has finicky behavior

[jaina8851]

My Fitbit app was saying that my "start date" for my weight goal was March 13, even though I had actually started March 8. (No idea why this happened, it started randomly and I didn't know there was a way to fix it until just now.)

I changed the date, and suddenly my goal weight changed from 132 to 59.9 lb. 

I couldn't change the weight back without restarting the "goal" process, which of course changed the "start date" to today's date.

When I changed the start date to March 8 again, it changed the log entry for March 8 from 142 lb, my start weight, to today's weight (136.2lb) and the progress indicator on the app's dashboard showed that I had no weight loss.

I changed the March 8 log entry back to 142 lb, but the progress indicator still said '-- lb lost' instead of showing my progress over the last month.

I managed to get it fixed by logging onto the website dashboard and manually entering the 142 lb on the dashboard tile there. 

I am not sure which part of the process has the bug, or whether there are many here, but this was frustratingly difficult to resolve.

[RobertoME]

Hello @jaina8851, good to see you around the Fitbit Community. Usually this happens if you update your starting weight.

When you change the starting weight on your app, it will change the weight lost you have so far since due to the history of the weight entries. The way to fix this on the app is to change back the starting weight date to the original date you had and enter your weight goal once again. You can do this from the Account tab > Nutrition & body.

I saw you were able to fix this through the online Dashboard, however if the issue happen again, take a look here for additional advice. Here you' will find a post from @jordy1990 which has been very helpful for this situations.

See you around and let me know if you have additional questions.

[jaina8851]

I didn't update my starting weight. Did you read my repro steps? I didn't change anything at first except the starting DATE, because it arbitrarily picked a date four days after I started recording. It then did a bizarre collection of steps, as I described in detail in my post. The app still isn't telling me the right thing. These are bugs. The post you cited doesn't describe what I was seeing at all.