...
You've validated that the app and any necessary server-side resources are ready to go in the production environment. Now it's time to cross the i's and dot the t's. ...or the other one.
- You need to supply a full set of metadata in the app’s Versions pane, as described in Creating an iTunes Connect Record for an App. This can (and should) be started before, or at least in parallel with, the Production smoke test steps above. Getting all the required assets ready takes time.
- If this is an update to an existing app, notify the support team (currently Amy Truong <amy.truong@sagebase.org>) of the upcoming release and of any significant changes included. If it's a new app, notify them in what ways this app differs from previous apps.
- Submitting the app for final review is explained in Submitting the App to App Review. Always submit with the option for us to pull the trigger once approved, not for automatic release upon approval.
- Double check the territories in the Availability section. In most cases, the only territory will should be the United States.
- Once approved by Apple, meet with all parties involved in the app (server team, client team, researchers, support, QA) and get a final go/no-go from each. Only release the app when the response is unanimously "go." Best to do so on a day early in the week when most of the engineering team will be on hand to deal with any unexpected problems that arise.
...