Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Lifetime distance section showing up twice (in Android app)

Replies are disabled for this topic. Start a new one or visit our Help Center.

In the app, on the Account/badges tab, I see Top Badges, Daily Steps, Daily Climb, Lifetime Distance, Lifetime Climb, Fitforgood, Weight Goal, Lifetime Distance (again), and Challenge.

 

Also, it's getting kinda congested on this tab. Sections should start out collapsed, and open when one taps them (IMHO).

 

Oddly, I do not see the Challenges at https://www.fitbit.com/badges/all

 

Thank for reading, Eric

--- Two wrongs don't make a right, but three lefts do.
Flex (Christmas 2014), ChargeHR (Christmas 2015). Wife is using the Flex now! Nope, that Flex has died. Alta ordered 12/15/16 as Flex replacement. So far, she likes it. Nope, alta battery only lasts 2 days, started at 7. Support contacted 12/7/17. Hope warranty covers it.
Best Answer
0 Votes
7 REPLIES 7

Hey there, @EricJRW! It is nice to see you around. It is weird that you see Lifetime distance twice, can you please share a screenshot of this? 

 

Thanks so much for sharing your feedback and experience regarding the Fitbit App, I'll make sure to share this with my team. Keep in mind that the challenges feature is only available on the App and not on the online dashboard, this is why you do not see it there. Cat Tongue

 

 

Solange | Community Moderator, Fitbit

Best Answer

Im experiencing the same issue. I just got the New Zealand badge, but I got the Great Barrier Reef badge (=more km than Nez Zealand) months ago!

Best Answer

Hey, @Tvdp! Welcome, welcome! Cat Very Happy Hmmm..this is very weird. To get the Great Barrier Reef badge you should do either 1600 miles, or 2574 km. Maybe this was the confusion? 

 

If you are sure that you received it months ago and before the New Zealand, can you provide me a screenshot where it shows the date please?

 

I'll be around. 

Solange | Community Moderator, Fitbit

Best Answer
0 Votes
Hi Solange,


Thanks for your reply!


Unfortunately I can't, as the dates marked in the achievements do make sense. I am however a 100% sure that I received the notification for the New Zealand badge just recently. So maybe it is only the notification that is wrong? Maybe it gets sent a second time when it gets triggered by something.


However, it is still weird that there are 2 sections for Lifetime Distance and Lifetime Climb, each containing different badges.

I included screenshots in attachment.


Kind regards,

Thomas
Best Answer
0 Votes

@EricJRW wrote:

In the app, on the Account/badges tab, I see Top Badges, Daily Steps, Daily Climb, Lifetime Distance, Lifetime Climb, Fitforgood, Weight Goal, Lifetime Distance (again), and Challenge.

 

 


For me I see Top Badges (which shows a steps in a day badge and a lifetime miles badge), Weight Goal (I don't have a Fitbit that measures stairs), Challenge (which shows badges for different challenges that I've done), Lifetime Distance (which shows the PREVIOUS lifetime miles badge - from before the one I got in Top Badges) and Challenge (again - although this one has a different adventure than the other Challenge section).

Best Answer
0 Votes

Hey, @Tvdp! Thanks for joining us! Man Tongue Hmmm...could be that only the notification was wrong then. It should not happen again. If it does please let me know and we will further investigate. 

 

The climbing and distance sections are divided because one is for achieving your steps and distance goals and the other one for achieving the floors climbed. The screenshots are not included in your post. 

 

Please make sure to follow this process to include them correctly. I'll be around. 🙂

 

Hey, thanks for your help, you are awesome! @ChristyDoodle

Solange | Community Moderator, Fitbit

Best Answer
0 Votes

I replied by email so the attachments probably didn't get included in my forum post. I get the difference between climbing and distance of course, but both of these sections were appearing twice. I have just switched to another phone and the problem is not occurring on this one. The phone on which I had the bug was a Moto G2. May be worth looking into if more users report this problem.

Best Answer
0 Votes