Error submitting to iTunes Connect

  • 1
  • Problem
  • Updated 8 years ago
The app runs fine when testing using the developer certificate on an iPhone and iPad, and when using the Distribution certificate it builds fine, but when uploading to iTunes connect I get two errors:

1. ipad: icon.png: icon dimensions (57x57) don't meet size requirements
2. App Store Submission: Application failed codesign verification

I've had this happen before and after recompiling on PG Build several times, it finally worked previously, but so far no luck this time. Is Build having issues again?

My App ID is 100415

Thanks

John
Photo of John Saya

John Saya

  • 68 Posts
  • 7 Reply Likes

Posted 8 years ago

  • 1
Photo of Yi Ming Kuan

Yi Ming Kuan

  • 1840 Posts
  • 78 Reply Likes
Seems like it's mistaken your iPhone icon for the iPad one. Can you try changing the iPhone icon configuration in config.xml to this?

-yiming
Photo of John Saya

John Saya

  • 68 Posts
  • 7 Reply Likes
Hi Yiming,

The last successful submission from PG Build my config.xml file looked like this:



<icon src="icons/ios/icon_57.png" gap:platform="ios" width="57" height="57" />
<icon src="icons/ios/icon_72.png" gap:platform="ios" width="72" height="72" />
<icon src="icons/ios/icon_114.png" gap:platform="ios" width="114" height="114" />



This time I used how the docs show and removed all of the gap:platform="ios" except on the 72 dpi icon. So it now looks like this:



<icon src="icons/ios/icon_57.png" width="57" height="57" />
<icon src="icons/ios/icon_72.png" gap:platform="ios" width="72" height="72" />
<icon src="icons/ios/icon_114.png" width="114" height="114" />



This fixed the icon error, however I'm still getting the "Application failed codesign verification" error message. My certificates have never changed, so maybe PG Build is using the wrong certificate somehow?

Thanks

John
Photo of John Saya

John Saya

  • 68 Posts
  • 7 Reply Likes
Any updates on what could be causing this? At this point it's impossible to submit any updates to iTunes from PG Build.

Thanks

John
Photo of Yi Ming Kuan

Yi Ming Kuan

  • 1840 Posts
  • 78 Reply Likes
Hi John,

This is most likely caused by an error in your certificates.

Can you verify that you have proceeded with the following steps? https://build.phonegap.com/docs/ios-b...

Also verify that your .p12 and .mobileprovision certificate are still valid in your iOS Developer account.

-yiming
Photo of John Saya

John Saya

  • 68 Posts
  • 7 Reply Likes
Hi Yiming,

My certificates expire May 2013 according to the iTunes Provisioning Profile. Everything builds fine using the distribution certificate on PG Build, and always has, since my certificates have not changed in months. I even tried to upload them again to PG Build, but I get the same error when submitting to iTunes. I can only assume PG Build isn't signing the app with the correct certificate.

Thanks for your help,

John
Photo of John Saya

John Saya

  • 68 Posts
  • 7 Reply Likes
Ok, so originally I was using a Mac with Snow Leopard on it, and it refused to let me upgrade the Application Loader. Assuming this was the issue, I got a hold of another Mac with Lion on it, and the submission was accepted by iTunes.

So, for all those with the dreaded "Application failed codesign verification" error, it's likely your Application Loader or Mac needs to be updated if your certificates are ok.

Thanks PG Build Team for an excellent product and service!

John
Photo of Matt Chatterley

Matt Chatterley

  • 2 Posts
  • 0 Reply Likes
I'm having the same problem, but with the latest version of Application Loader (2.8) - and a pair of p12/provisioning files that I know work and are valid - because I built and submitted a version of the same app with them last week.

Therefore to my mind this can only be a defect in PhoneGap Build?
Photo of Matt Chatterley

Matt Chatterley

  • 2 Posts
  • 0 Reply Likes
And some luck - for anyone else suffering. I had failed to update the version number in the config.xml - presumably iTunes wasn't clever enough to tell me this and gave me an obscure error instead (either that or changing config.xml forced PhoneGap to do a clean build).