REQ: remove Hazel from the supported applications

[Gompje]

Support for this was spotty at best but since v5 it's a complete disaster.

I have added an ignore rule in the config; but I think support should be better removed. It took me a while to track down the issue was with the sym linking.

what happens? welllll ... this:

1. endless trail mode loop, even when registered. Fun fact: the app sees the license file, but still a fff popup everytime and limited features
2. rules disappear at random
3. folders disappear, reappear
4. sometimes rules load, most times not
5. hazel crashes multiple times on rebooting

No not all at once and not every time

Anyway I had enough and was ready to ditch Hazel until I read this last response:
https://www.noodlesoft.com/forums/viewtopic.php?f=4&t=11615&p=28576&hilit=mackup#p28576

luckily this user did document his fix and helped me 😄 so no I am kinda paying it forward?

[monkey555]

I can confirm.

I was using Hazel just fine for several weeks and then after a reboot all of my drives and rules were gone. I contacted Hazel's support and after trying everything they could think of they told me to create a new admin account, which I did.

I moved everything over to the new account, reinstalled mackup, and after my first backup everything disappeared in Hazel after reboot.

It was while attempting to repair permissions on the Hazel settings directory in ~Library/Application Support/Hazel that I noticed all of the symbolic links.

Almost every symbolic link was related to a problem.

For instance, Bartender 5 kept showing an onboarding splash screen every restart even though the "Don't show this again" was checked.

Transmit forgot my license key every time it restarted.

CleanShot also lost the license key on every restart.

I did an uninstall on mackup and all of the problems ended. Hazel restored all of its settings, Bartender 5 quit showing a splash scrren, and Transmit and CleanShot both started up and didn't ask me a license key.

[spuder]

Are you running OSX Sonoma?

The lates 10.14.1 update has strict sandboxing enforced which breaks mackup completely. This may be a OSX problem, not a hazel problem

Additional information in this thread

#1924

You can confirm by opening the console app and looking for a log message like this

deny(1) file-read-data