Notarization taking hours??

I started a notarization run a few hours ago. (and used --wait)

Conducting pre-submission checks for Metrix Installer.dmg and initiating connection to the Apple notary service...
Submission ID received
  id: dd77be4c-0cb6-4913-a846-d4025ede37fd
Successfully uploaded file
  id: dd77be4c-0cb6-4913-a846-d4025ede37fd
  path: /Users/johnluss/Work/Metrix Installer.dmg
Waiting for processing to complete.
Current status: In Progress.................................................................................................................................

I finally ctrl-c out of it (PAGES of ....) and tried getting the log

Submission log is not yet available or submissionId does not exist
  id: dd77be4c-0cb6-4913-a846-d4025ede37fd

The Apple System Status page shows all servers up and running.

Any suggestions on what might be going wrong?

I just tried notarising a tiny test project and it took about 30 seconds. So I don’t think that the notary service is completely borked. That and the fact that DevForums hasn’t exploded with grumpy Mac developers who can’t ship their products (-:

Please retry and see if you’re still having problems. If so, try notarising a small file and see if that also has problems. If it does, that suggests the problem is tied to your environment [1]. If it doesn’t, that suggest that the problem is triggered by your content [2].

Let me know what you find.

Share and Enjoy

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

[1] Or possibly your account, but that’s much more unusual.

[2] Which isn’t to say that there’s anything wrong with your content. Sometimes specific content triggers obscure bugs in the notary service.

Well, after quite a few hours (not sure how many, but > 4) it came back with this:

Error: internalError(statusCode: Optional(500), strData: nil, jsonData: Optional(["statusCode": 500, "errors": <__NSSingleObjectArrayI 0x600000db82b0>(
{
    code = "UNEXPECTED_ERROR";
    detail = "<null>";
    id = G5FW7NFIIPPCZWYPDTUGODP7EQ;
    links = "<null>";
    status = 500;
    title = "Uncaught server exception";
}
)

])) Please try again at a later time.

I'll do some experiments to see if I can narrow down what part of my DMG is breaking the server.

My initial experiment indicates that if I use "zip -ry something.app" to create a zip of the app, then use "unzip something.app.zip" to restore it - that results in the Notarization of the DMG hanging and causing the above error. Previously, I had tried using just "zip -r something.app". When I unzipped that I'd always get a prompt asking to overwrite some file, which probably meant a link wasn't being handled correctly.

Being unable to transfer the app via .zip is going to be a PITA.

Well, after quite a few hours (not sure how many, but > 4) it came back with this

Yikes!

I’d appreciate you filing a bug about this. You don’t have to do anything complicated, just include the UUID of your request and your experience of the problem.

Please post your bug number, just for the record.

With regards your zip issue, using the standard zip and unzip commands isn’t a good idea on macOS because they don’t have deal with extended attributes. For more background on this, see Extended Attributes and Zip Archive.

The recommended alternative is ditto. Our Customizing the Notarization Workflow doc shows an example of this.

Having said that, the fact that zip fails suggests that your product is relying on extended attributes, something that I recommend against because zip isn’t the only transfer mechanism that drops them. If you zip your app with ditto and then list its table of contents using unzip (with the -l option), what sort of AppleDouble files do you see?

Share and Enjoy

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

Notarization server hangs for hours then returns an error FB11547511 — Developer ToolsDeveloper Certificates, Identifiers, and Profilesjust now

Notarization taking hours??
 
 
Q