jasxchange.blogg.se

However, since the deleted old value is not pushed to mySugr Logbook (in other words, Health does not tell Logbook that records have been deleted or updated), now BOTH values appear.

This new value is pushed into mySugr Logbook. This new value shows up in Health (and the old value from step 1 is gone). Behind the scenes, MyFitnessPal does NOT push another (new) value to Health, but instead, it deletes the previously saved value and stores a NEW value, which is the sum of both food items. Now you enter your additional food item into MyFitnessPal. It's immediately pushed to Health.įrom Health it's pushed into mySugr Logbook. You enter a carb value into MyFitnessPal. I'll do my best to describe why, but please let me know if you have questions along the way.Īpple HealthKit doesn't currently provide a good way of knowing when an existing value in HealthKit has been modified or deleted. And it's really not the fault of MyFitnessPal, but rather that of how Apple Health handles this data. Synchronizing carb info between MyFitnessPal & mySugr Logbook via Apple Health is a bit messy right now. So why do we not recognize data you've worked so hard to save into MyFitnessPal? It would seem like the perfect marriage, right? We also know that it connects to Health for easier tracking of exercise and other things. Whether you're a newbie and only track calories and carbs, or if you are hard-core and track macros, MyFitnessPal seems like a great solution for helping you get on track and stay motivated in your awesome efforts.

We know, MyFitnessPal is a great app for tracking your meals, exercise, and weight.