I'm not sure if this is the right forum for this, but I figured since Cloud Build is introducing some uncertainty into my process, I'd put it here. Here's my process for my macOS game: I build and notarize my app through Unity Cloud Build (using my Developer ID Application certificate) Download the .app file Build/sign the .pkg file (using productbuild --component APP_NAME.app /Applications --sign '3rd Party Mac Developer Installer: Company Inc. (XXXXXXXXX)' APP_NAME.pkg) Submit to Mac App Store via Transporter Apple sends me this great big long error email, with the headline error of "Invalid Signature." I'm concerned because I know you sign the code before notarization and apple seems to be having problem with some internal unity .dylibs. So if anyone has any insight on how the notarization process is actually going in cloud build, that'd be useful. I've also asked this question (worded somewhat differently) on the apple forums, in case I forget to update this and I figure it out over there.