Reviewer can't test the app (most common)
The Apple reviewer needs to browse products, add to cart, and ideally complete a purchase. If your Shopify store is password-protected, has no products, or the reviewer cannot log in with the test account you provided, they will reject the app under Guideline 2.1 (App Completeness).
Prevention:In your App Store Connect review notes, include a working Shopify store URL (without password protection) and a test customer account email and password with at least one saved address. Mention that the checkout opens in a browser and completes on Shopify's website.
If rejected: Open your Shopify store to the public before resubmitting. Remove any storefront password. Add at least a few products.
Missing privacy policy (Guideline 5.1.1)
Every app that collects user data — including email addresses for login — must have a privacy policy URL in App Store Connect. A missing privacy policy is an automatic rejection.
Prevention: Use the Appolar privacy page URL or create your own at your store URL. Add it to App Store Connect under App Information > Privacy Policy URL before submitting.
Account deletion required (Guideline 5.1.5)
Since iOS 15.1, Apple requires that any app offering account creation also provides an in-app account deletion flow. Appolar includes an account deletion option in the Account screen under Settings > Delete account. This sends a deletion request to Shopify, which handles the data deletion per Shopify's customer privacy policies.
If you receive this rejection, it likely means you are running an older version of the Appolar build. Trigger a new build to pick up the latest app version, which includes the account deletion flow.
Minimum functionality (Guideline 4.2)
Apple rejects apps that are too similar to a mobile website or offer insufficient native value. This is rare for Appolar apps because the app includes full native navigation, variant picking, cart management, wishlist, and order history — well beyond a wrapped WebView. However, if your Shopify store has very few products or only external links, a reviewer may flag this.
Prevention: Ensure your store has a real product catalog with multiple products before submitting.
Metadata issues
Common metadata rejections include:
- Screenshots that don't match the actual app — use real screenshots from a device or the Appolar preview
- Description mentioning features the app doesn't have
- App name that's too generic or trademark-infringing
- Missing or broken support URL
Warning. Apple cross-checks your screenshots against the binary during review. Screenshots generated from the web preview that show different content than what the reviewer sees in the running app can trigger a rejection. Always use screenshots captured from the actual running app.
Appealing a rejection
If you believe a rejection is incorrect, respond in the Resolution Center (App Store Connect > Your app > App Review > Resolution Center). Be specific: reference the guideline number, explain what you changed or why the rejection doesn't apply, and attach a screen recording if it helps your case.
Apple's team typically responds within 1–3 business days. For complex cases, you can also request a call with an App Review board member directly from the Resolution Center.