com.coronalabs.template App Store Publishing error

Solar2D General Questions/Discussion
#1

I’m in the process of updating one of my apps. I’ve encountered an issue that I’ve never seen before when trying to sign and publish an app using Corona to application loader publishing tool.

[disclaimer] I have done this literally hundreds of times before…

For some reason when I sign this app today I’m getting the following error when I try to submit the signed app to the Apple app store.

 

Error ITMS-9000 :Invalid Code Signing entitlements. The entitlements in your app bundle signature do not match the ones that are contained in provisioning profile. According to the provisioning profile, the bundle contains a keyvalue that is not allowed “[BG2J43EA88.com.coronalabs.template]’

Obviously that is not my bundle identifier and I have no idea where it is picking that up unless it’s getting it from the Corona building servers and basically signing it with the wrong provisioning profile that I am telling it to use.

Anyone else is having trouble publishing to the Apple app store?

#2

Did you try the suggestion listed here?

http://forums.gamesalad.com/discussion/32731/invalid-code-signing-entitlements

#3

I just did a build for distribution with 2076 and didn’t have a problem.  That’s an odd error.  Is BG2J43EA88 an Apple ID of your’s?  I don’t have access to our developer account to see if that’s one of ours.  Is that build ID coded into a build.settings maybe?

Rob

#4

iCloud is off, so I’m afraid that isn’t it. @Rob - apps build fine, did you try and submit an update though to an app in the iOS app store? Rob, my appID is 406423598, I have no idea where the Corona build is coming up with that BG2J43EA88, but more alarming is the  com.coronalabs.template after it.

Richard

#5

Oh, forgot to mention I’ve recreated my certificate, and distribution profile at least a dozen times now to no avail…

I’m running the latest daily build as well (was a few weeks old and I thought that was it, so I updated the Corona SDK, still no publish love…)

Richard

#6

It submitted fine.  I had a missing screen shot, but no other errors about bundle problems.  I’ve forwarded this to engineering.

Rob

#7

Bizzare! I’ve been trying all day on and off, with all variants of re-boots, re-provisioning, etc… 

What is your build --> Publish process, maybe that is the difference?

Rich

#8

I have the same issue this morning, have once again recreated my distribution certificate, checked the bundle ID (and checked again), along with creating a brand new distribution provisioning profile. No matter what I try, I keep getting the com.corona labs.template error that the entitlements are wrong. Please see the attached screenshot…

signing-error.png

#9

This is a show-stopper for me? Rob, any progress on this one?

Richard

#10

Can you try building and submitting one of the sample apps (you can reject the
binary).   Are you running Application loader by hand or are you still
letting Corona launch it?

What OS are you running (10.8 10.9?)

What version of Xcode do you have installed?

What version of Corona SDK are you running?

Can you drop back to an older version and try?

Thanks

Rob

#11

xCode Version 5.0.1 (5A2053)

Corona Version 2013.1260 (2013.11.13)

OSX 10.9

Letting Corona simulator launch app loader, but have tried it manually as well.

I will drop to an earlier version of Corona and let you know, will also try to build and publish a demo app -

Thanks!

Richard

#12

Just downloaded the latest stable build of Corona and my app won’t build using it. I guess I’m using a function or two based on a daily build. So I went down to a slightly older version (Version 2013.1255 (2013.11.4)) and just copied my build settings file over to the demo physics “bridge” app. Runs in simulator, so I built, and signed using my distribution provisioning profile - got the exact same com.coronalabs.template entitlement error…

Still up against a wall…

#13

Can you build the sample app with the build.settings that came with the sample app?

Can you post the build.settings you are trying to use here?

Thanks

Rob

#14

Hi Rob, here is my build.settings file…

– build.settings

settings =

{

orientation = {

        default = “portrait”, 

        

    },

 android =

        {

                versionCode = “4”

               

        },

    

    androidPermissions =

    {

         “android.permission.INTERNET”,

             

    },

    iphone = 

    {

        plist =

        {

            UIApplicationExitsOnSuspend = false,

            CFBundleIconFile = “Icon.png”,

            

            CFBundleIconFiles = 

            {

               “Icon.png”, 

               “Icon@2x.png”, 

               “Icon-72.png”, 

            },

            

            FacebookAppID = “159719600833118”,

            

            CFBundleURLTypes =

            {

                {

                    CFBundleURLSchemes =

                    {

                        “fb159719600833118”,

                    }

                }

            },

                UIPrerenderedIcon = false,

                CFBundleDisplayName=“Scan”,

                CFBundleIdentifier=“NaughtyorNiceScan”,

                CFBundleVersion=“1.4”

                

        },

    },

}

