Quick auto-renewal App review question

We have created an auto renewing subscription for our existing App that used to support only non-renewing payments. The subscription seems to work fine on our test server with compressed times.

We would now like to submit our App for review so that the auto-renewal can be approved. But we are curious as to how the App Review Team will test our app with new subscriptions as our production server does not support the rapid subscription testing. We do not really want to mess with our running server before everything is ready to support compressed test payments (Especially because our production server is already working with other subscriptions for Android etc).



According to Apples guideline Preparing for App Review “... during app review, your app runs in a mixed production/test environment: it’s production signed and connects to your production servers, but it connects to the test environment for the App Store....”



Should we submit our App linked to our test server to enable Apple to test the compressed payment and then if successful and the auto-renewal is approved- resubmit the App linked to our production server?

Accepted Answer

The app you submit to app review is the one that gets launched. You can't change the app. If you are using the Apple servers to validate the receipt then you typically use the Apple production server first. If the receipt fails with a 21007 code then you use the Apple sandbox server. You can also place a remote flag on your server to circumvent this simple logic and change that flag when your app is approved. You can redirect things within your own server after the app is approved.

From your responce I understand that our production server must suport rapid subscription testing just like our test server does. Am I correct?

No. The sandbox environment will only be used by Xcode and App Review. Only once your App is launched will users be using the production environment. Your problem is how to differentiate a real user from an Xcode user and direct them to a different server. That is a bit tricky to do.

Hello Timbotwo!

We are struggling with a different issue with the subscription creation and maybe you can help.

How did you create a subscription product for testing on the sandbox environment?

We created the product in iTune's "in-app purchases" section where all our other 'non-renewing' products reside.

However, Apple keeps rejecting the subscription product!


As you can imagine, we cannot test it in our binary.

Can you please send tell us where or send the link to create a subscription product for testing purposes?


Thanks in advanced!
Paul.

paulperroni


Sorry for late response.


Dont submit it to Apple till you ready. You can use it for testing and when you ready to submit your app, add that price to your submition.


Hope thats clear.

Don't add the screenshot and then it won't be available for submission for approval. And if you do add the screenshot, don't submit it for approval.

Quick auto-renewal App review question
 
 
Q