Post not yet marked as solved
Ok, just found another thread which actually provides functional workarounds:
https://developer.apple.com/forums/thread/727123
Replacing ditto with zip works for us. For anyone considering doing the same please read the other thread as it contains additional infos which may be important in other cases.
Post not yet marked as solved
We are having the same problem. Since altool notarization will be removed this fall we need a functional workaround soon. In our case the only reason we zip our .app is to send for notarization because altool and notarytool don't accept .app. We distribute only an installer which pulls/updates the .app from our servers. So what is the solution/workaround now? What's the status of the bug report anyway? The link provided above doesn't work for me (feedback not found).
Found the answer: App Store -> Settings has the button to sign out from a sandbox account on 13.4.1.
Post not yet marked as solved
Thank you, that solved the problem!
Post not yet marked as solved
We have resolved the problem. I am presenting details here in case other developers run into the same problem.
First, not every Mac shows the same symptoms. We were unlucky to start testing with a Mac Mini (10.15) that did not trigger the keystrokes dialog which made it impossible for us to debug. Further tests with other Macs were successful and allowed us to localise the problem.
In our case the offending code was located in an older version of SDL (2.0.8). The problem has been fixed in later versions, the two relevant commits are:
Commit 1 - https://github.com/spurious/SDL-mirror/commit/8ace14e8244b7bc82881b7ee437ee3b17ab86985#diff-8779326b1912bdedc731ffe4bf485dc8
Commit 2 - https://github.com/spurious/SDL-mirror/commit/1ceddc5a20b954f7e4110e2cec2403576faf71ab#diff-906b3479f92876240ca6d12bbd1299f8
The first commit contains the actual fix for the privacy problem and the second is a correction, included here in case someone wants to patch older SDL versions instead of upgrading.
Post not yet marked as solved
Hello eskimoYou are correct, disabling Hardened Runtime did not solve the problem.We are also not able to reproduce the dialog. I have installed the failing package on a 10.15 system where the application has never run before. It did not trigger the dialog. This means we are unable to progress.
Post not yet marked as solved
We have been able to solve the problem by removing a specific key from the entitlements file we use for resigning (aps-environment). It is still a mystery to us why we got different results with different certificates. Code signing is way too painful than it should be and the unspecific error messages don't help either.
