09-19-2016 13:22 - edited 10-04-2016 16:59
09-19-2016 13:22 - edited 10-04-2016 16:59
Fitbit Update 10/04/2016: Hi everyone -- The issue where app users were unable to manually enter distance of less than a mile should be resolved with updating to the Fitbit app for Android, version 2.35.
I am closing this thread as this issue has been confirmed resolved.
If you're still experiencing issues with manually logging a distance of less than 1 mile on Android 2.35 or above, please create a new post and refer to this thread as well. Thank you!
Fitbit Update 09/19/2016: Some Community members have reported that they're unable to manually log activities under 1 mile in distance in the Android app, version 2.33.
Our team is aware of this issue and is currently working to get this resolved. I will be sharing updates with everyone about this here when I hear something new.
In the meantime, try this workaround for logging something under a mile:
Let me know if that works for you. Thank you!
09-11-2016 14:56 - edited 09-12-2016 17:05
09-11-2016 14:56 - edited 09-12-2016 17:05
With the latest update (2.33), I am not able to enter a distance of less than 1 mile. I can enter decimal distance, but only if it is over 1 mile. So as an example, I cannot enter 0.34 miles as a distance.
This is super frustrating because I manually log my warm-up and cooldown walks, and those are always less than 1 mile.
09-14-2016 12:17
09-14-2016 12:17
I have the same issue, there is a work around although kind of a pain. Enter the mileage with a digit before the decimal place and then go back and remove the digit before the decimal place, i.e. for 0.5 miles enter 1.5 miles but before you save it go back and delete the 1 and the app will let you save the 0.5 portion. It is a pain but it works.
09-14-2016 12:32
09-14-2016 12:32
Thank you so much for the workaround steps. This is helpful!
It's super weird to take this functionality away, and I hope it's just a bug that will be fixed in a future update rather than a conscious decision to remove a feature.
09-14-2016 14:56
09-14-2016 14:56
@brinstar & @xcat01 welcome to the forums! @xcat01 Thanks a million for the workaround! Thanks for bringing this up to my attention. Have you guys tried logging out, force quitting the app and then logging back in again? Just out of curiosity, were you able to do it before the update? Do let me know. I also suggest trying to clean your Android mobile devices' cache. To do so, please do the following:
1. Log out from Fitbit app
2. Go to phone settings
3. Tap Fitbit app
4. Tap clear Cache & Clear Data
5. Finally close the app and then log back into the Fitbit app
Let me know if it helps. Keep me posted!
Did you receive the answer you were looking for? Mark the post as an accepted solution! 🙂
09-14-2016 18:03
09-14-2016 18:03
09-14-2016 22:37
09-14-2016 22:37
09-19-2016 08:05
09-19-2016 08:05
Hi there @Lauram1331 welcome aboard to our Community and good to see you around @xcat01. Thank you for bring this issue to our attention. Note this is the way the app works since at the moment does not allow to enter decimals, but a good workaround for this is like @xcat01 recommended.
I know its not the best solution, but I will pass this information to our teams. Also as an additional note, do not reinstall the app as this may present other issues; although is not common I don't recommend to do this unless is require due to this troubleshoot only works for specific scenarios.
Thank you for your patience and let me know if you have more questions. I will keep you posted if I have more updates about this.
"Great things are done by a series of small things brought together.” What's Cooking?
09-22-2016 01:43
09-22-2016 01:43
09-23-2016 10:53
09-23-2016 10:53
@TheresaLP I totally agree that it is a nuisance. I appreciate you taking the time to report this. I have made our Android team aware of this and they've confirmed that they are working on resolving the issue. Until further notice, continue to use the workaround that you've been using. Keep an eye on this post as I will make sure to update it once the issue has been resolved. Thanks again!
09-24-2016 02:15
09-24-2016 02:15
09-27-2016 11:17
09-27-2016 11:17
@DebsG Thank you for confirming that this is also affecting your swimming logged activities. I will keep you posted here with updates as to when this will be resolved.
In the meantime, please continue using your workaround of logging as yards or use our online Dashboard activity log page. Sorry for the inconvenience, but I hope to have an update soon.
Thank you for your continued patience and time.
10-04-2016 13:44
10-04-2016 13:44
Fitbit Update 10/04/2016: Hi everyone -- The issue where app users were unable to manually enter distance of less than a mile should be resolved with updating to the Fitbit app for Android, version 2.35.
Please test it and confirm with me if that holds true. Thanks in advance!
10-04-2016 15:45
10-04-2016 15:45
10-04-2016 16:55
10-04-2016 16:55
@TheresaLP Thank you so much for taking the time to confirm the fix and update me. I greatly appreciate the follow-up.
10-04-2016 16:59
10-04-2016 16:59
Fitbit Update 10/04/2016: I am closing this thread as this issue has been confirmed resolved.
If you're still experiencing issues with manually logging a distance of less than 1 mile on Android 2.35 or above, please create a new post and refer to this thread as well. Thank you!