We have an iOS app which has been approved for release with its version 1.0 and we submitted a minor update, version 1.1 that was also approved, and is \"Pe
We just tested this and it appears that after you press "RELEASE THIS VERSION" on the 1.1 version, the app is actually still held back until you set the release date in the "Rights and Pricing" section (as long as you haven't yet released the app). So it is possible to continue submitting further updates to an app before releasing it to the public.
When you submit a new version you are usually asked if you want to release it immediately or wait for manual release, usually just before uploading. I think this is what you want to do.
This answer from iTunes Connect I got on 12th March 2014, with availability date in "Rights and Pricing" section set to 4/1/14 (1st April 2014):
I understand that you have set the available date of version 1.0.1 of your app to 4/1/14. If you click the 'Release This Version' button prior to 4/1/14 this will override the available date and the app will go live within 24 hours of the date that you clicked 'Release This Version.'
Version 1.0.1 will be displayed as an update to your app. For more tips and information on gaining visibility for your app, please refer to the App Store Resource Center - Marketing Resources:
https://developer.apple.com/appstore/mac/resources/marketing/index.html
So it states the opposite of what MobileVet experienced around 7/25/12, as their app was held back until the release date (availability date ?) set in "Rights and Pricing" section.
From App Store Marketing I received such a answer when I asked if updating the app before the release would influence initial exposure:
This will not affect your potential feature placement. I'd suggest you update so your app is a best as possible on release.