Well, I can't see any fooling of the rating system. The user can leave a review whenever he wants. Asking for a review when he's in a good mood is simple marketing.
Even Apple gives tips and tricks how to get good reviews from within an app.
You can ask users to rate and review your app at appropriate times throughout the user experience. Make the request when users are most likely to feel satisfaction with your app, such as when they’ve completed an action, level, or task. Make sure not to interrupt their activity.
The SKStoreReviewController API lets you give users an easy way to provide feedback about your app. You can prompt for ratings up to three times in a 365-day period. Users will submit a rating through the standardized prompt, and can write and submit a review without leaving the app.
Ensure that your support contact information is easy to find in your app and on your App Store product page. This gives users a direct way to reach you if they encounter difficulties, and gives you an opportunity to resolve negative experiences that may otherwise lead to poor reviews.
From:
https://developer.apple.com/app-store/ratings-and-reviews/
Greetings
Brigitte
Try to run:
install_name_tool -change @executable_path/../libtbarcode11.0.dylib @executable_path/../Frameworks/libtbarcode10.0.dylib <PathToTheNewLibrary.dylib>
Hope it helps.
Brigitte
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.
No.
https://developer.apple.com/app-store/review/guidelines/
4.3 Spam
Post not yet marked as solved
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.
Do what they say: Use WKWebView instead of UIWebView.
Greetings
Brigitte
Post not yet marked as solved
Can the executable itself be an app? In my projects, the executable is just an executable file.
Greetings
Brigitte
Post not yet marked as solved
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
Post not yet marked as solved
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.
Post not yet marked as solved
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
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
