Maybe there is some overnight process that will clean things up, but I haven't found it. I have deleted the two apps in question and they are still there. I suspect that the trigger only fires for Mac App Store apps. Even if you delete the apps in question, these notifications will still fire. ![]() So, none of my reminders are going to fire until at least two days. I can check today and tomorrow, but that's all. I can't tell when these notifications are going to fire. Unfortunately, Apple has made most of the data too opaque. These are the only two apps I know that use the notification system to push ads. To see all scheduled notifications, run the following SQL statement: The one you want for notification spam is at "/db/db". Move into that folder and you'll find some interesting files. Run the following "getconf DARWIN_USER_DIR" and it will return something like: The first thing to do is find the secret directory for these things. EtreCheck, at least the current version, is not going to help with it. Thanks for giving me the kick in the butt I needed to get this fixed. Maybe I should take this opportunity to address the problem. This has been on my EtreCheck to-do list for some time. Come to think of it, you probably shouldn't even restore from backup either as the ads are probably backed up. If you want to purge the notification database without manually editing the database, you must erase the hard drive and reinstall the operating system. ![]() ![]() The only way to fix the problem is to remove the software causing it. I encourage you to write an Apple Bug Report and ask for a solution to allow end-user editing of the notification database or to suppress notifications from apps that are no longer installed. Even if you remove the software in question, the notifications will survive to avenge their fallen app. Apps like this load up the macOS notification system with notifications pushing their products. This is not a problem that can be solved by removing software. If you know of some other solution, I would be glad to hear it. That will just cover up the problem without actually removing the software causing it. I also strenuously disagree with the idea of hacking a database to disable those notifications. That is why I proposed editing the database first. I'm not jumping "straight to erasing the hard drive". Without some reason to suspect otherwise, that would be major overkill. I don't see any reason to jump straight to erasing the hard drive because of this. ![]() Otherwise, this is an erase and reinstall of the operating system situation. There is a way to disable these notifications by using SQLite to edit the notifications database.
0 Comments
Leave a Reply. |