notarize-app | Linear notarize and staple for build tools

TLDR: check your developer.apple.com account has admin permissions for your organization and go to https://appstoreconnect.apple.com/ to accept the legal docs.

I also got the error "Error: You must first sign the relevant contracts online. (1048)".

Navigating to developer.apple.com memberships or anything else didn’t reveal prompt. It turned out, my Apple developer account had no "admin" rights within our organization and I could not see the legal prompts, but there was no indication of this.

After a team member with admin access navigated to https://appstoreconnect.apple.com/ there was a pending agreement that had to be accepted and the error went away.

UPD. Comments suggested that the agreements could also be directly reviewed at https://appstoreconnect.apple.com/agreements/#

You don't download your plugin.zip from Apple - just work with the same archive you originally uploaded to them. You are the one that actually staples the notarization ticket to whatever you are notarizing.

I haven't tried it myself with a .zip, but this is the process pieced together from the documentation.

Notarizing Your App Before Distribution says:

Notarize Your Preexisting Software

[...]

1. Upload your software to the Apple notary service, as described in Upload Your App to the Notarization Service.

You've already done this step.

1. Staple the returned ticket to your existing software, as described in Staple the Ticket to Your Distribution.

You have to attach the notarization ticket to whatever you're distributing, so Gatekeeper can find it even without a network connection. Normally you use the stapler tool to do this:

xcrun stapler staple MyApp.app

However, stapler doesn't support zip files. Customizing the Notarization Workflow says:

While you can notarize a ZIP archive, you can’t staple to it directly. Instead, run stapler against each individual item that you originally added to the archive. Then create a new ZIP file containing the stapled items for distribution.

So; expand your .zip and run stapler staple {filename} against each item contained inside. Then create a new .zip archive of the stapled contents.

couple of things need to be done.

1) manage app specific password(https://appleid.apple.com/account/manage) https://github.com/expo/expo-cli/issues/927

2) try to type all commands manually so that command line should not have escape character(before I tried to copy paste commands)

I've seen this error before, I forget what exactly caused it, but it definitely would have been a mistake in the way I submitted the command. Unfortunately, altool does not appear to have been written with user-friendliness in mind and does not seem to do much in the way of command line validation.

With that in mind, taking a closer look at your command lines, I notice:

• It should be --asc-provider, not -asc-provider. Two hyphens, not one.
• The --notarization-info sub-command actually does not need the --asc-provider option as the UUID is unambiguous for identifying the notarisation transaction you're after.

Tips for anyone finding this answer after a web search for this error message:

• Compare xcrun altool --help with your actual command. Check number of hyphens, and make sure the command you're running requires or supports the arguments you are passing.
• Check that all strings (user name, provider, bundle IDs, password (I strongly recommend the keychain provider over providing the literal password on the command line!), etc.) are correctly escaped and surrounded by quotes for good measure.

If your firewall is blocking the port for transferring except HTTPS, following answers may help you.

itunesconnect using application loader behind a firewall

Upload iOS App to AppStore using port 443