homebrew-cask: XtraFinder error after cask install and launch

General troubleshooting steps

I have checked the instructions for reporting bugs (or making requests) before opening the issue.
- None of the templates was appropriate for my issue, or I’m not sure.
I ran brew update-reset && brew update and retried my command.
I ran brew doctor, fixed as many issues as possible and retried my command.
I understand that if I ignore these instructions, my issue may be closed without review.

Description of issue

After installing xtrafinder by brew cask zap xtrafinder brew cask install xtrafinder the app shows an error on every launch from then on. It says

Warning, XtraFinder.app was modified. For security reason, re-download XtraFinder from official web page.

I noticed it installs to /usr/local/Caskroom/xtrafinder/0.27/XtraFinder.app instead of /Applications/XtraFinder.app

After moving it to the correct location

mv /usr/local/Caskroom/xtrafinder/0.27/XtraFinder.app /Applications/XtraFinder.app

the error goes away.

Would be nice to see a fix installing it to the correct location by default.

Thanks in advance

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 16 (16 by maintainers)

Most upvoted comments

but in my eyes running the command with --verbose --debug doesn`t make sense and neither does brew cask doctor

All due respect, that’s not your call to make. There’s a reason we ask for that information; it’s for our eyes, not yours. If you’re submitting a bug, we need to know everything that happened.

the cask is clearly installed in the wrong location

No, it is not. The cask was unpackaged to the correct location, but the app isn’t what matters, the pkg is. That is the one that is failing.

Do you have the same issue installing the pkg manually?

I can confirm on a clean Sierra VM that it indeed fails when trying to install manually. We need to either:

Make the cask stage_only and add a caveat about SIP (linking to their instructions).
Make the cask depends_on under 10.11.

vitorgalvao on Sep 19, 2017

I would like it better if it would not work before 10.11

There’s no reason to do that.

but if it would work automatically on the latest macos versions instead of installing manually.

We can’t do that. It’s impossible, due to SIP.

This is not a negotiation of what we want to do; it’s an explanation of what can be done.

Make the cask depends_on under 10.11.

I’d favour this option.

I do as well. I really don’t want to tell users to disable security features.

vitorgalvao on Sep 19, 2017