09-28-2018 09:59 - edited 09-28-2018 10:00
09-28-2018 09:59 - edited 09-28-2018 10:00
Fitbit Update 9/28/2018: We are aware that some users on iOS 12 are unable to log weight using decimal points or foods using a comma. Our team is currently investigating. As a workaround, you can add your weight and food through Fitbit.com and it should populate correctly. Thanks for your reports!
Actively managing your weight? Find accountability buddies on the Manage Weight board
Answered! Go to the Best Answer.
08-13-2019 15:53
08-13-2019 15:53
Closing this thread as we are no longer receiving reports and can not reproduce. Please start a new thread if you experience an issue similar to this. Thank you.
Actively managing your weight? Find accountability buddies on the Manage Weight board
09-19-2018
09:34
- last edited on
09-20-2018
04:36
by
MarcoGFitbit
09-19-2018
09:34
- last edited on
09-20-2018
04:36
by
MarcoGFitbit
Hi
installed IOS 12 yesterday.
since then i can not enter food with a comma in the qty (1,5 grams ).
the app only lets me sellect a point but its not accepting that.
Moderator Edit: Clarified Subject.
09-19-2018 13:15
09-19-2018 13:15
I'm having the same problem with my weight input... When I try to input the number with the decimal separator on the numeric pop-up it gives me the message " Invalid weight " and I have no alternatives... I have looked at all my setting (iPhone and Fitbit) and cannot find any place where I can define the decimal separator... With the iOS 11 I did not have this problem...
09-19-2018 23:27
09-19-2018 23:27
Same for entering weight!
09-20-2018 04:39
09-20-2018 04:39
Hello @laburante and @HermanFrederik, thanks for joining the Fitbit Community, it's great to have you on board. It's nice to see you too @SunsetRunner, I hope you're doing well.
I appreciate you have taken the time to report this situation. Tell me, have you updated the Fitbit app to its latest version? Have you restarted your phone or logged out / in from the Fitbit app? If so, I would like to ask you for a screenshot of the error you're getting when trying to add decimals to your weight with a dot or a comma, this will be very helpful for me to check this further.
Thanks for your patience and understanding, I'll be waiting to hear from you.
09-20-2018 09:37
09-20-2018 09:37
Hi
see screenshots ... i can only sellect a DOT ( food and weight log )
the comma you see in weight is my PREVIOUS entered weight. I can only sellect a dot on the entry
09-20-2018 12:41
09-20-2018 12:41
@MarcoGFitbitthanks for your prompt answer... Here are the answer's to your request:
1. Yes... I am on the last version of the app...2. I turned off the phone and also logged out and back in to the app, but still the same problem...
3. Following the screen shots...
Note the "dot" in the keyboard, which the app seems to not accept...
The error msg...
This final one is the last input which I entered with no issues, prior to installing iOS 12...
Hope this helps solve the issue...
09-20-2018 22:54
09-20-2018 22:54
Hi there!
I’m having the exact same issue with the same conditions as above. Any updates on this?
09-23-2018 00:47 - edited 09-25-2018 01:48
09-23-2018 00:47 - edited 09-25-2018 01:48
when entering weight manually, the decimal sign is “.” on the number pad but “,” in the text. illegal entry, sets number to zero.
app should accept both signs as separator
Moderator Edit: Clarified Subject.
09-23-2018 08:42
09-23-2018 08:42
Same here
09-24-2018 05:35
09-24-2018 05:35
Hello @rolvmarius, I hope you're doing well, it's nice to see you around the Fitbit Community.
I appreciate your participation in the Forums and for sharing your experience and feedback with us. Would it be possible for you to reply to me with a screenshot of what you're able to see when trying to log in your weight and a screenshot of the error you're receiving? This will be very helpful for me to check this further.
Thanks for your patience and understanding, I'll be waiting to hear from you.
09-24-2018 07:29
09-24-2018 07:29
Hi... Is this the same issue we brought up on 09-19 ( Unable to log weight with decimals after updating to iOS 12.) ?
Any news on this?
09-24-2018 15:37
09-24-2018 15:37
Any news on this issue?
Version 2.79 has the same bug!
09-25-2018 07:53
09-25-2018 07:53
Hello @laburante and @Gabarra, I hope you're doing well, it's nice to see you around the Fitbit Community.
I appreciate you have shared your experience about this issue. At this moment I have already forwarded this information to our team so they can take a better look at this situation. Once I have more information to share with you, I'll make sure to post it here in the official Forums. In the meantime, I would like to ask you for a screenshot of the error you're getting so I can forward it as well.
Thanks for your patience and understanding, I'll be waiting to hear from you.
09-25-2018 08:31
09-25-2018 08:31
Following the two screenshots... 1st when inputing weight and 2nd the error msg...
09-25-2018 08:35
09-25-2018 08:35
Hello @SunsetRunner and @laburante, I hope you're doing well, thanks for taking the time to reply and provide the screenshots requested, I really appreciate it. It's great to have you on board @Aleite and @loevestein, thanks for joining the conversation!
I appreciate you have taken the time to report this to me. At this moment I would like to suggest you to update the Fitbit app to its latest version (2.79) that we have just released. Then, try to enter a new weight log with decimals and let me know if you're still experiencing this issue.
Thanks for your patience and understanding, give it a try and let me know the outcome.
09-25-2018 08:46
09-25-2018 08:46
09-25-2018 08:57
09-25-2018 08:57
Hi again
Same issue (2.79).
just a point sellectable and fitbit app does not accept.
i have DUTCH language/region settings for my iphone X ( Nederlands ). This was the same on IOS11 but did not have this issue on that version. Just on IOS 12
regards
09-25-2018 09:39
09-25-2018 09:39
@MarcoGFitbit the screen shots I sent correspond to the 2.79 (787) version of FitBit, which I installed early this morning... I have seen other users also mentioning that the problem has not gone away with the new release...
09-25-2018 09:50