Repository navigation
|
How can a team catch Digital goods sold outside in app purchase automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'Stripe\|PayPalCheckout\|braintree\|razorpay' --include='*.swift' --include='pubspec.yaml' --include='package.json' . && ! grep -rnE 'StoreKit|SKProduct|Product.purchase|in_app_purchase|purchases_flutter|flutter_inapp_purchase|react-native-iap|react-native-purchases|expo-iap|cordova-plugin-purchase|@revenuecat/purchases-capacitor' --include='*.swift' --include='pubspec.yaml' --include='package.json' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. A web checkout or external payment SDK is used for digital content rather than StoreKit. The fix. Route all digital goods through StoreKit in app purchase unless the app is a documented exempt category. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, …