Contingencies for IAP + App Review Process

In preparing to submit our first in-app purchase along with a new app binary, I want to be fully aware of the contingencies should the purchase be rejected, or incurs a delay due to developer action required.


Specifically:


- If the IAP is delayed requiring developer action, can the app binary be approved and released independently?

- Similarly, if the IAP is rejected and we decide to appeal, can the app binary be approved and released independently?

- Can the IAP submission be revoked like an app binary so that the app binary can be released by itself, leaving the IAP to be re-submitted with a future app version/binary?

Replies

Delay for whom? The dev or the app's users?


From the IAP FAQ:


"When an application is approved, the developer must also approve the application for release to the App Store. On approval, the application ID is activated to the App Store. The same activation is required for the in-app purchase identifiers and can only take place once the application is activated. In some cases, the activation of the In-App Purchase identifiers may lag up to 48 hours following the activation of the application.


If the developer does not approve the release of the production application to the App Store, then any new in-app purchase identifiers will not be activated. This is an issue when a developer wants to verify the application prior to activating it on the App Store. If the desire is to test the in-app purchase process for the new items, the application must be activated to the App Store. This is only an issue for new in-app purchase identifiers in a corresponding application submission. Once these in-app purchase identifiers have been activated, application updates to the submission will find that these in-app purchase identifiers are validated, even if the update is not activated."