Repository navigation
|
How can a team catch Digital goods sold without Play Billing 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\|PayPal\|razorpay' --include='*.kt' --include='*.java' --include='pubspec.yaml' --include='package.json' . && ! grep -rnE 'BillingClient|com.android.billingclient|in_app_purchase|purchases_flutter|flutter_inapp_purchase|react-native-iap|react-native-purchases|expo-iap|cordova-plugin-purchase|@revenuecat/purchases-capacitor' .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 third party payment SDK is used for in app digital goods rather than Play Billing. The fix. Use Play Billing for in app digital goods, with regional alternatives only where Google permits. 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, which reports this as
GOOGLE-PLAY-BILLINGwith a coverage line and a …