Helper Tools Installation Failed

Got a problem with Viscosity or need help? Ask here!


User avatar
Posts: 2175
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Thu Jan 13, 2022 10:12 pm
Hi CanuckMSP,

Please try using the following command - the previous command won't check beyond the outer basic layer of the bundle:
Code: Select all
codesign --verify --deep --strict --verbose=2 /path/to/
The bundling method will still work fine with modern versions of macOS. In this instance I'd say something is modifying the Viscosity app bundle prior to it being included in the installer.

James Bekkema
Viscosity Developer



Posts: 6
Joined: Tue Nov 14, 2017 5:56 am

Post by CanuckMSP » Fri Jan 14, 2022 2:01 am
Fantastic, that helped narrow down the issue. Thank you!

I store all my project files on OneDrive, which apparently modifies files as part of the sync. What a nuisance.

A fresh copy from my /Applications folder passed, but as soon as it was put into OneDrive it would fail.
Code: Select all resource fork, Finder information, or similar detritus not allowed
In subcomponent: /Users/work/Library/CloudStorage/OneDrive/Packages Projects/Viscosity/Viscosity/


Posts: 6
Joined: Tue Nov 14, 2017 5:56 am

Post by CanuckMSP » Wed Apr 13, 2022 3:56 am
Unfortunately, this has come up again with our users only when installing an updated version of Viscosity.

It seems something is happening to the .app between when it's packaged in the PKG and when it's executed on the system.

If I extract the .app from the .pkg with Pacifist, it passes just fine. If I install it with our MDM tool (Addigy), it then fails the codesign and the user gets the error message (and we get a ticket).

Ostensibly, all that's being run against the PKG file is:
/usr/sbin/installer -pkg "/Library/Addigy/ansible/packages/Viscosity (1.10.1)/Viscosity_Installer_CLIENT_1.10.1.pkg" -target /

I'm not sure why there would be any difference between an update and a clean installation though.
13 posts Page 2 of 2