Export tool
-
@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?
-
@SteveRiggs If I remember correctly you need to make an app specific password and enter it in the settings page.
-
@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
-
@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
-
@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.....
-
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.
-
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. -
@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?
-
@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...
-
@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....
-
@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.
-
@SteveRiggs you are DEF going to need altool
-
@Lindon Eesh. Is that part of Xcode 10 then? Any way to get it working on my current setup that you know of?
-
@SteveRiggs should be in earlier versions....try and see if you have it and what PATH contains,
-
@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:
-
@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...
-
@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.
-
@SteveRiggs can you not install 10.13.6? Can you not find it? - try this:
-
@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 :(
-
@SteveRiggs What's the machine? Can you def not upgrade the OS? Maybe check DOSDude if you haven't already...