App Features
Feature entries are centralized in the Features / In-App Purchases area: IAP, subscriptions, in-app events, server notifications, associated domains, and more. Whether a capability works depends on the App ID + provisioning profile + Xcode all being consistent.
- Define the product ID first (immutable); distinguish consumable, non-consumable, and auto-renewable subscriptions.
- Fill in localized name and description, and upload a review screenshot (showing the actual purchase UI).
- Pricing and availability: choose price tiers and countries/regions; subscriptions support trials, offers, and discount codes.
Whether IAP is “available” is determined by the App ID’s capabilities. If IAP isn’t visible in the app, first check whether In-App Purchase is enabled on the App ID and whether the profile was regenerated.
- Support showcasing event cards on the App Store (contests, updates, livestreams, challenges, etc.).
- Provide name, short description, long description, media, and start/end times.
- Keep content compliant; avoid over-marketing or irrelevant info.
- Great for operations: feature launches, limited-time events, livestream tie-ins.
| Capability | Configuration |
|---|---|
| Associated Domains | Universal links/web credentials: enable on App ID and profile; host apple-app-site-association |
| Sign in with Apple | Enable on App ID; follow the “equal button” rule in-app (if you have third-party login, Apple login is required) |
| Push Notifications | Enable Push/Background Modes; create APNs key or certificate; explain usage before the first in-app prompt |
| App Groups | Enable when sharing data with Extensions/Widgets |
- Configure a callback URL (prefer V2) for subscription status changes, refunds, and more.
- Ensure the service is HTTPS and handles signature validation and retries.
- Server notifications are the infrastructure for correct subscription logic (renewals/refunds/grace periods).
- All IAP/subscriptions must provide a test account and reproducible path; incomplete metadata delays review.
- Subscription prices/trials must be consistent between metadata and in-app display to avoid “misleading users” rejection.
- Verify capabilities on a real device after enabling (push and universal links can’t be fully tested in the simulator).
- Required capabilities enabled on the App ID; profile regenerated
- Xcode target matches App ID capabilities
- IAP/subscription metadata and review screenshots complete
- Server notifications integrated and handling key events
- Push, universal links, Sign in with Apple verified on real devices
- Push not arriving? Check the APNs certificate/key, environment (development vs production), and device token/signing consistency.
- Universal links not opening? Check
apple-app-site-associationcontent, domain certificate, and that Associated Domains is enabled in both App ID and Xcode. - Sign in with Apple button not showing? Confirm the capability is enabled on the App ID and the system version supports it.