Export tool

[d.healey]

@DanH said in Export tool:

@LeeC Spaces in the notarization file path aren't allowed

Just for clarification, spaces are "allowed" but the export tool has a bug with spaces on a Mac. It will be fixed when I do the next round of updates. If you want to see the complete list of known bugs you can check the github issues :)

[d.healey]

@LeeC That file is created internally by the export tool. Do you have a space in your project path?

[LeeC]

@d-healey Yep 2 spaces to be exact!
I'll remove them and retry... thanks

[LeeC]

@d-healey That worked thank you.
Managed to get all the way through to Notorization and saw:

Status Message: Package Approved

It completed and I did see a quick prompt from HISE Exporter saying that 'Notarization failed' but when I check in the 'Darwin' folder in my project folder I see a 'PluginName signed.pkg'.

Is there a quick way to check if this file is indeed Notorized?

Cheers

[d.healey]

@LeeC
https://github.com/davidhealey/hise-exporter/issues/21
https://stackoverflow.com/questions/55074168/how-do-i-verify-that-a-macos-pkg-is-notarized

[LeeC]

@d-healey Perfect and apologies for not checking the bug board
Man, I have to say that this is an insanely useful tool and you've solved a very sticky pain point for a lot of us.
Just EPIC!
Thanks again

[SteveRiggs]

@d-healey

I'm having a bit of trouble with getting a signed and notarized installer to work on Mac High Sierra.

I've successfully built an un-signed and un-notarized installer, but when I try notarized one I keep getting this error?

I left it for 3 hours last night and then tried another 2 attempts at over an hour each but the circle keeps spinning.

I made sure there are no spaces or capital L's in the file path or project name but still no joy.

Also made my 2 certificates and put them in keychain. Any idea what could be wrong?

These are the 2 certificates I made...

[d.healey]

@SteveRiggs Any spaces in your project path?

[SteveRiggs]

@d-healey Not that I can spot. Are there any other characters in the file path that could be affecting it?

[d.healey]

I can't see anything unusual there. The error your getting is coming from the notarization status check, I wonder if the notarization server was down when you were trying to notarize. You can always check the status here btw - https://developer.apple.com/system-status/

Give it another try, if it doesn't work send me the log file.

[SteveRiggs]

@d-healey Thanks mate. Just checked and it's saying it's available. I'll save the link and try another build now...

[SteveRiggs]

@d-healey Sorry for all the questions...

It failed with the same error again. I'll PM the log file now...

Other than the 2 certificates I made, do I need to make an Identifier App ID as well? Or are there any other things I need that could be stopping it from notarizing if I missed something on the developer site?

[d.healey]

@SteveRiggs If I remember correctly you need to make an app specific password and enter it in the settings page.

[SteveRiggs]

@d-healey I did do that before when I first tried the exporter app. Do I need to do that every time? I think it's saved from the first time

[SteveRiggs]

@d-healey I just made a fresh app specific password and I'm trying an installer build with that. Still getting the same red error though

[SteveRiggs]

@d-healey I may have found the cause... My certificate had no private key attached. Just started over and re added them to keychain so I'll try another build.....

[d.healey]

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.

[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...