Issue with Notarization

[adamretter]

Notarization status(s) is retrievable with:

xcrun altool --notarization-history 0 --username <apple Developer ID here> --password <notarization API key here>

Which gives something like:

Notarization History - page 0

Date                      RequestUUID                          Status  Status Code Status Message
------------------------- ------------------------------------ ------- ----------- ----------------
2021-12-17 16:20:27 +0000 8375797c-5324-404c-ba36-80e72189ad0f invalid 2           Package Invalid

Notarization info about a specific request, and a link to the log is retrievable with:

xcrun altool --notarization-info 8375797c-5324-404c-ba36-80e72189ad0f --username <apple Developer ID here> --password <notarization API key here>

{
  "logFormatVersion": 1,
  "jobId": "8375797c-5324-404c-ba36-80e72189ad0f",
  "status": "Invalid",
  "statusSummary": "Archive contains critical validation errors",
  "statusCode": 4000,
  "archiveFilename": "fusiondb-server-1.0.0-SNAPSHOT.dmg",
  "uploadDate": "2021-12-17T16:20:27Z",
  "sha256": "48cecde44497fe2459e01c12d576284332e5b517bdf87eefcaa05f81e4cc78c3",
  "ticketContents": null,
  "issues": [
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86/libjansi.jnilib",
      "message": "The binary is not signed.",
      "docUrl": null,
      "architecture": "i386"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86/libjansi.jnilib",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "i386"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/arm64/libjansi.jnilib",
      "message": "The binary is not signed with a valid Developer ID certificate.",
      "docUrl": null,
      "architecture": "arm64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/arm64/libjansi.jnilib",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "arm64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86_64/libjansi.jnilib",
      "message": "The binary is not signed.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86_64/libjansi.jnilib",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "x86_64"
    }
  ]
}

[adamretter]

This is now fixed as of Fri Dec 17 23:05:00 2021 +0100 and will appear in the next nightly build of FusionDB.