Application Loader Errors

Solar2D iOS
#1

I’ve had the worst time trying to submit my iOS app. My android version had no issues and is happily in the Google Play store. Here’s what’s happening. I built a storybook app using Kwik and Corona Starter. Published the build and the development version worked great on various iPads so I moved on to distribution. Published the build (w/ distribution not development) and went to upload in the Application Loader and got the following error:

So came here and searched around and found that I should clear out the Keychain Access and the MobileDevices/Provisioning Profiles folders and download the certificates again which I did. I also requested a new Certificate Signing Request. I then went to Corona Simulator and published the build again and again tried to upload through Application Loader but this time I get the following error: 

I’m at a loss. Nothing has been changed so I’m not sure why the original error went away and this new set of errors has cropped up. I’m not a programmer and this is my first time submitting any apps so I don’t know what I don’t know lol. Any help would be greatly appreciated! 

#2

Can you post a screen shot of your Corona Build screen with all the fields filled out just before you hit the build button?

#3

Here’s the Corona Simulator Build screen before I hit the build button:

#4

Try taking the apostrophe out of the application name (and if it’s in the folder name).

Rob

#5

I tried removing the apostrophe and made sure the folder and application name were the same but still got the same error in the 2nd image I posted. Thoughts? Time to purchase customer support? lol 

#6

Hi @tdemidio,

As an initial test, can you successfully build the Corona sample project “Hello World” using the exact same provisioning profile and certificates? This might narrow down if it’s an issue with your provisioning setup, or with this app more specifically.

Thanks,

Brent

#7

Hey Brent,

I opened up Hello World and was able to publish the build to my desktop from Corona Simulator creating the two files using the same settings without any errors. But to be fair I have been able to do that with my own project. Unfortunately, its the next step of using the Application Loader to submit to Apple that I started getting the above errors. Being a first timer with all of this and not a programmer leaves me at a disadvantage to problem solving skills lol but my guess is it has to do with the certificates but I’m just not sure.

#8

Hi @tdemidio,

I wish this wasn’t the case, but you may need to completely wipe your provisioning setup and certificates and start from scratch with new App IDs and provisioning profiles (none of them with apostrophes are any other non-alphanumeric characters). Sometimes this is the only way to get past some snag in Apple’s system. Fortunately, it shouldn’t take long if you follow the guide and the steps in careful sequence:

http://docs.coronalabs.com/guide/distribution/iOSBuild/index.html

Brent

#9

That’s what I figured. When I go to create everything new from scratch do I have to name it something new? If my App ID is WebstersGeckoGoof will I have to change that to something like WebstersGeckoGoof2?

#10

Hi @tdemidio,

I’d suggest just removing the previous one entirely, then setting up a new one, using a fresh certificate and prov. profile (don’t just use an older certificate to generate a new App ID).

Best regards,

Brent

#11

Are you clicking on the “Upload” button from Corona SDK to launch Application  Loader or are you running Application Loader by hand?
 

#12

running application loader by hand. i tried the upload button a few times when i first tried submitting and it didnt work. got an xml error i believe it said and was told to just open application loader once i published the build instead.

#13

if i create a new app ID will that effect what I’ve done in iTunes Connect? before i tried to publish i went into iTunes Connect to set everything up. will i be able to change the Apple ID and Bundle ID? i want to keep the title of my game what it is right now. thats a concern.

#14

iTunes Connect should be talking to your developer provisioning portal.   The Bundle ID in iTunes Connect must match what you have in the Provisioning Portal and you must download the profile that goes with that App ID and then use Corona SDK to build against it.  If you are using the wildcard identity, or if you’ve got something in your build settings that’s setting the Bundle ID there, then things can get out of whack.

As to your question, if you create a new AppID it will have a new Bundle ID and you will have to create a new App  in iTunes Connect to match and you likely will have problems with the title of your game.  Though you should be able to change the title of the bad version and then use the title you want on the new version.    That said, I’ve never seen issues between iTunes Connect and the provisioning portal before.  But it’s too easy to mess up getting the right profile into your computer to use.

Can you post new screen shots now that you’ve removed the apostrophe?  Also post your build.settings.

#15

Rob would it be possible to move this conversation offline?

#16

It’s best to keep it here since the whole community can chime in with suggestions.

Rob

#17

Can you post a screen shot of your Corona Build screen with all the fields filled out just before you hit the build button?

#18

Here’s the Corona Simulator Build screen before I hit the build button:

#19

Try taking the apostrophe out of the application name (and if it’s in the folder name).

Rob

#20

I tried removing the apostrophe and made sure the folder and application name were the same but still got the same error in the 2nd image I posted. Thoughts? Time to purchase customer support? lol