Numbers in steps tile are not displayed correctly

[Unity11]

Here recently my steps have been showing incorrect with the last digit on a different row when it used to show all in the same row. Is there an issue going on with the fitbit app? Anyone else having this issue

Moderator edit: Subject for clarity

[RicardoFitbit · Accepted solution]

Welcome to the Community Forums @Unity11.

Thanks for bringing this to my attention, seems odd that your steps are being displayed in such way. To better assist you with this, can you please let me know when was the first time you experienced this and how many times since then? Which Android mobile device are you using? If you haven't already done so, please try the following steps:

1. Force quit the Fitbit app.
2. Uninstall the app from your mobile device.
3. Make sure that the Android version is up to date.
4. Reboot your mobile device.
5. Reinstall the Fitbit app.
6. Login using your account credentials.
7. Let me know if the issue persists.

Let me know if you have any additional questions.

[Unity11]

Hello there, I follow the steps that you provided however the steps are still displaying incorrectly. This has been going on for two weeks now.

Sent from Yahoo Mail on Android

[Unity11]

Hello there, I follow the steps that you provided however the steps are still displaying incorrectly. This has been going on for two weeks now. I have the Galaxy Note 10 device. 

[wdadli1]

I am having the exact same problem. I have a Pixel 3a XL. I will try the recommended steps to correct it, even though I see it did not work for Unity11.

[LLoga]

Tried also... doesn't work. Stays with last digit on next line. Just started when I updated my Fitbit. 😟

[LLoga]

This didn't work for me ...I tried 3x.

I have a Google pixel. Alta Fitbit...and it just happened today Jan 31 2020

[LLoga]

I have the same phone... didn't work for me. 

[wdadli1]

So how do we get Fitbit to fix the problem?

Sent from my Pixel 3aXL

[wdadli1]

This"fix"did not work for me either. We need a fix that works.

[wdadli1]

This fix didn't seem to work for most of us. What next?