MyFitnessPal entries are being multiplied on Fitbit

[ErickFitbit]

Fitbit Update 10/29/2015: As this issue has now been resolved, I am closing the thread from further discussion.

Thank you to everyone who reported this issue and for your patience while we worked to get it resolved. Happy to know that your food logs are back to normal! 

---

Fitbit Update 10/25/2015

Syncing food from MFP to Fitbit is now back to normal. Thank you again for everybody's patience while this problem was being worked out.

---

Fitbit Update 10/22/2015: MyFitnessPal is aware and has added this to their known issues page. Fitbit and MyFitnessPal are closely working together to get this issue resolved ASAP.

In the meantime, a workaround to try is to manually delete the duplicate entries from your Fitbit Food Log. In order to delete duplicate entries, do the following:

1. Go to your Fitbit Food Log.
2. Hover over the duplicate food item, an "X" should appear on the left-hand side.
3. Click the "X" to delete the entry (illustrated below).

Another option is to unlink your MyFitnessPal account from your Fitbit account and checking your calories on MFP until the multiplying issue is fully resolved! 

Thank you for your continued patience as we work alongside MFP to get this issue resolved! 

---

Fitbit Update 10/21/2015: Some users have reported that their MyFitnessPal food log entries are being multiplied on their Fitbit Food Log.

Sorry for the inconvenience, but Fitbit and MyFitnessPal are both aware of the issue. We are currently working on resolving this issue with MFP's help. MyFitnessPal has also posted an update here as well. I will share updates here with everyone when I find out more! Thank you for your patience! 

[Adrienne_T]

I'm having the same problem as well. Tried clearing data on both apps but still didn't work. I hope this is just a one off glitch that would resolve itself

[Gregg429]

Same hear. I just deleted the MFP entries and re-synced and even more breakfast was added. I'm up to a 6000+ calorie breakfast

[Darth_H]

same here for all meals of the day synced from MFP. looks like a bug. tried manually deleting, but they just came back.

[SunsetRunner]

Hi @Gregg429 @Darth_H

Have moved this thread from the Charge HR to the Third-Party Integrations section to increase the chance of getting a solution.

Wishing a wonderful evening

[melsm]

Same here as well, I've tried deleting, but every time it sync's it just keeps adding more.

[A_AVL]

I just deleted a whole lot of entries from the MyFitnessPal because they were brought over, and over, and over, and it was something like 4 or 5 additional entries per meal.  It was more than doubling my caloric intake.

While I am sorry to see that this is happening to others, I am glad that I am not the only one, and am wondering if FitBit has corrected this yet?

Similar to TracyV125 my meals came over with different totals, so I deleted all but the one that was correct.

I have also linked/unlinked/linked my accounts, but it isn't stopping the problem.

A

[MBRMK]

Having the same problem.  I manually deleted entries, but fear (based on other comments) that it reaccumulate the next time it syncs.

Any chance someone at fitbit can help with this?

[A_AVL]

Regarding the trouble shooting on if it is APP related or website related.
All of my MFP input on food is input through the website, I don't even have the app on the phone, so I have the same problem, and am using the web version, on both MFP and the FB.

A

[A_AVL]

Aaand, this problem started in NOVEMBER of LAST YEAR
So here I sit, wondering if FB and MFP ever took care of it or have a solution, since I just removed 4 breakfasts, 3 snacks, and a few lunches from today's entries.

HELOOOOOO FB

I read both threads, and am on this thread because a FB moderator directed to watch this thread for the solution.  I don't see a solution, I do however, have the problem.

I have now had the FB Charge HR for going on 2 months, and I got it to TRACK things.  That is can't be used with the Apps it says it CAN be used with is a bit of a let down.

Please publish when you expect this problem to be resolved.

Regards

A

[honeybee2607]

I am having the same exact issue. I've tested it out, deleting things from MFP and readding them, and the number of calories it says I'm eating on Fitbit just keeps skyrocketing.

[Neofolis]

Hi, first post, sorry if I'm meant to do an introduction or something first.

My problem is not necessarily Charge HR related, but it is not specifically related to any one of the FitBit apps either, so I'm posting here, purely because I use an HR.

So, every day before today I record my food in MyFitnessPal and, whichever FitBit app I'm using syncs with that data, so everything is updated on the In/Out graph.  Today, however, rather than the usual import each meal as a summary of the total values, it's importing each item individually, plus combinations of items, plus the total.  As a result, I have recorded 1406 calories on MyFitnessPal so far today, but FitBit is showing that I have consumed 4041 calories.

I have no way of knowing whether the problem is with FitBit's interpretation of the data or with the data MyFitnessPal is exporting.  Just wondered if anyone else is experiencing similar issues or has done in the past and whether they were resolved by any action that I can take.

I haven't changed any settings or anything I'm doing for this to occur, so I assume it's related to a change that either FitBit or MyFitnessPal have made.

[424a57]

I noticed the same thing.  It appears as though every time I add a new item to a meal in MFP, the summary is added to Fitbit, so that every entry is cumulative (logrithmic?) rather than the new total becoming the new "meal summary" in Fitbit.

[424a57]

---

@Sonja351 wrote:
Can I change it ?

---

As a work-around, I've just been deleting each previous entry, leaving only the correct last entry, from the Fitbit Activity Log Food tab.

[abbabanana]

The fitbit app is erroneously adding breakfast calories (200+) that aren't showing up on myfitness. I went into my fitness and deleted all my food and resynced: MyFitness shows 0 cal for the day, Fitbit shows almost 600 for the day. I've double checked to make sure I'm on the right day in MyFitness.

Thanks!

[CandiGirl1968]

I am having the same issue. It seems to be a FitBit/MFP sync issue as the website has the same issue as the app. FitBit did an update today, and I suspect this threw things into disarray.

[Neofolis]

Sorry, I just created a thread about the same thing before I found this.  Guess we'll have to wait for FitBit to sort it out.

[Petalouda8]

My FitBit Flex is synced with MyFitnessPal, and my steps are syncing up correctly.  But the calories eaten have gone completely out of whack today.

I've eaten 1,191 calories.  And my FitBit app is showing me as having eaten 13,657!! I don't think it's humany possible to eat that many calories in only 6 hours (which is how long I've been awake ).

And what's worse is that every "fix" I've tried (closing out of both apps, then re-opening, shutting off my iPhone competely, then turning it back on, disconnecting the two apps online, then re-connecting), only adds more calories. And I'm talking thousands of calories with each "fix"! 

Looking at the details on my FitBit app, it seems that it's adding every breakfast, lunch & dinner I've eaten over the last 3 weeks.

I've sent a help-email, but I thought I'd ask in the community as well. Is anyone else having this problem?  Is it just a bug that is being worked on?

Any help/response would be greatly appreciated.

Thanks!

anna

[Jinkyjenks]

This has happened to me also today. I've disconnected MFP and connected it again buts it's still telling me I have eaten 3500 calories! I wonder if there is a way to clear the data on the Fitbit? I really like using MFP but not if it's giving wrong information.

[Jinkyjenks]

I'm having the same problem too. It must be a glitch but it's annoying as the two apps normally work so well together. I too have disconnected and connected again with no joy.

[Neofolis]

I noticed after posting this that there is another thread about it.  Apparently FitBit did an update today, so they must have screwed up a bit of code in the update.  Hopefully they'll do a hotfix to sort it out quickly.