If you distribute a Mac app outside the Mac App Store, the first thing a user meets is whether it opens cleanly. Your own Mac is a poor test, because it already trusts your builds.
Sources, retrieved 2026-10-22: Apple Developer ID and Apple Platform Security: Gatekeeper and runtime protection. Apple says: "Gatekeeper on macOS helps protect users from downloading and installing malicious software by checking for a Developer ID certificate from apps distributed outside the Mac App Store." On notarization: "Give people even more confidence in your software by submitting it to Apple to be notarized." The security guide says Gatekeeper "requests user approval before opening downloaded software for the first time." Behavior differs between macOS versions, so check the current Apple pages for details.
A clean-machine test
- Use a Mac that never ran your build tools. A second Mac, a fresh user account or a clean macOS VM.
- Deliver the build the way users get it. Upload it to your download location and download it in a browser. Copying by USB or network share skips the step you want to test.
- Open it by double-click. Record exactly what appears: no message, a warning, or a block.
- If there is a warning, write it down word for word, with the macOS version. Decide whether it is expected or a signing or notarization problem. Apple's Developer ID page says software is uploaded for notarization with the "xcrun notarytool command-line tool"; for inspecting signing and notarization status, see Apple's current notarization documentation.
- Test every container. Disk image, zip or installer package can behave differently. Test the one you ship.
- Test first launch and a later launch, and after moving the app to the Applications folder.
- Test the update path. An update delivered to an already installed app must not trigger new warnings.
- Retest after each change to your build or signing setup. A new certificate or build script can break a build that worked.
Record results
| macOS version | Delivery | Container | Result |
|---|---|---|---|
| Example: one recent version | Browser download | Disk image | Opens, no warning |
(The row is an example of the format, not a real result.)
Ask testers to help
Ask a few people on different macOS versions to download and open the build, and report the exact message, with a bug report template.
AppReviewX accepts apps by store link from Google Play, the Apple App Store, the Mac App Store and the Microsoft Store. Windows and Mac apps must already be published in their store, and AppReviewX does not distribute builds or installers. Feedback is private and structured, one accepted feedback = one credit, and store ratings are voluntary, unpaid and never required. Back to the Windows and Mac apps hub. Related: Windows installer and update testing, beta testing a Windows app. If you also ship on mobile, start free.