Unlike sandboxing, notaries should have no harmful effects for most Mac apps.
As always, the real issues start when you try to inject Notarisation into the tangled web of modern Mac software development: rights, certificates, automated Xcode build chains, build settings, etc.
In this context Had it saved me a lot of time if I had known how to find out if a product has the fact signed with a secure timestamp. Performing "code names – verifying – deep-knit – verbose = 4 – showing -r- / path / to / my / product" will show many things. If there is a line of " Signed Time " in between, it means that you did not sign with a secure timestamp . If you have a line with " Time Stamp " in it, it means you have a secure timestamp.
For most of my products, Sparkle is just frames that I collect, so I blame it for the whole of the dreaded complexity and wasted time for frame signing .. which is a lot of blame. Signing frames is hell .. or used to be hell .. and now hell is again.
This [timestamp issue] is covered on the searchable "Solution of common notarization problems" page.
Stay updated by subscribing to the RSS feed for this post.