com.coronalabs.template App Store Publishing error

Solar2D General Questions/Discussion
#61

Hi tap32.  Thank you SOOO  much.  That solved it.  The reason I didn’t do this before was that just before upgrading to Yosemite etc I had done this.  However, when you said that it made me wonder if the keys work differently in yosemite.  No idea if they do, but I revoked my production certificate and regenerated a distribution provisioning profile.  Installed that and Bob’s your uncle it worked!  So thankful, that was driving me potty.

For others’ benefit, these were the steps I went though (approximately):

  • Running Mountain Lion and whatever XCode was on there

  • Had loads of issues uploading to apple

  • Revoked and regenerated profiles etc

  • Upgraded to Yosemite, the latest version of XCode etc

  • Still had problems (see above)

  • On tap32’s advice, revoked the certificates again

  • Uploading now works

Thanks again and good luck everyone.  The force may need to be with us at the moment I fear!

D

#62

BG2J43EA88.com.coronalabs.template … same problem please help me thanks 

#63

You need to tell us more. What version of Corona SDK are you building with?  What is the full error message?  Have you ever successfully deployed an app?

Rob

#64

Corona SDK - Version 2014.2393 (2014.8.5) please check attached file this is error 

#65

this is attachment 

#66

Can you try and build the Hello World sample app and try and deploy it?  You can always reject it.

Can you post a screen shot of your Corona SDK build screen?  Please do not blur out things.  I need to see what you’re seeing.

Can you post a screen shot of the folder showing the files in the folder with your main.lua?

#67

I am still getting the same error after revoking and creating a new distribution cert / profile. It does not seem to identify the code signing entity: 

ERROR ITMS-9000: “Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: ‘BG2J43EA88’ for the key ‘com.apple.developer.team-identifier’ in ‘Liechtenstein Gemeinden Geographie Speicher.app/Liechtenstein Gemeinden Geographie Speicher’”

Any help is appreciated.

#68

Can you post screen shots of your Corona SDK build screen just before you hit the build button?  Please do not blur out any values.

#69

I have attached the screenshot before performing the build. Hope it helps.

#70

It sounds to me like the profile isn’t based on the right App ID in the provisioning profile.  It looks like you have a release profile that’s trying to use the Team identifier instead of a unique App identifier.

Rob

#71

For what it’s worth, a $9.99 app called AirSign seems to fix the problem.   I revoked and rebuilt my certificates over a dozen times with the com.corona.templates error still rearing it’s ugly head every time. Simply resigning the apps with AirSign using the same exact provision made the errors go away.  Doesn’t solve the problem with Corona itself, but hopefully this can help save someone’s project deadline.  I missed mine yesterday trying to solve this problem and just discovered AirSign today.

#72

The great thing about Airsign is that it also does beta entitlements correctly! Still bewildered as to why Corona doesn’t!

#73

Engineering is working on it.

Rob

#74

I’m having the same issue out of the blue with build 2468. Anyone found a reliable fix? 

#75

I’ve just tried it with an app that I’ve previously successfully uploaded and got the same issue. First it says the Application account information is incorrect, and then it progresses to these issues. Will try again with both Apps tomorrow

#76

Hmmm… the old deleting everything and re-importing everything worked. I wonder what was causing the issue?

#77

One thing that did happen was that I had created a new distribution profile on another computer and then imported it. I use XCode to manage all of that, but maybe it doesn’t correctly replace the old keys or provisioning profiles? Also I upgraded Mac OS

#78

Hi

I’m afraid I’m having the same problem.  The app has been deployed to the Apple store loads of times and there are only very minor code changes in the version I’m uploading now.

I had Mountain Lion installed until yesterday.  I have upgraded to Yosemite now because of other other errors in uploading to the store.  I have also updated XCode to the latest version in the hope that might help.  I also updated to the latest version of Application loader Version 3.0 (620).  The app has been tested on local devices and runs perfectly.

I am running Corona Simulator Version 2014.2393 (2014.8.5)

When uploading the app I get the attached errors which all (apart from the 64-bit thing) seem to reference the coronalabs.template issue.

Any advice on how to get around this would be most welcome.

Thanks very much in advance  :slight_smile:

Dougi

#79

Hi Dougi,

I think in the end I just revoked my distribution certificate and generated everything again. It’s working now!

#80

Hi tap32.  Thank you SOOO  much.  That solved it.  The reason I didn’t do this before was that just before upgrading to Yosemite etc I had done this.  However, when you said that it made me wonder if the keys work differently in yosemite.  No idea if they do, but I revoked my production certificate and regenerated a distribution provisioning profile.  Installed that and Bob’s your uncle it worked!  So thankful, that was driving me potty.

For others’ benefit, these were the steps I went though (approximately):

  • Running Mountain Lion and whatever XCode was on there

  • Had loads of issues uploading to apple

  • Revoked and regenerated profiles etc

  • Upgraded to Yosemite, the latest version of XCode etc

  • Still had problems (see above)

  • On tap32’s advice, revoked the certificates again

  • Uploading now works

Thanks again and good luck everyone.  The force may need to be with us at the moment I fear!

D