Best practice for notarization to reduce the time?

Question

Created Mar ’21

Replies 2

Boosts 0

Participants 2

Hi,

My pkg(installer) is pretty huge(over 5G bytes) because of the resources (images/wavs). The resources are almost 2G bytes.
Also we have 2 different packages like a full installer and an updater in which most of the bundles are shared.

It takes huge time to get notarized because of the context above. Is there any economical way to be notarized? For instance, uploading a zip contains the bundles and package them as a pkg after getting notarized. If it is possible, I could reduce the traffic and time.

Thanks,

Kaz

Answered by DTS Engineer in 666065022

Is there any economical way to be notarized?

Not really, at least not with your current architecture. For Gatekeeper to accept an installer package the package itself must be notarised. The resulting ticket references the signature of the package, and that signature (hopefully :-) covers all the content of the package. So there’s no point notarising code items within that package because the whole package still needs to be notarised.

Do your resources change less frequently than your code? If so, you could split them out into a separate package. That’s more of a hassle for your users — they’d have to install both packages — but it would get past this problem. And it would also save your users some download time (-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

Mar ’21

Accepted Answer

Is there any economical way to be notarized?

Not really, at least not with your current architecture. For Gatekeeper to accept an installer package the package itself must be notarised. The resulting ticket references the signature of the package, and that signature (hopefully :-) covers all the content of the package. So there’s no point notarising code items within that package because the whole package still needs to be notarised.

Do your resources change less frequently than your code? If so, you could split them out into a separate package. That’s more of a hassle for your users — they’d have to install both packages — but it would get past this problem. And it would also save your users some download time (-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

ioue OP

Mar ’21

Thank you for the comment. I understand it.
The thing I could do is splitting the bundles and the resources as you mentioned and letting customers download the resources at the 1st launch of the app like Garageband.

Kaz

0