Expansion Installation Issue

[d.healey]

@casey-kolb said in Expansion Installation Issue:

are we supposed to sign the hr1 file?

I don't know, I hope not, but I'm wondering if it would make a difference.

[Casey Kolb]

@d-healey Signing the plugin seems like it would make a difference. I'll give that a whirl.

[d.healey]

@casey-kolb Let us know if it solves it. Also is the issue there if installing from a standalone app?

[Casey Kolb]

@d-healey So far only tested from Standalone app.

[d.healey]

@casey-kolb Was it codesigned?

[Casey Kolb]

@casey-kolb It was not. I'm like 90% sure that's the problem now that you mention it.

[yall]

@d-healey I sent one of my vst to friends who had a mac m1. and the download of the hr1 was considered dangerous so directly deleted. I sent it back in zip format. it has passed but others have not. I then created a pkg to simply drag the hr1 into the library then signed and notarized. and no problem. so I made my life difficult for not much. I think you just have to put the hr1 with a zip created from a mac. and send it and it works most of the time

[Casey Kolb]

@yall That makes sense. I've been zipping the hr1, so I think we're all good there.

[d.healey]

@casey-kolb said in Expansion Installation Issue:

I've been zipping the hr1

Seems redundant, like putting a zip file in a zip file.

[Casey Kolb]

@d-healey Yeah, but Macs at least know what a zip file is when you're downloading. It does seem safer, especially considering that things can get corrupted if they're not zipped, and if you're using Dropbox or other platforms to share with beta testers.

[A Former User]

Not sure if they're related but a Windows user just informed me that the expansion installer gets stuck at 0% for them... Master branch

[d.healey]

@iamlamprey Unrelated I think, test on develop branch

[A Former User]

@d-healey Yeh it was unrelated, just following up here in case someone else has something similar happen -> run Ableton as an Admin :)

[Casey Kolb]

Ok so after testing this and code signing / notarizing my apps and installers, this is still an issue I can't resolve. It won't install expansions on certain Macs unless the Samples folder has Write permissions for "Everyone", even if I use setReadOnly(false) for the Samples folder.

@Christoph-Hart Any thoughts on this?

[DanH]

@Casey-Kolb I have users getting stuck on the install too, across Win and Mac... Did you get to the bottom of this? I can't recreate the problems here so its super tricky to know what's going wrong!

[Casey Kolb]

@DanH Yes, we figured out that you need to install the samples to the default Expansions folder within the AppData folder to ensure your plugin has the right permissions for unpacking the samples. Basically, your plugin won't be able to write to a lot of directories on the OS because the folders may be read-only for the plugin. I'd recommend not even giving the user a choice for where to install the samples, and if they need to move the samples, they can always move them to their samples folder manually.

[DanH]

@Casey-Kolb great, thanks for letting me know! Did you run the install within the plugin or with a .pkg?

And no problems on Windows then?

[Casey Kolb]

@DanH It's currently installed within the plugin, but honestly a .pkg makes a lot more sense. We do have license keys for expansions though, so it's a bit tricky. It would certainly be faster with a .pkg file

[d.healey]

Might be relevant to this thread...

I've just added a File.hasWriteAccess() script wrapper function so you can verify if a directory selected by the user is writable and prompt them for another location if it isn't.

[bendurso]

Is there some way to give permissions to the plugin to install samples in a custom location now? Or still the better option is to install the samples in the appdata folder?