Export tool

[d.healey]

Oh also this Could not find appropriate signing identity for “Developer ID Installer:

You need to put your full ID the team ID box. So it will be something like YOUR NAME (123456) I think you've only put the number. In the next release these will go in two separate boxes instead of one.

[Lindon]

@d-healey said in Export tool:

Just had a look at your log file, think this might be the problem
xcrun: error: unable to find utility "altool", not a developer tool or in PATH

I have no idea what it means, I thought altool was a built in thing. Hopefully some MacOS expert can chip in.

@SteveRiggs - you have XCode 10 installed right?

[SteveRiggs]

@d-healey Ah! My bad. Ok, so I changed that and added the full team ID name and number now. It was only the number before.

The build is still running and it doesn't have the errors about finding the appropriate signing ID now, but it still has the other error about the altool. I'll leave it running for a while and see if it works, as the /signed.pkg is appearing in the folder now which it wasnt before...

[SteveRiggs]

@Lindon I'm on Xcode 8 at the moment being on High Sierra. I cant upgrade to 10, as far as I know?

Looking into it now....

[SteveRiggs]

@Lindon Yeh, I have 10.13.5 and it needs 10.13.6 to run.

I've tried updating to 10.13.6 a few times now and it never works. It ends up freezing the mac on a black screen and when I get it recovered it then wont power down without holding the power button, unless you go in and do some sudo sorcery. Had to do that a few times now.

[Lindon]

@SteveRiggs you are DEF going to need altool

[SteveRiggs]

@Lindon Eesh. Is that part of Xcode 10 then? Any way to get it working on my current setup that you know of?

[Lindon]

@SteveRiggs should be in earlier versions....try and see if you have it and what PATH contains,

[d.healey]

@SteveRiggs Nope has to be at least Xcode 10. Have a read through the Apple docs - https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow

You upload your app for notarization using altool. Xcode 10 or later supports notarization, so if you have more than one version of Xcode installed on your Mac, be sure to use the xcode-select utility to choose the appropriate version:

[Lindon]

@SteveRiggs you should be able to download the command line tools from your Apple developer account - that Should I think include altool - but you will have to put it somewhere that Daves utility can see it...

[SteveRiggs]

@Lindon Ok cheers I'll look for that now....

I just found an app called Transporter which apparently contains altool. I just tried installing that and it also needs 10.13.6 or later so thats no good either for me on 10.13.5. It might be useful for someone else though who is on a later version that mine.

[Lindon]

@SteveRiggs can you not install 10.13.6? Can you not find it? - try this:

Xcode want install on high Sierra … | Apple Developer Forums

(developer.apple.com)

[SteveRiggs]

@Lindon I've tried updating to 10.13.6 a good few times now and it never works. It ends up freezing the mac on a black screen and when I get it recovered back to 10.13.5 so it works again, it then wont ever power down without holding the power button unless you go in and do some sudo sorcery removing files from the registry. Had to do that a few times now. I'm stuck on 10.13.5 on this machine :(

[DanH]

@SteveRiggs What's the machine? Can you def not upgrade the OS? Maybe check DOSDude if you haven't already...

[SteveRiggs]

Thanks @DanH , I'm looking into DOSDude now...

I'm not sure if I can upgrade just to High Sierra 10.13.6 from 10.13.5 though. I don't really want to open the Catalina can of worms just yet while I'm in the middle of finishing a load of projects just incase everything breaks. I've been hearing plenty of horror stories :man_zombie:

This is the machine I'm running at the moment...

[DanH]

@SteveRiggs Mojave is where you want to be ideally (for now). Still supports 32bit (sort of) and HISE all working nicely.

If your HD is removable you could try and do a test run at upgrading on a different HD. Assuming there are no firmware updates that cld set you back.

Anyway Dosdude will have the answers hopefully.

[SteveRiggs]

@d-healey I'm having a go at building installers on Windows now and have a new conundrum to figure out. I'm wondering if you'd experienced anything similar when testing...

When I try and add an installer job to the queue, it's pops up a message saying 'Inno Setup 6 Installation Not Found'

I do already have Inno Setup 6 installed so do I need to do something to point the exporter app to it?

I did notice that Inno setup is installed as 32bit. Could that be the problem?

I'm trying to find information about how to install it as 64bit or how to change the settings in Windows so it installs as 64bit as default but I'm struggling to find anything...

[Lindon]

@DanH said in Export tool:

@SteveRiggs Mojave is where you want to be ideally (for now). Still supports 32bit (sort of) and HISE all working nicely.

If your HD is removable you could try and do a test run at upgrading on a different HD. Assuming there are no firmware updates that cld set you back.

Anyway Dosdude will have the answers hopefully.

it seems it does.. http://dosdude1.com/mojave/

[SteveRiggs]

@Lindon @DanH Cheers fella's. Taking a look at this now...

[d.healey]

@SteveRiggs said in Export tool:

When I try and add an installer job to the queue, it's pops up a message saying 'Inno Setup 6 Installation Not Found'

As always, check github for reported issues ;) - https://github.com/davidhealey/hise-exporter/issues/6