Posts

Post not yet marked as solved
9 Replies
1.2k Views
Previous to the notarization requirement, we were able to offer custom downloadable packages (.pkg files) to our customers. This package could include extra information like accountIds or a different subset of the software and such so that when installed the software would be associated with the customers account automatically and have the correct features installed.We did this by modifying the install scripts and repackaging on the fly then resigning. All of this was done on a linux machine because Apple does not have much support to legally/easily license osx in the cloud.Now with catalina, and the additional notarization requirement, we could still modify install scripts and resign, but we are unable to notarize the new package for two reasons:1. It takes a long time and will fail peroidically.2. We cannot run the notarization and staple from the cloud anyway (without licensing trouble).My question is this:Is there a Apple recommended method to provide custom packages for different customers? Some way to add additional parameters to a package without breaking the notarizartion/signing of it?
Posted
by mriley.
Last updated
.
Post not yet marked as solved
5 Replies
2.1k Views
I am currently notarizing from the command line.When I try to notarize an item that has already been uploaded the result from the command line is:2019-07-30 12:43:05.491 altool[11971:259993] No errors getting notarization info. RequestUUID: <redacted> Date: 2019-07-30 16:40:25 +0000 Status: invalid LogFileURL: (null)"Then in a minute or two I get an email explaining that "ITMS-90732: Duplicate Upload - The software asset has already been uploaded."My question is how I can get this info from the command line so the build script can deal with the result?
Posted
by mriley.
Last updated
.