Reasons for the prompt "application is damaged and cannot be opened. You should move it to trash"

Question

Created 1w

Replies 2

Boosts 0

Participants 2

We have an application which keeps throwing the error "application is damaged and cannot be opened. You should move it to Trash"

We have checked the following possible root causes:

Codesign of the application using the codesign command
Notarization of the application using the spctl command
Executable permissions
Checked for the presence of "com.apple.quarantine" flag for the application using xattr -l <path to executables"

None of the above listed items seemed to be a problem and are as expected.

Can you please help us understand what could cause this issue and how to resolve this without recommending an uninstall/reinstall of the application?

Boost

Answer 1

DTS Engineer OP

Apple

1w

Thank you for providing the details of the checks you've already performed.

Would it be possible to share more information about the specific device or operating system versions that are experiencing this error? Additionally, have there been any recent changes made to the device or the app before this issue started occurring? Is the app version compatible with the OS? Can you provide all that?

Have you checked the sysdiagnose to see the reason?

Albert Pascual   Worldwide Developer Relations.

0

Answer 2

oddeyed OP

5d

This is an issue occurring in Ventura & Sequoia on M1 processor.

We have not looked at sysdiagnose to see the reason as this is occurring on a machine we don't have ready access to.

The following are the details of our investigation based on the logs shared from these machines:

Our application has patched from a legacy version where we were using Rosetta translated binaries to latest arm64 supported version.
Our application was in a repeated install loop due to a buggy script deployed on that machine which is now resolved.
There are no changes to device AFAIK.
The application version is compatible with the OS.

We have done the initially listed checks after these repeated installs have stopped and when this prompt started popping up.

0