You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: release/certs.md
+67-9Lines changed: 67 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -371,7 +371,7 @@ Examine the contents of the output (e.g., `codesign0` )for signature expiration
371
371
372
372
- Primary Bundle ID
373
373
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.)
375
375
376
376
- app-specific Password
377
377
@@ -393,18 +393,76 @@ Examine the contents of the output (e.g., `codesign0` )for signature expiration
393
393
RequestUUID = e8d76646-d018-468d-bb0f
394
394
```
395
395
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".
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:
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:
"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
+
```
402
460
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.
404
462
405
-
- Stapling
463
+
- Stapling After Successful Notarization
406
464
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".
0 commit comments