Home > Tips and Tricks

Twitter false persistent notification alert on iOS: How to Fix

In this guide, we will show you the steps to fix Twitter’s false persistent notification alert issue on iOS devices. This microblogging and social networking site has been quite a lot in the news lately, mostly due to the elements of uncertainty surrounding the CEO and the decisions taken by its board of directors.

However, keeping all that stuff aside, the service is once again in the news, and again not for the reason that it would have liked. As of now, various iPhone users have voiced their concern that they are getting false persistent notification alerts on the iOS Twitter app. In reality, there are no new notifications, but the app is constantly bugging them with a prompt that they have received a notification.

Likewise, even the app icon shows a notification counter. What is even more infuriating is the fact that these false alerts don’t go away even if you launch the app and re-check all the notifications. With that said, there does exist a nifty workaround that might help you resolve this bug. So without further ado, let’s check it out.

How to Fix Twitter’s false persistent notification alert on iOS

Twitter false persistent notification alert on iOS

  1. To begin with, launch Twitter from a non-Apple device, such as an Android device or Windows PC.
  2. Then log in to the same account that is currently showing false alerts.
  3. After that, head over to its notification section and refresh it once. That’s it.
  4. Now launch the Twitter app on your iPhone and it should fix Twitter’s false persistent notification alert issue on iOS.

The only caveat with this workaround is the fact that its respite is temporary in nature. As a result, this issue might re-appear after a few hours. When that happens, you will have to carry out the above-listed fix once again. While this in no way is the most viable approach to rectify this issue, but as of now, this is our only way out.

As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly.


Share: