07-05-2019
13:38
- last edited on
07-07-2019
07:18
by
LanuzaFitbit
07-05-2019
13:38
- last edited on
07-07-2019
07:18
by
LanuzaFitbit
So I've had my versa lite for months now. No problems getting all my data synced. But recently (without me making any changes) my text notifications are not coming through on the versa lite.
Tried trouble shooting. Turning off notifications, restarting & turning back on.
Tried running messages as a secondary program.
Tried turning on & off blue tooth.
All others come to the versa lite; phone calls, Facebook messages, emails, and my blood sugar app.
I'm stuck.
Have the galaxy s8 phone.
Moderator edit: Clarified subject
Best Answer
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Hello @amazzeratti.
Thanks for bringing this up and sharing all of those details of what you have tried.
I'd like to better understand what is going on so I'd like to ask you a couple of questions:
In the meantime, I'd like to recommend that you try turning notifications off from any other apps (Facebook messages, email, etc.) for a moment and check if that helps so that the text notifications come through.
Let me know if there are any other questions on the matter.
Best AnswerMy charge 3 is not receiving incoming text messages, but displays my outgoing texts. Never had a problem until after most recent update, have tried everything! I have a Samsung S9, and no other apps are set to send notifications. Only my message app and calls.
Best AnswerI get Facebook message notifications if I set that as much primary messaging app.
I do not get any notifications for my regular text messages either run as primary messaging option. Or when Facebook messages are primary & messages are added to "other" notifications. Which of my other notifications like emails I get no problem.
This problem started about a week and a half ago.
I am not aware of any updates to my phone or the Fitbit.
As for your work around idea, I've already tried.
Thanks!
I finally got a straight answer from support:
"I'd like to bring to your attention that this is a known issue that has just been reported to us and our engineering team is already aware of and actively working on a fix."
Looks like we wait for 3.2
Best Answer