My iOS apps are getting rejected more and more often because of “Guideline 2.1 - Performance - App Completeness” where they claim they do not find the submitted new subscription in the submitted binary.
This is an interesting take because:
I cannot put the new subscription in my RevenueCat defaultoffering because it is not approved yet - so anybody who downloads the app now would not see it.
But if I dont put the new subscription in my default offering obviously the App Review team will not see it during review.
What would be the best practice to introduce new subscriptions, so it does not mess up the paywall for the existing users but also the App Review team sees it in the app. How you usually do it?
(Depending on the paywall and the products in the default offering, you cannot really put the new subscription there before it got approved. For example if I have only 1 subscription product in my default offering, etc)
(Also sometimes you just want to submit a new subscription to be able to use it later in an A/B test.)
Best answer by jeffrey_bunn
Hi @zoli! Adding a new subscription to an existing app is definitely an interesting problem. You should be able to submit the new products to app review directly from the product screen (and not alongside a new app version). Reviewers should only need a screenshot of your paywall with the new product to approve it.
Here’s another way you could approach this:
Add your new product to RevenueCat and create a newOffering.
Create a new Paywall (or duplicate your current one) and attach it to the new Offering.
Create a Targeting rule with an App Version condition that matches your new version. This rule should point to your new Offering if the iOS version matches your new version.
In App Store Connect, set your new version to be released Manually.
After the app has been reviewed and approved, remove your targeting rule.
Release your app.
Give your new product at least 24 hours to fully propagate.
When ready, add the new product to your default Offering.
I hope this helps! Please let me know if you have additional questions.
Hi @zoli! Adding a new subscription to an existing app is definitely an interesting problem. You should be able to submit the new products to app review directly from the product screen (and not alongside a new app version). Reviewers should only need a screenshot of your paywall with the new product to approve it.
Here’s another way you could approach this:
Add your new product to RevenueCat and create a newOffering.
Create a new Paywall (or duplicate your current one) and attach it to the new Offering.
Create a Targeting rule with an App Version condition that matches your new version. This rule should point to your new Offering if the iOS version matches your new version.
In App Store Connect, set your new version to be released Manually.
After the app has been reviewed and approved, remove your targeting rule.
Release your app.
Give your new product at least 24 hours to fully propagate.
When ready, add the new product to your default Offering.
I hope this helps! Please let me know if you have additional questions.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
