We have tried multiple in-house replications for this issue and we were unable to replicate this on demand. This is an issue that is occurring across platforms (Intel/ARM). We have also tried the install on a fresh VM, however, we are unable to replicate this. We have also noticed a pattern of all of the affected machines receiving 15.6.1 OS update few days (as close as few hours before) before our product patch is applied and this prompt is triggered. The install.log indicates a clean install of our product without any issues. I have created a feedback ticket for the same sharing more details on this issues, FB20104614

Thank you. I will not be able to share the link publicly for my application. This is also not occurring on all of the MacOS machines my application is installed in, just a few machines. Please let me know if we can raise a ticket for this. I can share more background and details on this issue in the ticket.

Yes, the application only shows the stapling error which I understand is not a "fatal" error from the documentation. "Severity: Fatal Full Error: A Notarization ticket is not stapled to this application. Type: Distribution Error" I have also run "/usr/bin/log show --predicate '(process == "syspolicyd") && (eventMessage CONTAINS "MyApp")'" and "/usr/bin/log show --predicate '(process == "trustd") && (eventMessage CONTAINS "MyApp")'" I don't see any logs messages for the above two commands

I will be distributing the application directly using Developer ID signing

Please let us know if there is an update on this issue.

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.