Failed Build: deploy-to-itunesconnect-deliver

Hey there! Our iOS build pipeline works as expected. I just turned on “Submit for review” in Bitrise and now it fails.

I have no idea where to add this information:

The request could not be completed because:

You must provide a first name in the Contact Information section. You must provide a last name in the Contact Information section. You must enter a phone number in the Contact Information section. Make sure the phone number is formatted correctly and try again. The phone number must start with a “+” followed by the country or region code (for example, +44 844 209 0611). The email address must be in a valid format (for example, support@example.com). You must select the level of frequency for each Apple content description in the Age Rating section. You must add at least one screenshot. You must add at least one screenshot. You must add at least one screenshot. You must add at least one screenshot. [en-US]: You must add at least one screenshot. [en-US]: You must add at least one screenshot. [en-US]: You must add at least one screenshot. [en-US]: You must add at least one screenshot. [en-CA]: You must provide an app description for English (Canada). [en-CA]: You must enter one or more keywords for your app in English (Canada). [en-CA]: You must provide a Support URL. There are errors on the page and for 2 of your localizations. You must choose a price tier in <a href="[?]">Pricing</a>.

Deploy failed, error: exit status 1

Hi @jbibla!

This guide should explain the steps you have to take to get started: https://help.apple.com/app-store-connect/en.lproj/static.html

Sorry @bitce — we are all set up with app store connect and release manually quite often. Submitting for review automatically from within Bitrise is not working.

The error message is not helpful. I know information is missing but I do not know where to enter it.

Thanks!

hey @bitce would love your help on this.

Hi @jbibla, sorry for this long silence. Can you paste here the build URL where this is happening? To be honest I’d recommend contacting Apple about this error. I do not see basically any instance of this error happening and this makes it very hard for us to tell why you’re receiving it.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.