Page 1 of 1

Bundling Viscosity on MacOS High Sierra does not work

Posted: Fri Feb 09, 2018 9:38 pm
by JdZ
I was trying to build a new install package following this guide:
https://www.sparklabs.com/support/kb/ar ... ences-mac/

I installed Packages, downloaded your viscosity_installer.tgz template installer package and of course downloaded the latest version of Viscosity.

I followed all the steps, first installed Viscosity, then added Settings (including only a license key), and also added 1 connection to the template folders

I open up the project file in Packages and Build, and I get no errors everything seems to work just fine.

Now the problem:
When I test this new package, (first uninstall the existing Viscosity version) and then run the new install package I just created everything seems to work just fine as well, I get no errors at all.. .but Viscosity.app is never placed in the Application folder.

It seems like the connection included in the package is added just fine to the corresponding Library folder etc, but the actual application is never added to the application folder.

As far as I can tell this is happening because I am creating this package on a computer running MacOS: High Sierra (10.13.3)
I have build these packages before (for instance for Viscosity 1.7.5) but at that point it was on a Mac running El Capitain, I don't have access to that anymore.

Right now I'm trying to build a package with viscosity 1.7.6 and on a Mac running High Sierra and it just will not work no matter what I try it seems.

Could it possibly be that Apple changed things up again with their latest updates that require a change of your package template, or am I missing something obvious? :)

Re: Bundling Viscosity on MacOS High Sierra does not work

Posted: Mon Feb 12, 2018 9:04 am
by James
Hi JdZ,

Is Viscosity already present on the machine you’re testing the installer on? If so, and Viscosity is in a different location, the installer will automatically find that copy and perform an "upgrade" instead, rather than install an additional version to the Applications folder. I’d recommend running your installer on a fresh machine/VM and see if Viscosity gets installed to the correct location.

It is possible to turn off this behaviour by editing the installer project in the Packages application and removing any locators:
http://s.sudre.free.fr/Software/documen ... oad.html#4

Cheers,
James

Re: Bundling Viscosity on MacOS High Sierra does not work

Posted: Mon Feb 12, 2018 8:00 pm
by JdZ
As mentioned in my original post
"When I test this new package, (first uninstall the existing Viscosity version) and then run the new install package"

So as long as Viscosity is removed when I remove it this should not be the reason as I understand it .

And Viscosity has only been installed in the default location on this computer before I removed it .

I also tried a previous pkg package I made and that installed just fine.

Re: Bundling Viscosity on MacOS High Sierra does not work

Posted: Mon Feb 26, 2018 6:11 pm
by JdZ
Also tested this package on a different computer , same behavior. Is this just me this happens to or is there an issue with the template and High Sierra??

Re: Bundling Viscosity on MacOS High Sierra does not work

Posted: Fri Mar 02, 2018 10:16 pm
by James
Hi JdZ,

I'm afraid we're not aware of any issues, nor have we had any other reports. I'd recommend making sure you have the latest Packages application, and maybe try the latest beta version of Packages if the developer has made one available.

The template is super straightforward: you're welcome to try another installer maker if you think there may be an issue with Packages. Basically all that you need to do is copy Viscosity.app to the Applications folder, copy the Preconfigure folder from your bundle to "~/Library/Application Support/Viscosity/Preconfigure", and then execute the command "/Applications/Viscosity.app/Contents/MacOS/Viscosity -installHelperTool YES".

Cheers,
James

Re: Bundling Viscosity on MacOS High Sierra does not work

Posted: Mon Jul 30, 2018 11:20 pm
by JdZ
I finally figured out the reasons for the issues I was having.

The clue is in your (James) previous reply from "Mon Feb 12, 2018 9:04 am" :)

So to recap:
I followed all the steps in the guide
https://www.sparklabs.com/support/kb/ar ... ences-mac/

Important in this case is that I did this: "Before the installer can be customised it is first necessary to copy the Viscosity application itself into the installer template."

I followed all instructions, built the package etc.

I then uninstalled viscosity, I even followed this to make sure all was gone:
https://www.sparklabs.com/support/kb/ar ... osity-mac/

I then tried to test my new installed package (on the same computer I built it on), and the installer seems to run just fine...but it never puts the Viscosity.app in the application folder..

So why is this?

First off, I ran the pkg file from the Template build folder.. that might be stupid, but seems it actually does not matter where I run it from.
More importantly it seems that the installer locates the Viscosity.app file in the Template folder used to build the package in the first place, the : 'Viscosity Installer->Viscosity' folder
So instead of actually 'installing'(copying the viscosity.app to the application folder) it instead upgrades the Viscosity.app file in the Viscosity Installer->Viscosity folder ....brilliant :)

So, if I just delete file in the template folder 'Viscosity Installer->Viscosity' (after I built the package of course) and then run the .pkg file the installation works just fine even on the machine I built the package on.

So the explanation "Is Viscosity already present on the machine you’re testing the installer on? If so, and Viscosity is in a different location, the installer will automatically find that copy and perform an "upgrade" instead, rather than install an additional version to the Applications folder." was absolutely correct.. I just never though it would also include the Template folder on the Desktop in that check ....

Why it didn't work on another computer before I can not explain, because that was months ago..and I could have done something else wrong back then ..

Either way, the moral of the story is if some one gives you an explanation ..read it .. read it carefully .. because it could contain a clue :) it might even contain the answer and solution. Thank you James....several months after . ;)

I hope this helps someone else if they make the same silly mistake I did .