Transfer third version of iOS app via iTunesConnect before app live

Question

We have an iOS application that has been approved for release with its version 1.0 and , we have introduced a small update of version 1.1, which has also been approved, and is the "Pending Developer Version". The date set for the first availability in Rights and Pricing is a month later.

The question is: is it possible to send another update (say, version 1.2) without making the application work live earlier? That is, if we click "Release this version" on the page of version 1.1 of the application, will this really lead to the immediate launch of the application in the application store? Or will iTunes appreciate the date in "Rights and Prices", and the application will remain unreleased, and we can send another update to the slot with an open version?

A copy in the Apple Developer Support Guide seems to indicate that the application will go live when you press Release Release, but this is not clear:

R. 72:

Availability Date

The date your app will be available for in-app purchase. Keep. If your application has not been approved by Apple before this date, your application will live as soon as it is approved.

This is a global date and applies to all selected territories. if you change this date, it applies to all versions of your application. If you are creating a new version of your application, you can use the release management function version to control the date your new version is released in the App Store.

page 73:

NOTE. You can use the version control to update applications. This is not available for the first version of your application, since you already have the ability to control when your first version goes live using the "Availability date" option in the "Rights and Prices" section. If you decide that you do not want to release a ready-made release for version developers, you can reject your binary to send a new one. You are not allowed to miss the whole version.

Answer 1

We just tested it, and it seems that after you click "RELEASE THIS VERSION" in version 1.1, the application is actually still held until you set the release date in the "Rights and Prices" section (if you haven’t yet released the app). Thus, you can continue to send additional updates to the application before publishing it to the public.

Answer 2

I received this response from iTunes Connect on March 12, 2014, indicating the date of availability in the "Rights and Prices" section set on 4/1/14 (April 1, 2014):

I understand that you have set the available version 1.0.1 date of your application to 4/1/14. If you click the “Release this version” button before 4/1/14 this will override the available date and the application will go live for 24 hours from the date on which you clicked “Release This Version '.

Version 1.0.1 will appear as an update for your application. For more tips and visibility information for your application, please refer to the App Store Resource Center - Marketing Resources:

https://developer.apple.com/appstore/mac/resources/marketing/index.html

Thus, it says that MobileVet tested around 7/25/12, as their application was delayed until the release date (availability date?) Is set in the "Rights and Prices" section.

From Marketing on the App Store, I got this answer when I asked if updating the application before release would affect the initial impact:

This will not affect your potential placement of objects. I would advise you to update so that your application is maximally possible at release.

Answer 3

When you submit a new version, you are usually asked if you want to release it immediately or wait for the manual version, usually before downloading. I think this is what you want to do.