11-24-2019 11:24 - edited 11-25-2019 11:28
11-24-2019 11:24 - edited 11-25-2019 11:28
-I have tried the following: restarting my Fitbit, at least 5 times now.
-reinstalled my Fitbit at least 5 times.
-looked at all the possible settings in my Fitbit app, as per suggested here.
-reinstalled the Fitbit app.
I see many are having the exact same issue not receiving notifications. Is Fitbit going to address this issue in an email soon? It's been several months now without a major part of this product working correctly. Thanks!
Moderator edit: updated subject for clarity
11-24-2019 11:41 - edited 11-24-2019 11:44
11-24-2019 11:41 - edited 11-24-2019 11:44
@Jen_5 I think while your request seems totally reasonable we aren't going to see any response from Fitbit on this. There was no warning of the issue so i don't think we should expect an update or a fix.
@KateFitbit and the rest of the fitbit team have all but disappeared from any post regarding notifications.
These community council members apologize in what seems to be an attempt to mitigate the issues, but are unable to solicit a response from actual fitbit employes regarding the issue.
As they are here to advocate for the betterment of Fitbit products and services i haven't seen a post or anything where they stepped in asking fibit to post an update on the issue.
Maybe one of the founding members can chime in and help all of us out. @SunsetRunner @Odyssey13 @wtksk8r
11-24-2019 12:03
11-24-2019 12:03
@thenameless1 Community Council members are not Fitbit employees and have no inside information or insight into what goes on at the company level. @KateFitbit is an employee, but she can only tell us what she is allowed, according to her position within the company. As for our asking Fitbit for an answer, all we can do is wait for them to respond, same as anyone else. Fitbit is aware of these posts, but continuing to ask the same questions or starting multiple threads isn't going to make them come up with a solution any faster. Sometimes all we can do is trust they are working to resolve this for us. Sorry if this isn't what you want to hear, but it's the truth.
11-24-2019
12:31
- last edited on
11-24-2019
16:36
by
EdsonFitbit
11-24-2019
12:31
- last edited on
11-24-2019
16:36
by
EdsonFitbit
@Odyssey13 I believe you are missing the point here and attention needs to be brought to the fact that all anyone is looking for is an update on the issue. Fitbit's silence on the issue is only making matters worse. Even you have to agree that at 2 months after the ios 13 update we all should have had an update on the issue by now.
Now @KateFitbit has the sticky thread posting information about the last iphone update. There is another thread here where she specifically mentions that the team is looking into the frequency of the ios app frequency of location requests. So it appears that she is the one to reference in regards to the notification issue. Is that not true?
I've attached a link below. pertaining to information regarding community council members which i read before my previous post. You guys have the ability to flag posts when they require advanced moderator attention.You also have the option to escalate high impact or emerging issues to customer support. It also appears that you have a private forum allowing you to interact solely with fitbit employees. Again, all i'm saying and what @Jen_5 hinted at is why isn't there an update on the issue and why haven't the community council members advocated for an update in this private forum with fitbit employees?
https://community.fitbit.com/html/assets/CommunityCouncilGuidelines.pdf
Moderator edit: added label
11-24-2019 13:24
11-24-2019 13:24
@thenameless1 it seems you have been given an answer in this post - click to read.
11-24-2019 13:38
11-24-2019 13:38
Hi @Jen_5, @thenameless1 and @Odyssey13. It's great to see you here in the Forums.
@Odyssey13, thanks for stopping by to help our members!
@Jen_5 and @thenameless1, thanks for the steps that you've tried on your own as well for sharing your thoughts about this situation. Fitbit is aware about the notifications issues experienced after updating to iOS 13 and they're working hard to bring a solution. I understand how important is to have this feature working again, while there isn't a time frame for a fix I'd recommend to check this thread for future updates and to try the suggested tips which have worked for others. Your feedback will also be passed along to our team.
Hope to see you around.
11-24-2019 14:14
11-24-2019 14:14
@Odyssey13 Yes we all got an update and I'm thankful for it. Thank you for advocating on my behalf!
I hope there is no hard feelings as all i was doing was advocating for @Jen_5 and the rest of the fitbit community.
As far as cross posting all i did was reply to someone else's post here didn't realize its considered cross posting. @LizzyFitbit and/or @Odyssey13 would it be considered cross posting to provide links to the thread where kate posted the update. As the thread is closed and it's technically the last posted update by fitbit it seem like it would disappear as new users post issues.
Or would it be more acceptable to make it a sticky at the top of the forum until the issue is resolved or another update is provided.
Thank you everyone!
11-24-2019 16:04 - edited 11-24-2019 16:05
11-24-2019 16:04 - edited 11-24-2019 16:05
@thenameless1 anyone in the community has the ability to flag posts. Use the drop down menu by the post.
Capitalizing every letter is usually prohibited on any board, including Fitbit. Using bold, underline or italics is preferred. Please don't tell at us.
11-24-2019 16:46
11-24-2019 16:46
@Rich_Laue Thank you for the feedback. I'll ensure not to use all caps in the future and apologize for using them before. I just read through the link about the community guidelines.
11-25-2019 11:27
11-25-2019 11:27
Thanks for the responses. Too bad the title of my post was edited by a moderator, that is a bit odd. It has been several months and we are not getting what we pay for with alerts for IOS. Just something to consider with your customers, not getting what we pay for.
11-25-2019 11:57
11-25-2019 11:57
Don't feel too bad. I still remember the title of your post before it was edited! I'm only guessing, but i think it was edited because there was some truth to the title.
If it makes you feel any better mine was edited as well (and the same time yours was!). Mine was originally titled "Did Google Kill iOS Notifications??" I got flagged for cross posting in your post, but no explanation on why the title was edited either!
I'm guessing we both applied a little pressure, but i'm not sure why we have to jump thru hoops just to get information in the first place.
I've included the link to the other post where Fitbit commented on the status of the issue if anyone else is interested.
https://community.fitbit.com/t5/iOS-App/Status-on-iOS-notifications/m-p/3910384#M123804