12-27-2017 09:33
12-27-2017 09:33
I am located in the US, I have the Fitbit charge 2, using the most current version of the fitbit app (v.2.63) and running on Android 7.0 on a Samsung galaxy S7 Edge phone. I just bought my husband the exact same model fitbit as mine and and he installed the app yesterday. His app appears to be slightly different from mine, he has an icon for community and I do not. Knight hat has also been giving me trouble syncing lately. We are both using the app up on the exact same type of device running on the same version of Android. I checked the Google Play Store and there are no updates available for my Fitbit app. I have also tried restarting my phone, force stopping the app, clearing the cache and even uninstalling and reinstalling the app but none of this has helped. How can I get this newer or different version of the app that seems to work better for my husband?
12-27-2017 11:13
12-27-2017 11:13
Open the app, then account and advanced settings. Check witch location your Fitbit account use. Seems that the community service only works if you use United states (and maybe some other countries) as your location.
12-27-2017 11:15
12-27-2017 11:15
12-27-2017 11:21
12-27-2017 11:21
The app changes on my phone if I choose US as my location, seems Fitbit won't let me be a part of the community when I use Norway.
Do you use automatic location or not?
12-27-2017 11:29
12-27-2017 11:29
12-27-2017 11:37 - edited 12-27-2017 11:44
12-27-2017 11:37 - edited 12-27-2017 11:44
Tried to switch it off and choose US manually? Then sync your device.
12-27-2017 12:44
12-27-2017 12:44
Yes I have switched automatic location off synced turned it back on synced and it didn't fix it. I also tried changing my country to something else and then syncing and then changing back to the US and syncing but that didn't help either.
12-27-2017 14:20
12-27-2017 14:20
Sorry, running out of options here. Only thing I would suggest is logging out of the app, and clear out the app memory. Then log in to see if it does the trick. Best of luck
12-27-2017 14:53
12-27-2017 14:53
No apologies necessary, I appreciate all the help and suggestions you have offered. I just tried this suggestion and sadly it did not fix it for me. I searched the forum for similar issues and found someone with the same issue and someone responded that we are just seeing an older version of the app and until the new view is fully rolled out there's nothing you can do about it. But that post was a few months old so I'm not sure if that's really the solution for me.