#15

I just tried to  build and publish Shape Tumbler - no go. Same com.coronalabs.template error . All I changed was in the build settings:

},

                UIPrerenderedIcon = false,

                CFBundleDisplayName=“Scan”,

                CFBundleIdentifier=“NaughtyorNiceScan”,

                CFBundleVersion=“1.4”

So that I could sign it with my own provisioning profile.

#16

You don’t need those lines in your build.settings.   If you don’t provide them, it will pick up the version number from the dialog box.  It will pick up the name that goes under the icon from the Folder name that the main.lua is in and for the CFBundleIdentifier it will pick that up from the provisioning profile.  The only one I would consider leaving would be the CFBundleDisplayName if your folder with your main.lua isn’t named what you want. 

I’ve found setting the others leads to issues.

That’s why I wanted you to build a sample app to rule your build.settings out of the way.

Rob

#17

This is the way all of my build settings files are for my over 200 apps published. I can’t see that it would be an issue but just for grins and chuckles I’m going to try it - I’m at my END with it. I’ve been trying everything this morning…

#18

Just removed everything except for the CFBundleDisplayName, no go. No matter WHAT I do - I get the com.coronalabs.template error. I even searched my entire mac for anything containing that string of text and can’t find a single vestige of it…

Richard

#19

Just to make sure, you have tried one of our sample apps, like Hello World with it’s build.settings file (no edits)  and you’re getting this problem?

I’ve asked engineering a couple of times to look at this, but it’s the weekend.  I’ll stay on them, but I wouldn’t expect a response until Monday at the earliest.

It just about has to be something local to your setup.  I can’t think of what it might be.  There have been a few Mavericks related issues to building, but they’ve all been cleared by clearing the keychain and downloading fresh keys, certs, profiles.   There was a bug we fixed related to Mavericks and the XCode simulator, but there is no reason any of our profile information should be in yours.  

So just to clarify for the engineers when they do look at this:

  1. You were working before Mavericks and have not worked since.

  2. You are using 1260 and have dropped back a couple of daily builds and are still experiencing the problem.

  3. You are hand running Application Uploader

  4. You have run a test without your build.settings using one of our sample apps.

also to humor me, from the command line, use the “cd” command to change to the directory where your .app and .zip file are, then cd into your app’s. .app folder (.app’s are just directories) and from there do a :

find . -exec grep -i com.coronalabs.template {} ; -print

(spacing is important in that command) and see if it can find the string in any files in the bundle.  It won’t find it in any encrypted data (which sadly may be where it is) but it’s worth a try.

Rob

#20

The horse animation demo app does the same thing. Here is the result from the grep command…

MACDaddy-2:horseanimation.app rharris$ find . -exec grep -i com.coronalabs.template {} ; -print

grep: .: Is a directory

grep: ./_CodeSignature: Is a directory

grep: ./CoronaResources.bundle: Is a directory

grep: ./FacebookSDKResources.bundle: Is a directory

grep: ./FacebookSDKResources.bundle/Contents: Is a directory

grep: ./FacebookSDKResources.bundle/Contents/Resources: Is a directory

grep: ./FacebookSDKResources.bundle/Contents/Resources/en.lproj: Is a directory

grep: ./FacebookSDKResources.bundle/Contents/Resources/he.lproj: Is a directory

grep: ./FacebookSDKResources.bundle/FBDialog: Is a directory

grep: ./FacebookSDKResources.bundle/FBDialog/images: Is a directory

grep: ./FacebookSDKResources.bundle/FBFriendPickerView: Is a directory

grep: ./FacebookSDKResources.bundle/FBFriendPickerView/images: Is a directory

grep: ./FacebookSDKResources.bundle/FBLoginView: Is a directory

grep: ./FacebookSDKResources.bundle/FBLoginView/images: Is a directory

grep: ./FacebookSDKResources.bundle/FBPlacePickerView: Is a directory

grep: ./FacebookSDKResources.bundle/FBPlacePickerView/images: Is a directory

grep: ./FacebookSDKResources.bundle/FBProfilePictureView: Is a directory

grep: ./FacebookSDKResources.bundle/FBProfilePictureView/images: Is a directory

Binary file ./HorseAnimation matches

./HorseAnimation