App-Review is not a QA Department. They are just checking if apps follow the Appstore-Guidelines. If your app crashes at start, the reviewer can't review and this is what he (or she) has told you. Even if your app passes app-review, it can crash on millions of user devices and I don't think that many of the disappointed users will give you more information than a bad ranking.

You have seen that?https://bugs.openjdk.java.net/browse/JDK-8223671You can only fix the problem with an old sdk by compiling the binary against a newer sdk.I don't know if this is what you really want...GreetingsBrigitte

You have seen this one?https://developer.apple.com/library/archive/releasenotes/General/ValidateAppStoreReceipt/Chapters/ValidateLocally.htmlYes, Apple provides a receipt if someone downlods your app from the appstore. You can validate it locally or validate it with the appstore. For Testing you need a sandbox tester account.GreetingsBrigitte

I don't think it is a problem about notarization, but about your Developer Certificate.If an app isn't notarized properly, the message is somewhat about 'Isn't checked for malware'.The message you see indicates what it said: Your Developer ID can't be verified.If you want to distribute your app outside the Mac-Appstore you'll have to sign it with the Apple Development certificate, not with the Apple Distribution certificate. The Apple Distribution certificate is for distributing via Appstore.And:Nether sucessfull signing or notarisation will remove the quarantine-flag. The quarantine-flag tells macOS to check signing and notarisation.GreetingsBrigitte

You don't need hardened runtime if yout want to publish your app via appstore. Yo need to enabled Hardened Runtime for Notarisation when you want to publish your app outside of the appstore. GreetingsBrigitte

Seems like your App includes a framework 'TrustDefenderMobile' and this framework uses UIWebView. You have to get a new version of TrustDefenderMobile.framework (without UIWebView) or get rid of it. Greetings Brigitte

Take a look at Security-Scoped Bookmarks. You can find a short description how they work in the last half of this document: https://developer.apple.com/library/archive/documentation/Security/Conceptual/AppSandboxDesignGuide/AppSandboxInDepth/AppSandboxInDepth.html Nevertheless you have to ask for permission via NSOpenPanel for the file or the folder one time. Then you can persist the Security-Scoped Bookmark for future use. Greetings Brigitte

We are facing the same issue. I filled a bug report, but if anyone here has a quick solution / workaround, I would be very grateful.

You have to add <key>NSCameraUsageDescription</key> <string>Explain why your app wants to access the camera</string> in the info.plist of your app. Greetings Brigitte

Can the executable itself be an app? In my projects, the executable is just an executable file. Greetings Brigitte

Do what they say: Use WKWebView instead of UIWebView. Greetings Brigitte

Are you talking about apps, that were distributed via Appstore? Then you should take a look at Appstore-Review-Guidelines, 2.4.5, (viii): They must use the Mac App Store to distribute updates; other update mechanisms are not allowed. Every change of a signed binary will break the signature, and apps with an invalid signature won't start.

No. https://developer.apple.com/app-store/review/guidelines/ 4.3 Spam

It's not your certificate that is wrong or expired, it's your root-certificate (R3) that is expired on 29. September 2021, 21:21:40. And it is also an macOS issue.

Try to run: install_name_tool -change @executable_path/../libtbarcode11.0.dylib @executable_path/../Frameworks/libtbarcode10.0.dylib <PathToTheNewLibrary.dylib> Hope it helps. Brigitte