Notarisation for dummies

[Lindon]

@trillbilly I think like all Apple products(Logic I'm looking at you..) that it looks for the plugin id first and if there are two with the same ID it will only load (find) the first one.. so first step make sure your plugin has a unique ID, then make sure its in the correct AU folder...

this: "or even scan for more than just Apple items" - make me suspect you are not putting your plugins in the correct folder...

[trillbilly]

@lindon I just assumed it was the regular "components" folder. I will do auval with location and find where it is pulling the apple AUs from and direct mine there as well.

When you say unique ID, I assume you mean unique as in per developer? Or do they really want you to go through all AUs on the system and find a unique code...

I will be in studio in a few hours, I'm on dad duty at the moment.

[d.healey]

@trillbilly said in Notarisation for dummies:

When you say unique ID, I assume you mean unique as in per developer

You need to add a company code, a plugin code, and an app bundle ID to your project through the project preferences in HISE.

[trillbilly]

@d-healey yes, I've got all of this. I was just ensuring the unique code only had to be unique to your developer account/company and not unique to all other AUs on the machine...

I guess I should mention I've got everything signed and notarized. I'm just trying to figure out auval to add to the "Apple Process" if you will...

[DanH]

Hi guys, experiencing a really weird issue with Terminal when notarising. Codesigning all fine btw.

so I go to notarise and Terminal says it can't find my file, but when it reads back the file's location there's a 'U201c' in front of my path. So now the path is like:

NSLocalizedFailureReason = "The file '\U201cUsers/UnsignedPlugins/myplugin\n\nxcrun altool --notarize-app --primary-bundle-id com.me.HPRE --username me@mail.com --password **hidden value** --file \U201cUsers/UnsignedPlugins/installer.pkg' cannot be found.";

I'm so baffled! Worked fine a couple of days ago. Anyone come across this?

[orange]

@DanH Check the file path with \ or / question :) macOS uses / for folders

[DanH]

@orange how do I do that?

[orange]

@DanH What is the location of your pkg installer?

[DanH]

@orange Users/UnsignedPlugins/Installer.pkg

[d.healey]

@DanH I posted a script on Patreon a few weeks ago that will do the notarizing for you.

[orange]

@orange For example if the file location is:

Volumes > Folder A > Signed Installers > MyInstaller_v1.1.0.pkg

Then the file path will be this on macOS:

"/Volumes/Folder A/Signed Installers/MyInstaller_v1.1.0.pkg"

But you've used also \ which shouldn't be used here

[DanH]

@orange

But you've used also \ which shouldn't be used here

I haven't, it's just appeared in the error. The path and the command is fine. I've been using it for a year. I think my Terminal is messed up. I just got this error:

*** Error: Failed to get transporter defaults file 'https://contentdelivery.itunes.apple.com/transporter/Defaults.properties': Error Domain=NSCocoaErrorDomain Code=256 "The file “Defaults.properties” couldn’t be opened." UserInfo={NSURL=https://contentdelivery.itunes.apple.com/transporter/Defaults.properties, NSUnderlyingError=0x6000020a8210 {Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSUnderlyingError=0x60000208ef70 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://contentdelivery.itunes.apple.com/transporter/Defaults.properties, NSErrorFailingURLKey=https://contentdelivery.itunes.apple.com/transporter/Defaults.properties, _kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4, NSLocalizedDescription=The request timed out.}}, NSErrorFailingURLStringKey=https://contentdelivery.itunes.apple.com/transporter/Defaults.properties, NSErrorFailingURLKey=https://contentdelivery.itunes.apple.com/transporter/Defaults.properties, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.}}}

[orange]

@DanH It's weird then

[DanH]

@orange oh ffs a single " was the wrong type of ".... Not sure how that got in there!