Home > Apple > iPhone

Blank/Empty Notifications reported after iOS 16.2 Update

Many users are reportedly getting blank/empty notifications on their iPhones after updating to iOS 16.2. The latest iOS update has bought a slew of intriguing features to the fore. These include the likes of the Freeform app, Advanced Data Protection, App Store, and changes to the Always on Display. On the flip side though, a few bugs have also managed to creep in, with AOD, App Store, and ADP going through a rough patch.

Blank/Empty Notifications on iOS 16.2

Blank Empty Notifications on iOS 16.2

Now, there has been another unfortunate entry to this long list of issues. Numerous users have voiced their concern that they are getting blank/empty notifications on their iPhones after updating to iOS 16.2. When they tap on that notification to expand it then they could view the content of that notification but if they tap on those notifications again to collapse it, then it tends to go into hiding.

How to Fix Blank/Empty Notifications on iOS 16.2

Blank Notifications iOS 16.2

As of now, the only workaround that is spelling out success for “some” users involves disabling the Always on Display. So do give it a try using the below-listed instructions and check if it works in your favor or not.

  1. Head over to the Settings menu on your device.
  2. Then go to Display & Brightness > Always On.
  3. Finally, enable the toggle next to it to disable it.

That’s it. These were the steps to fix the blank/empty notifications issue on iPhones after updating to iOS 16.2. 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. In the meantime, the aforementioned workaround is your best bet.


Share:
  • ExhibitA

    So it went from numerous to only a handful of people getting the blank notification? Lol.. well I’m getting it and it’s annoying as hell. I wonder if it has anything to do with disabling notifications for the always on which they added in 16.2.. I’ll test this theory later.