Skip to content

Commit 2f3258f

Browse files
more info about notarization
1 parent df3af3b commit 2f3258f

File tree

1 file changed

+67
-9
lines changed

1 file changed

+67
-9
lines changed

release/certs.md

Lines changed: 67 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -371,7 +371,7 @@ Examine the contents of the output (e.g., `codesign0` )for signature expiration
371371

372372
- Primary Bundle ID
373373

374-
Obtain the `primary-bundle-id` from `/Volumes/idv/Integrated\ Data\ Viewer\ Installer.app/Contents/Info.plist`, `CFBundleIdentifier` element. (I actually do not know if an accurate `primary-bundle-id` matters, but this is what I did and it worked.)
374+
Open the DMG you just fetched. This step will mount it into `/Volumes/idv`. Obtain the `primary-bundle-id` from `/Volumes/idv/Integrated\ Data\ Viewer\ Installer.app/Contents/Info.plist`, `CFBundleIdentifier` element. (I actually do not know if an accurate `primary-bundle-id` matters, but this is what I did and it worked.)
375375

376376
- app-specific Password
377377

@@ -393,18 +393,76 @@ Examine the contents of the output (e.g., `codesign0` )for signature expiration
393393
RequestUUID = e8d76646-d018-468d-bb0f
394394
```
395395

396-
If the upload attempt was not successful, you will get a lengthy error log with some obscure error codes. In that case, just try again. Sometimes, you'll have to try a few times before it works. Hopefully, after a few minutes you will get an email saying "Your Mac software was successfully notarized". If not successful, you'll have to run
396+
If the upload attempt was not successful, you will get a lengthy error log with some obscure error codes. In that case, just try again. Sometimes, you'll have to try a few times before it works. Hopefully, after a few minutes you will get an email saying "Your Mac software was successfully notarized".
397397
398-
```shell
399-
xcrun altool --notarization-info <RequestUUID> -u <email> -p \
400-
<app-specific password>
401-
```
398+
- Notarization Failures
399+
400+
After upload to Apple, if there are notarization failures you will see an email from Apple Developer titled "Your Mac software was not notarized". In this case you will have to access the notarization failure with:
401+
402+
```shell
403+
xcrun altool --notarization-info <RequestUUID> -u <email> -p \
404+
<app-specific password>
405+
```
406+
407+
This command will return a message that contains a URL where you can find the error log. **Note** notarization failures are considered by Apple as "upload" failures. This language is somewhat confusing since the DMG may have uploaded to Apple without problems, but when the notarization process fails, it is **still** considered an "upload" failure.
408+
409+
- Common Problems
410+
411+
The most common problem you may encounter is 32-bit code which the notarization process will reject:
412+
413+
```yaml
414+
{
415+
"logFormatVersion": 1,
416+
"jobId": "7c91ddea",
417+
"status": "Invalid",
418+
"statusSummary": "Archive contains critical validation errors",
419+
"statusCode": 4000,
420+
"archiveFilename": "idv_6_0_macos_installer.dmg",
421+
"uploadDate": "2021-07-08T18:50:09Z",
422+
"sha256": "e5d0afa",
423+
"ticketContents": null,
424+
"issues": [
425+
{
426+
"severity": "error",
427+
"code": null,
428+
"path": "idv_6_0_macos_installer.dmg/Integrated Data Viewer Installer.app/Contents/Resources/app/67.dat/ncIdv.jar/com/sun/jna/darwin/libjnidispatch.jnilib",
429+
"message": "The binary is not signed.",
430+
"docUrl": null,
431+
"architecture": "i386"
432+
},
433+
{
434+
"severity": "error",
435+
"code": null,
436+
"path": "idv_6_0_macos_installer.dmg/Integrated Data Viewer Installer.app/Contents/Resources/app/67.dat/ncIdv.jar/com/sun/jna/darwin/libjnidispatch.jnilib",
437+
"message": "The signature does not include a secure timestamp.",
438+
"docUrl": null,
439+
"architecture": "i386"
440+
},
441+
{
442+
"severity": "error",
443+
"code": null,
444+
"path": "idv_6_0_macos_installer.dmg/Integrated Data Viewer Installer.app/Contents/Resources/app/67.dat/ncIdv.jar/com/sun/jna/darwin/libjnidispatch.jnilib",
445+
"message": "The binary is not signed.",
446+
"docUrl": null,
447+
"architecture": "x86_64"
448+
},
449+
{
450+
"severity": "error",
451+
"code": null,
452+
"path": "idv_6_0_macos_installer.dmg/Integrated Data Viewer Installer.app/Contents/Resources/app/67.dat/ncIdv.jar/com/sun/jna/darwin/libjnidispatch.jnilib",
453+
"message": "The signature does not include a secure timestamp.",
454+
"docUrl": null,
455+
"architecture": "x86_64"
456+
}
457+
]
458+
}
459+
```
402460
403-
This command will return a message that contains a URL where you can find the error log.
461+
In this case, make sure you obtain an `ncIdv.jar` from the THREDDS group that does not contain 32-bit code when building the IDV.
404462
405-
- Stapling
463+
- Stapling After Successful Notarization
406464
407-
The last step as part of the notarization process is "stapling".
465+
After the "successfully notarized" email from Apple, the last step as part of the notarization process is "stapling".
408466
409467
```shell
410468
xcrun stapler staple <idv>.dmg

0 commit comments

Comments
 (0)