Hi,
Facing issue while uploading on itunes using application loader .Error screenshot attached below.
Please suggest how to resolve this problem.
I suggest that you check your certificate chain.
Check that your bundle identifier is correct. Check that you have created a distribution provisioning profile connected to your bundle and that a distribution certificate for your appleID/company is valid and have a key that resides on the computer you have built the app on.
(In Xcode5 you can goto Xcode/Preferences/Accounts…, that helps a lot, in my opinion.)
@jensto thnks for suggestion i checked this Xcode/Preferences/Accounts … and it has both development and distribution certificate now.
Now i have another issue that is “invalid code signing entitlements” . I am declaring bundle identifier in build setting of corona .
What I have found out, the keychain never deletes any old entries. If you have invalid certificates that have the same name, Corona can get confused. (It could be the order of appearance in the keychain). Delete these or export them to play it safe.
Make sure you have a keypair connected to your valid iOS distribution certificate. This certificate must be the one set in the app’s distribution provisioning profile. This is what connects you/your computer to your developer account, and completes the certificate chain.
Hope this can give you a clue for a solution…
By the way… The certificates must not neceserly be invalid. It could be they do not have a valid key connected to them. So export them to be on the safe side.
There is no expired certificate and private key connected to both developer and distribution certificate . Tell me one thing , i declared bundle identifier in build Setting of corona should i do this or not.??
I looked in some of our projects and we have not set this up in build settings.
(Guess it is connect through the actual build process and the signing certificate selected.
We have had this issue before but with developer signed apps, and it has been resolved
by removing older certificates in the keychain.)
I suggest that you check your certificate chain.
Check that your bundle identifier is correct. Check that you have created a distribution provisioning profile connected to your bundle and that a distribution certificate for your appleID/company is valid and have a key that resides on the computer you have built the app on.
(In Xcode5 you can goto Xcode/Preferences/Accounts…, that helps a lot, in my opinion.)
@jensto thnks for suggestion i checked this Xcode/Preferences/Accounts … and it has both development and distribution certificate now.
Now i have another issue that is “invalid code signing entitlements” . I am declaring bundle identifier in build setting of corona .
What I have found out, the keychain never deletes any old entries. If you have invalid certificates that have the same name, Corona can get confused. (It could be the order of appearance in the keychain). Delete these or export them to play it safe.
Make sure you have a keypair connected to your valid iOS distribution certificate. This certificate must be the one set in the app’s distribution provisioning profile. This is what connects you/your computer to your developer account, and completes the certificate chain.
Hope this can give you a clue for a solution…
By the way… The certificates must not neceserly be invalid. It could be they do not have a valid key connected to them. So export them to be on the safe side.
There is no expired certificate and private key connected to both developer and distribution certificate . Tell me one thing , i declared bundle identifier in build Setting of corona should i do this or not.??
I looked in some of our projects and we have not set this up in build settings.
(Guess it is connect through the actual build process and the signing certificate selected.
We have had this issue before but with developer signed apps, and it has been resolved
by removing older certificates in the keychain.)
The problem is with the “Certificates and KeyChain” in App ID’s. Here’s what I did to fix it. Hopefully this will help anyone who’s having this issue.
1- Backup all your current AppStore Certificates. 2- Remove all your current AppStore Certificates. 3- Copy your certificate and provisioning profiles to this path
**/Users/{YOUR-USERNAME}/Library/MobileDevice/Provisioning Profiles/**
4- Re-install your AppStore Distribution Certificate. 5- Re-submit through Application Loader.
Worked for me 
Are you using the version of Application Loader that Corona SDK starts up after building the app and you hit the Upload to App store button?
If so, cancel that dialog so it does not run Application Loader and then run Application Loader by hand. If that doesn’t fix it, we will dive more into the root cause.
Thanks
Rob
The problem is with the “Certificates and KeyChain” in App ID’s. Here’s what I did to fix it. Hopefully this will help anyone who’s having this issue.
1- Backup all your current AppStore Certificates. 2- Remove all your current AppStore Certificates. 3- Copy your certificate and provisioning profiles to this path
**/Users/{YOUR-USERNAME}/Library/MobileDevice/Provisioning Profiles/**
4- Re-install your AppStore Distribution Certificate. 5- Re-submit through Application Loader.
Worked for me
Are you using the version of Application Loader that Corona SDK starts up after building the app and you hit the Upload to App store button?
If so, cancel that dialog so it does not run Application Loader and then run Application Loader by hand. If that doesn’t fix it, we will dive more into the root cause.
Thanks
Rob