Nutrition info not displaying correctly

[lwilliams35351]

Within the last few days I have noticed that the nutrition information of foods is displaying incorrectly and is cutting off the top lines of the information. 

I am using the most recent version of the app (4.48.fitbit-mobile) on my pixel 7 pro.

I have attempted all the usual suggested actions such as clearing the cache and storage and uninstalling then reinstalling the app but nothing resolved my issue. 

Any help would be appreciated as my primary use of this app is to track my caloric intake and macronutrients. 

Thanks

 

[greenfroggy1]

Same. It's been cutting off the nutritional information for a few weeks. Hoped with so many having the issue it would be fixed by now, but it isn't. 

[pjpjr]

Over 2 days and I am the only one who is reporting using an Android version lower than v15.  Anyone else?  This could be significant information for Support.

[Sparker18]

I don't think so. Replies have reflected a pretty wide range of phones and versions. 

[pjpjr]

@Sparker18 The range can be wide, however the minimum and maximum are still significant. Especially as new functionality is introduced to support newer features and old functionality is deprecated.

[sibhusky]

Android 16

[pjpjr]

@sibhusky Thanks and again more evidence that the issue occurs at Android 15 and above.

For those curious about the "why", my experience has been it centers around new functionality and support of prior versions. This is not a criticism of the OS or application developers.  This has been one of the places I have observed unforeseen, new bugs being introduced into products.  Also worth noting that the product developers want to support older versions as far back as possible.  I cannot remember the last time I upgraded my phone due to anything other than my phone's maximum level of OS no longer being supported due to OS functionality and vulnerability.

[pjpjr]

I see the Topic that Android App version 4.49 was released.

Anyone experiencing this Nutrition info issue tested with 4.49?

[sibhusky]

I have 4.49 and it's not fixed.  Got that 2 days ago.

[pjpjr]

I am still NOT experiencing this issue with:
Android

App

Charge 6

[Randelions]

I just updated and issue is still there. Android 16

[Mjpaintrain]

Android version 15

Fitbit app 4.49

[nleprohn]

I am also having same problem. 

Inspire 3-android 15 fitbit ver. 4.49

[dgacor]

Thank you for all these interesting details

Here the answer I have received today from fitbit-support_at_google.com "...

Thank you for your patience. We understand your concerns. However, we cannot tell you how soon this issue will be resolved. Please keep the app updated.

Knowing I have started my complaint on July 20th and they were completely lost (they asked me to delete all apps in my phone)

Now on your observation about Android version , Android v15 has been released on October 2024 , so weird that is only causing these issues now....Still your observation is quite relevant and no one of Fitbit company is reacting 

Even more , I´d used their own AI (Google Gemini) to find answers about how is possible a Google company having such poor reactivity and told me that is possible that there are Silos inside the company between Google & Fitibit (anyone can try it by his own , to see if get the same)

Finally I forced my solution moving to older version of Fitbit app (prior ~July 20th when the issue started)  manualy and deactivating any automatic update BUT keeping my Android 15 version as given by the system...and trying to move away of this brand as soon I find my required functionalities in an alternative brand (need to combine both fitness data + nutrition data , probably will need to use separate apps)

Good luck everyone , I keep following the case

[pjpjr]

@dgacor Thank you so much for sharing your update regarding this situation and your well wishes for those impacted!

Regarding "Now on your observation about Android version , Android v15 has been released on October 2024 , so weird that is only causing these issues now....Still your observation is quite relevant and no one of Fitbit company is reacting"

I know of know company who ever wants to isolate, or lose, users.  For new features and to mitigate vulnerabilities, an OS (really any software) introduces new functionality in existing APIs/modules, or introduces new APIs/modules.  All of this exists in an agile environment, meaning the company wants to deliver functionality the largest user population wants, as soon as possible.  This translates to the OS always having this goal of supporting the oldest and newest version of everything below it and above it, in it's stack, or supporting both extremes.  When one combines all of this, one can create a part of the software which delivers the desired functionality today.  Yet when one adds the next new functionality to that part, it can reveal things one did not have to previously consider, which can result in defects/bugs.

In my experience, with this goal of supporting the extremes, the defect can appear near either extreme; i.e. older versions or newer versions.  So in this case, that part has introduced defects we see in newer versions of the OS.  From the replies here, this defect appears to only impact versions greater than Android version 14; near that newer extreme.

[dgacor]

Thank you

I am using Inspire 3- Android 15