AppReviewX Log in

Mac App Store review readiness: a self-check

What to verify before you submit a macOS app: completeness, privacy details, sandboxing questions and demo access, with official sources.

A self-check before you press submit. It does not describe how Apple reviews internally.

Source: Apple App Review Guidelines, retrieved 2026-10-22. The guidelines change, so open the current version before you submit. Only the points quoted below were verified.

Much of the iOS advice carries over; see common App Store rejection reasons and how to test. Below are the Mac-specific points to check.

Self-check

  1. Complete and working build. No placeholder text, no dead buttons, no crash on first launch. Guideline 2.1(a) says: "We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems." Run the Mac app testing checklist on a clean Mac.
  2. Listing matches the app. Screenshots show the real app on a Mac; the description claims nothing the app cannot do.
  3. Privacy details match reality. List every kind of data the app and any third-party code collect. Check: review your SDKs and network calls. Guideline 5.1.1(i) says: "All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner." For the other privacy fields in App Store Connect, check the current App Store Connect help. Not legal advice.
  4. Sandbox and permissions. Guideline 2.4.5(i) covers apps distributed via the Mac App Store: "They must be appropriately sandboxed, and follow macOS File System Documentation." Request only the access you need, explain each request in the interface, and test with access denied.
  5. Demo access. If the app needs an account, a server or a license, give the reviewer working credentials or a demo mode, and keep the backend running during review.
  6. In-app purchase and account flows work as described, if you have them. Test them with the store's test mechanisms. Guideline 3.1.1 says: "If you want to unlock features or functionality within your app ... you must use in-app purchase." Guideline 2.4.5(vi) says Mac App Store apps "may not present a license screen at launch, require license keys, or implement their own copy protection."
  7. Support and contact details are reachable. Send yourself a message through the listed channel.
  8. Keep notes for the reviewer. Short steps to reach the main features, and anything unusual such as a hardware requirement.

Direct distribution is different

Distributing outside the store has different checks; see notarization and Gatekeeper testing.

Do not buy, swap or reward ratings; see why buying app reviews backfires.

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. If you also ship on mobile, start free.