Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
Then you better disable 'Make this app available on Mac' in AppStore Connect.
Post not yet marked as solved
A quick look at Apples Documentation shows that 'FloatingPointFormatStyle' is available since macOS 12.
https://developer.apple.com/documentation/foundation/floatingpointformatstyle
macOS 12 is still beta, so not much of your customers Macs are now running under macOS 12. And you can't expect them to update in the minute it is released.
Greetings Brigitte
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.
