Expansion Install getting stuck

[d.healey]

@DanH Your code looks fine to me. Is the plugin codesigned/notarized? Does it work in standalone?

[DanH]

@d-healey Thank you. Yes fully signed and notarized etc. Everything works here and I can't recreate the issue so I'm really stuck

Could be a bit flakey on the HISE side of things perhaps....

[d.healey]

@DanH Does it work in standalone?

[DanH]

@d-healey Right - the answer is sort of, here's what I've found so far for OSX (will attempt Windows later):

• If the main 'factory' samples are installed on an external drive then I can install the expansion samples into the same folder BUT!! - no link file is created and my standalone cannot find the samples.

• If the factory samples are installed on the system drive and I try to install the expansion samples into the same folder then the install process hangs UNLESS - I update the permissions of that folder and change 'everyone' to 'Read & Write'.

• Installing the expansion content to a new folder on any drive is fine (but this apparently still doesn't work for the users who are having issues).

I seem to remember a thread about the link file not being written not so long ago.

Anyway I might resort to creating custom installers for expansions...

[d.healey]

@DanH said in Expansion Install getting stuck:

@d-healey Right - the answer is sort of, here's what I've found so far for OSX (will attempt Windows later):

• If the main 'factory' samples are installed on an external drive then I can install the expansion samples into the same folder BUT!! - no link file is created and my standalone cannot find the samples.

• If the factory samples are installed on the system drive and I try to install the expansion samples into the same folder then the install process hangs UNLESS - I update the permissions of that folder and change 'everyone' to 'Read & Write'.

• Installing the expansion content to a new folder on any drive is fine (but this apparently still doesn't work for the users who are having issues).

I seem to remember a thread about the link file not being written not so long ago.

Anyway I might resort to creating custom installers for expansions...

Were these tests done with standalone or plugin?

Here's a function I made for creating the link file myself with my custom installer. You can adapt it to suit your needs.

	inline function createLinkFile(dir, target)
	{
		local filename = "";

		switch (Engine.getOS())
		{
			case "OSX": filename = "LinkOSX"; break;
			case "LINUX": filename = "LinkLinux"; break;
			case "WIN": filename = "LinkWindows"; break;
		}
	
		local f = dir.getChildFile(filename);
		
		if (target.isDirectory())
			f.writeString(target.toString(f.FullPath));
	}

[DanH]

@d-healey Standalone, but I'm almost certain the behaviour is the same in the plugin.

So you've made a custom installer within your plugin for expansions? I was talking about creating a .pkg / .exe

[DanH]

@d-healey where would I put this into my script?

[d.healey]

@DanH

So you've made a custom installer within your plugin for expansions? I

Yes, using zip files instead of hr

where would I put this into my script?

I wouldn't use that with your existing script, this is for a custom installer.

[DanH]

@d-healey Oh ok, What prompted you to do that out of interest?

[d.healey]

@DanH

What prompted you to do that out of interest?

I'm making a custom downloader/installer. The problem with the hr system is if you want to provide a partial update the user has to redownload the entire thing.

Imagine version 1.0 of my library contains 2GB of data, and version 2.0 contains an additional 100mb. The user who already has version 1.0 will have to redownload the 2GB they already have. With zip files I was able to build my own versioning system so users only get the pieces they need. This saves them time on the download/install and saves me money in bandwidth.