Apple has had disruptive issues related to notification infrastructure in macOS since at least macOS 12 aka Monterey. Affected are both the individual notifications themselves – also known as messages or notifications – as well as the notification center, the Notification Center, which can be folded out on the right side of the screen. There is no improvement in macOS 13 aka Ventura: on the contrary, according to user reports, the problems have even worsened up to the current version 13.2.
Notifications and Beach Balls
At first glance, the bugs appear to be more of a cosmetic nature, but they are particularly annoying in their daily work for users who receive many notifications. It often happens that a notification simply remains on the screen, either directly visible at the top right or in the notification center. In both cases, clicking the close button (X) fails. In some cases, entire notification blocks, which Apple automatically folds, remain in the notification center as if frozen or suddenly reappear after closing.
It also happens that notifications are not delivered at all or are only “silent” – although neither a focus mode has been activated nor any other manual muting. On macOS 13, users also experience that sending a notification from an app causes the sending app to get stuck – with a “spinning beachball” and high CPU usage in the activity monitor. There have also been reports of notifications being delivered too late, with delays of several minutes.
Deterioration in Ventura
While in macOS 12 aka Monterey notifications are a problem that don’t want to go away, the reliability of the overall system has deteriorated with macOS 13. Whether Apple continues to work on improvements is unknown. The hope that macOS 13.2 could remedy the situation was not fulfilled, the beta of macOS 13.3 is currently being prepared.
Recently there was a fresh bug in connection with the notifications: When the computer started, the system suddenly spit out the information that background processes that had already been deactivated had been activated again. However, the problem apparently has more to do with the behavior of startup objects or LaunchAgents than with a bug in the notification center itself.
(bsc)
To home page
