Weight graphs not loading

[DeinGesicht]

After latest update(2.91),when I click on one month, 3 months, even the one week graph within the weight tile, it constantly shows the "spinning wheel" before maybe loading. I've uninstalled, cleared cache, all the usual. No luck. See screenshot. Anyone else have the same trouble? Fed up with these updates. 

[LanuzaFitbit]

Hello @DeinGesicht.

Thanks for sharing those details, that screens, and listing all of the steps that you have tried to get this situation resolved.

I'd like to ask if you if this is happening with any other tile for section of the app or only with weight? In addition to that, when you say 'maybe loading', how often does it not load? When it doesn't, do you get some sort of error message? 

Look forward to your reply! Let me know if there is anything else that I can help you with.

[DeinGesicht]

apologies - I never had any notifications of replies here.  This only happens with the weight graphs and only on the app.  All other tiles and graphs, OK; weight graphs lag, 20 seconds and upwards, from the last two updates of the android app.  This was never a problem beforehand.  Minor, but annoying.  Even the one-week weight graph lags on loading, and it's not as though it has that much data to load.

[LanuzaFitbit]

Hello @DeinGesicht.

I apologize for my delayed response. Thanks for bringing this up and sharing those details on waht is going on.

The first thing I'd like to recommend is that you verify that you are using the latest version of the app. You can click here to read more about it.

To be sure I get the situation correctly, the graphs lag but they do eventually load, correct?

I'll be around if you have any questions.

[DeinGesicht]

Hi, definitely the latest version of the app and this problem has only arisen in the last two updates. The usual fixes (log in/out/delete app/reinstall) haven't worked 

[LanuzaFitbit]

Hello @DeinGesicht.

Thanks for letting me know about this and that the update hasn't resolved the situation.\

In this case I'd like to ask you some questions:

• Are they not loading at all or do they take a long time?
• What phone are you using?
• What Android version is that phone running?

In the meantime, maybe you could try accessing those details through a different phone. If you do, let me know if it does load or not.

I look forward to your reply.

[DeinGesicht]

Hi, not currently able to try with another phone .I use xperia xz (I believe it's supported now) on android 8. The graphs all take 20-30 seconds to load. The latest update of the app hasn't fixed it either. 

[LanuzaFitbit]

Hello @DeinGesicht.

Thanks for reaching back.

I'd like to ask you to check on the phone settings what app version you are running at the moment and share a screenshot in here.

Look forward to your reply.

[DeinGesicht]

I think that's what you're looking for? However, until this bug is fixed, I've been using an earlier version of the app which DOESN'T have the same problem . This weight graph problem has only happened with the last 2 or 3 versions. 

[DeinGesicht]

Version 2.90 has no problem at all, so I'll be going back to that in the meantime. 

[LanuzaFitbit]

Hello @DeinGesicht.

Thanks for sharing that screenshot and your findings with version 2.90.

I'll be sure to bring this up to the rest of the team so that I can be looked into. As soon as we have any details on the matter we will be sure to let everyone know.

Let me know if you have any further questions.

[DeinGesicht]

Has the fault been passed along to the developers? It's still there with the latest update from last week. Have any other users reported it. It is annoying not being able to update because of it. 

[LanuzaFitbit]

Hello @DeinGesicht.

Thanks for sharing your thoughts on the matter.

Our team is aware of the situation and is looking into the situation. At this moment we do not have any details on the matter but we will be sure to post about it as soon as we have any updates.

Let me know if there are any other questions I can help you with.

[DeinGesicht]

Just reporting that there's still no fix for this as of the latest update.