Application not getting identified after notarization

Hi folks

We have a Developer ID Application which we create using electron. We made our last release for our Application on Nov'24 which was correctly working.

Using the same code, we tried creating a notarized application again which started showing the following error while opening our Application.

Monterey-

M2-

When we directly run the dmg on the dev machine, it does not give us the prompt. But if we download it from somewhere and run, the prompt comes up even in dev machine.

We executed some commands to verify the notarization:

1- spctl --assess -vv /Applications/Refresh\ Pro.app

On both dev machine and non-dev machine, the output was "accepted"

/Applications/Refresh Pro.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: Prograde Digital Incorporated (*******)

2- xcrun stapler validate /Applications/Refresh\ Pro.app On dev machine, we executed this command and the output is as follows.

Processing: /Applications/Refresh Pro.app
The validate action worked!

3- codesign -vvv --deep --strict /Applications/Refresh\ Pro.app/

/Applications/Refresh Pro.app: valid on disk
/Applications/Refresh Pro.app: satisfies its Designated Requirement

We have created a bug attaching the dmg. Please suggest anything we can try to make the release out the door.

Bug link- https://feedbackassistant.apple.com/feedback/16811025

Answered by DTS Engineer in 829030022

The best way to investigate problems like this is to run syspolicy_check against your app. That usually helps you pinpoint the source of this problem.

If that fails, I have a bunch of additional info in Resolving Trusted Execution Problems. Oh, and the #1 source of this problem is folks disabling library validation when they don’t need to. See Resolving Gatekeeper Problems Caused by Dangling Load Command Paths.

Share and Enjoy

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

The best way to investigate problems like this is to run syspolicy_check against your app. That usually helps you pinpoint the source of this problem.

If that fails, I have a bunch of additional info in Resolving Trusted Execution Problems. Oh, and the #1 source of this problem is folks disabling library validation when they don’t need to. See Resolving Gatekeeper Problems Caused by Dangling Load Command Paths.

Share and Enjoy

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

Application not getting identified after notarization
 
 
Q