iOS 14 notification bug has not been fixed yet — it has been six months

iOS 14 notification bug has not been fixed yet — it has been six months

iOS 14.5 may be released soon, but iOS 14 is still plagued with major bugs. And there seems to be no solution in sight

The problem is a notification bug first discovered last September. The problem is preventing users from seeing messages and calls, and is serious enough to warrant a 90-page thread in Apple support. However, there is no reliable fix.

What is interesting about this issue is that it is not preventing calls or incoming messages; some Apple Watch owners have noticed that they receive notifications on their watches while their iPhones show nothing.

The support thread is full of various fixes from people who say the iOS 14 fix works on their iPhones. Some say that rebooting will get the notifications to show up, while others say that turning Bluetooth off is the best solution.

Some users have found that unpairing and re-pairing their Apple Watch has solved the problem. Some users also believe that iOS 14 randomly activates the "Hide Alerts" feature to prevent notification of incoming phone calls and messages.

If you are having this problem and want to explore all avenues, this might be worth a try. If you head into the message conversation and long press on the name or number at the top, you can see the status of the option to hide the alert.

But these fixes don't work for everyone, which means there could be a more serious problem here. And given the comments over the past few days, it appears that this problem is still ongoing.

Adrian Kingsley-Hughes of ZDent personally walked several users through the fixes on their iPhones, to their frustration when the fixes don't seem to work. One person he spoke to even went to the extreme of buying a brand new iPhone.

It's certainly an odd situation, not least because the bug has lived through several updates to iOS 14. It may be fixed in iOS 14.5, but there is no way to say for sure. Unless Apple announces that a fix for this issue will be included in the next update.

However, there is no obvious answer to the question of why this problem has persisted for so long; hopefully we won't have to wait until iOS 15

for a solution.

Categories