Highlighted

Gatekeeper on MACOS not accepting Adobe Air packages

Participant ,
Jun 24, 2020

Copy link to clipboard

Copied

Hi!

What we really need is, that the packages generated for MacOS could be send to Apple for notarization:

The Problem is, that Apple is increasing the restrictions from OS to OS. So what i have done

 

1. i have  a captive runtime:  SM.app

2. I codesigned on a MAC with a developer Application certificate I created from Apple

( there some binaries couldnt get codesigned) the Problem ist the Structure of the dreictories which Apple is looking at. to much nesting, Symbolic links etc

here the Link 

3. i use PKGBUild to make an installable Package and sign the package with a Developer Installer certifiacte I created on the developer Portal.

4. I notarize the Package to Apple

5. The Result is below

 

Here I think that Harman should look how to build up the structure of the SM.app to fullfill the  new rules of Apple. Please Andrew (Harman) take a look at this post.

I have man customers buying Apps and the Gatekeeper is not offering to install my APPS

 

cheers Michael

{
  "logFormatVersion": 1,
  "jobId": "f53de63d-6058-4528-aaa6-cb57c67e746a",
  "status": "Invalid",
  "statusSummary": "Archive contains critical validation errors",
  "statusCode": 4000,
  "archiveFilename": "SM.pkg",
  "uploadDate": "2020-06-24T14:26:27Z",
  "sha256": "1112ce4e7602aa7d7a528414c1cb88134bb4da3a459a2c52623234b839bc3878",
  "ticketContents": null,
  "issues": [
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/MacOS/Die Seemannschaft",
      "message": "The binary is not signed.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/MacOS/Die Seemannschaft",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/MacOS/Die Seemannschaft",
      "message": "The executable does not have the hardened runtime enabled.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR",
      "message": "The signature of the binary is invalid.",
      "docUrl": null,
      "architecture": "x86_64"
    }
  ]
}

 

Views

53

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Gatekeeper on MACOS not accepting Adobe Air packages

Participant ,
Jun 24, 2020

Copy link to clipboard

Copied

Hi!

What we really need is, that the packages generated for MacOS could be send to Apple for notarization:

The Problem is, that Apple is increasing the restrictions from OS to OS. So what i have done

 

1. i have  a captive runtime:  SM.app

2. I codesigned on a MAC with a developer Application certificate I created from Apple

( there some binaries couldnt get codesigned) the Problem ist the Structure of the dreictories which Apple is looking at. to much nesting, Symbolic links etc

here the Link 

3. i use PKGBUild to make an installable Package and sign the package with a Developer Installer certifiacte I created on the developer Portal.

4. I notarize the Package to Apple

5. The Result is below

 

Here I think that Harman should look how to build up the structure of the SM.app to fullfill the  new rules of Apple. Please Andrew (Harman) take a look at this post.

I have man customers buying Apps and the Gatekeeper is not offering to install my APPS

 

cheers Michael

{
  "logFormatVersion": 1,
  "jobId": "f53de63d-6058-4528-aaa6-cb57c67e746a",
  "status": "Invalid",
  "statusSummary": "Archive contains critical validation errors",
  "statusCode": 4000,
  "archiveFilename": "SM.pkg",
  "uploadDate": "2020-06-24T14:26:27Z",
  "sha256": "1112ce4e7602aa7d7a528414c1cb88134bb4da3a459a2c52623234b839bc3878",
  "ticketContents": null,
  "issues": [
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/MacOS/Die Seemannschaft",
      "message": "The binary is not signed.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/MacOS/Die Seemannschaft",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/MacOS/Die Seemannschaft",
      "message": "The executable does not have the hardened runtime enabled.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "SM.pkg/SM.pkg Contents/Payload/Applications/SM.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR",
      "message": "The signature of the binary is invalid.",
      "docUrl": null,
      "architecture": "x86_64"
    }
  ]
}

 

Views

54

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jun 24, 2020 1

Have something to add?

Join the conversation