We have previously uploaded an IPA and published it to TestFlight. Now we want to submit it to Apple for review, but not automatically publish it. The task fails because the app's store version hasn't already been created in App Store Connect. It appears that fastlane deliver requires the --build_number parameter to be specified if you want it to create a new store version. This number is in the IPA file.
Expected: The task creates the necessary store version for the app using the build number in the IPA file.
Actual: The store version isn't created, and the task eventually fails. We have to manually log into App Store Connect to create the store version of the app that matches the version we are submitting. So much for automating the release!
Required Information
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Apple App Store Release
Environment
Issue Description
We have previously uploaded an IPA and published it to TestFlight. Now we want to submit it to Apple for review, but not automatically publish it. The task fails because the app's store version hasn't already been created in App Store Connect. It appears that fastlane deliver requires the --build_number parameter to be specified if you want it to create a new store version. This number is in the IPA file.
Expected: The task creates the necessary store version for the app using the build number in the IPA file. Actual: The store version isn't created, and the task eventually fails. We have to manually log into App Store Connect to create the store version of the app that matches the version we are submitting. So much for automating the release!
Task logs
Our task definition:
Log: