Pixel phones-(Android 15) Recent/Frequent food have their tops cropped off at the top of the screen.

[Phoenix494]

I'm sure 4.29 solved some problems, however it introduced a new problem.  When in the food selection both the Recent and Frequent have their tops cropped off at the top of the screen.  Same thing happens when you want to add calories to the top numeric entry field which is cutoff.  

One has to wonder about all these updates but never getting very far. 

43 days later I finally get this issued resolved for me.  Never mind the myriad of previous problems and those that others are reportedly still exist.  During this long wait there has been no comments from Google, even the Moderators have nothing meaningful to communicate. Google has lost my loyalty and respect for treating customers this way.  I for one will not be renewing my Premium subscription.  I got tired of waiting and I am using Cronometer.  I regret buying the PW3 and my Pixel 9 XL Pro.

Moderator edit:  updated subject for clarity. 

[Ange516]

Me too! It's been over a week! Also my fitbit watch can't scroll in any direction. I wonder if the issues are connected. 

[wyngit]

How is there *no update on this* at all? This should be a simple hotfix? And it's been soooo long?

[RobbyDock]

 

 

Some screenshots on my Xiaomi 14 on Android 15 of the bug, not that I think Google or the Fitbit team care at this point. As you can see the top of the screens are cut off removing several navigation features and leaving you unable create new custom foods.

[dointhebestican]

Your Nov 30th comment is spot on!!! Google phone, and Google app and "NOTHING". Whenever there were glitches in the past, we could go online and input and adjust accordingly on the Fitbit dashboard, that's gone too. While I owe my improved overall better health to the awareness the Fitbit experience has provided, being ignored as all of us have been is quite a slap in the face thus my loyalty to the brand is eroding  quickly.

[mcgrew]

I never had any brand loyalty in the first place. I wanted something to track my sleep and calorie burn, and a year ago Fitbit seemed like the best option for that. When it comes time to replace my fitness tracker I'm much less likely to choose another Fitbit since obviously proper support for the device is not a priority to Google.

[Veldcath]

Honestly, I've already done what someone else suggested earlier and switched to using the Cronometer app for food. Scans faster, better databases for barcodes, much better interface for adding "custom recipes", and it has a supported web-based interface to boot. I connected the Fitbit app to it so it would get activity information for calorie calculations. Now the Fitbit app is just for tracking activity/exercise and sleep. Cronometer (even the free version) is so much better than Fitbit for food. I even converted my change-resistant mother to it after she saw how good the food tracking is, and she doesn't even have the problem covered in this discussion.

[WehlerDealer]

came here looking for an alternative for food logging, thank you!  Waiting on Fitbit to fix their app is a waste of time, and my next tracker won't be one of their devices (especially after they removed the website food logging a few months back).

[olrdvh]

It really is getting ridiculous. I have a P9Pro and have this exact same issue. 

[Zaidj]

Same issue. Thrilled to see it's been known for weeks with no resolution 🙄. I love my Fitbit device, but the support is garbage. I don't know why anyone would pay for premium with this level of support. 

[Darren_F]

@JuanFitbit  Any updates on when we may see a fix for this?? It has been 4 weeks now to fix a basic issue. If nothing else roll back to a known working version of the app. 

[Lizabuncon]

Still having same problem. Uninstalled and reinstalled. Extremely frustrating. 

[Steĉjo]

i received a couple of messages in my email from 

I've received two messages from "Darren_F (Jogger)" in my email this morning.

When I clicked on them I was told "Access Denied".  Does anyone know what's going on?

Steve

[Cyler8]

Yep same issue here. This is pretty ridiculous. 

[JuanFitbit]

Hi everyone. Thank you for your messages and updates. 

Our team is still working on this. We will be updating the thread as soon as we receive further info. 

[Steĉjo]

Thank you, Juan.

It's very frustrating for us all when it appears that we are being ignored.

I've been a Fitbit member for nearly 14 years, so just letting us know that an update is in works helps a lot.

Steve

[Darren_F]

Absolutely it helps!  I'm sure everyone, including myself, was feeling like this is insignificant and we were being ignored. Hopefully this is resolved quickly or, at the very least, rolled back to a stable build. 

[mcgrew]

But "the team is working on it" is the same answer we got 3 weeks ago. Still no ETA for what should be an easy fix.

I'm checking out Cronometer to see if it is a good solution. At least it works properly. Whether I like it is undecided as of yet.

[Nickolai93]

This really should be an emergency fix at this point. I was told by Google Support the first week that this happened, it would be resolved by the Nov 22 update. Guess what wasn't resolved???

[Phoenix494]

This is the same answer that was given 3 weeks ago.  Is that the Best information we can get after all the frustration Google has given us? It does nothing to appease the user base.   We are still left in the dark about a crippled app and when it will be resolved.  Maybe Google could address us directly.

[PoppyTrees]

Same issue here, Pixel 8 Pro. Just got charged my first Fitbit premium payment after the trial and this isn't making me want to continue.