Little late, I know... I've tried: set(CMAKE_XCODE_ATTRIBUTE_SWIFT_OBJC_INTEROP_MODE "objcxx") and it seems to work.

Yes. But you have to notarize the outside-appstore-app. Otherwise gatekeeper prevent the app to start. Greetings Brigitte

I have never experienced that Apple-Review rejected without a reason. In the rejection message, they refer to a guideline your app doesn't comply to or a crash, etc. And if you don't fix it (or demonstrate review, that your app met all guidelines) than you never get through. And no, there is no way to release through the App Store without an approval.

Take a look here: https://developer.apple.com/documentation/appstorereceipts/validating_receipts_on_the_device Keep in mind, that if you don't check what is inside the receipt, your app will start with any receipt. Greetings Brigitte

You don't need a Xcode - Project, but within Xcode codesigning and notarization are much easier than in a separate Workflow. The decisive terminal commands are 'codesign' for signing and 'altool' for notarization. There are man-pages for the commands and a good documentation for manual codesigning: https://developer.apple.com/library/archive/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html With codesigning you will get rid of the 'unidentified developer' message, but without notarization Gatekeeper still won't let you through, because your app isn't checked for malware. That is what notarization does. Please keep in mind that 'altool' will stop working in fall 2023. There will be a replacement for it, but I haven't tried that yet (and forgot the name). Good luck Brigitte

You have to sign the app and then notarize the app. Further informations you can find here: https://developer.apple.com/developer-id/ Greetings Brigitte

We have the opposite problem with local receipt validation. Receipt validation in App-Review works, but in test environment it fails with 'App is damaged', which is also thrown when there is no mas_receipt. And according to this thread: https://developer.apple.com/forums/thread/705761 this is the expected behavior (unfortunately) Greetings Brigitte

Thanks for your answer, Rich, my team is one of those who are using the local receipt validation just to check if the user downloaded our apps from the macOS Appstore, but: DCAppAttestService is available for macOS 11 or newer. What should we do with older systems? The documentation about local receipt validation (https://developer.apple.com/documentation/appstorereceipts/validating_receipts_on_the_device) isn't marked as deprecated and describes the process quite clear: If verification fails, exit with 173. This works for years and it even works sometimes for the last months. So don't you think it is a bug, that Apple should fix? Will Apple fix it? Greetings Brigitte

I think the App Store Guidelines are clear at this point. Take a look at 2.4.5.IV: They may not download or install standalone apps, kexts, additional code, or resources to add functionality or significantly change the app from what we see during the review process. and 2.4.5.VII: They must use the Mac App Store to distribute updates; other update mechanisms are not allowed.

I have already considered a report. And a lot of other developers too, I guess ('Similar reports: More than 10'). The last time this happened it took 2 or 3 month till the problem was fixed. And not for long... Greetings Brigitte

Exactly. If I remove the quarantine flag or download the dmg via curl (which ends with the same result: no quarantine flag) on 10.14 the app starts fine. If the verification starts, the verification stucks after some time. Greetings Brigitte

Have you figured out a solution or workaround? We are stuck in the same situation. The problem occurs when we are moving from intel-only to universal binaries, without making changes to the notarization process (while I'm not sure if we moved the Xcode Version from 12 to 13 at this time). Any help is appreciated. Greetings Brigitte

Same here (since Friday). We use local receipt validation for our apps and we get no receipt for sandbox test accounts. The result is the same: 'App is damaged...' I filled a bug report in Feedbackmanager. Perhaps Apple addresses this issue a bit quicker if more than one developer complains about that. Greetings Brigitte

You are asking for sandboxed Apps, right? No, there isn't a way to avoid the file-open-dialog. Greetings Brigitte

Then you better disable 'Make this app available on Mac' in AppStore Connect.