Bundle ID invalid trying to upload to iTunes

Solar2D General Questions/Discussion
#41

The first one is because you actually have a file called Icon in your project folder with no extension.  Apple is trying to make use of this.  I haven’t tracked down what’s creating it, but I’ve seen several people report it.  One forum posted that they thought Glider (the IDE) might be creating it.  You will likely need to open a terminal session and use command line commands to get into your folder, use the “ls” command to find it and the “rm” command to remove it.  For the one project someone sent me we we were first trying to figure this error out, I actually used Sublime Text’s file list to right-click and Delete the file. 

Now for the missing 152x152 I’m not sure what to say unless you don’t really have a 152x152 in the folder or it has a file name case mismatch.

Rob

#42

Hi Rob: I have Sublime Text, but I don’t understand your instruction to “right click on file list and delete the file”. What file am I opening in my folder? The config.lua, build settings, main.lua? Thanks!

John

#43

Hi Rob: here’s my list of icons in my build folder. Did I name them OK? Appreciate your help! Thanks! John

Icon-29.png
Icon-29@2x.png
Icon-72.png
Icon-72@2x.png
Icon-76.png
Icon-76@2x.png
Icon-152.png
Icon-152@2x.png
Icon-Small-40.png
Icon-Small-40@2x.png
Icon-Small-50.png
Icon-Small-50@2x.png

#44

For the first question, look for a file in the file list named “Icon” without an extension (no .png) and delete it.  You can ctrl-click or right-click and in the flyout menu there should be a “Delete file” options or something similar.

For the second question, Apple has a lot of flexibility in how to ID and provide the required icons, but under the “Follow this recipe and it will always work for you” method, we wrote up this in our guides:

http://docs.coronalabs.com/guide/distribution/buildSettings/index.html#appicons

If you copy/paste the build.settings block and follow the sizing guide lines as listed in that guide exactly, you won’t have problems.

For instance you list an Icon-152.png and Icon-152@2x.png file.  The 152 icon is really the Icon-76@2x.png file (76 * 2 = 152) and you don’t need a 304px icon (what 152@2x would in theory represent).   Follow the guidelines with zero variance and you should be good to go.

Rob

#45

Hi Rob: I was able to delete the “Icon” file using Sublime Text following your instructions…THANKS! Just saved the modified app file, re-zipped and uploaded it to iTunes and it took successfully! Yeah!!! Will read the link you provided about icon guide lines. Thanks for all your help! You’re AWESOME!!! Have a great day! Cheers! ~ John (-:slight_smile:

#46

Rob: now I’m getting this error message:

We have discovered one or more issues with your recent delivery for “Sound Sort Blends 2”. To process your delivery, the following issues must be corrected:

Invalid Signature - Make sure you have signed your application with a distribution certificate, not an ad hoc certificate
or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target.

Once these issues have been corrected, go to the Version Details page and click "Ready to Upload Binary."Continue through the submission process until the app status is “Waiting for Upload.” You can then deliver the corrected binary.

I have double and triple checked and tried SIX different submissions, with the same error message! I’m at a lost… any ideas? Grrrrr!!!

Thanks! I’m taking a break and getting some air! ~~~ John )-:

#47

This error is very straight forward.  You picked the wrong provisioning profile when you built the app.  There are three types that you can create in the Apple Provisioning Portal:

1.  Development  – Device Testing only

2.  Distribution - Ad Hoc – Device Testing, and Internal deployment (like internal to a business)

3.  Distribution - Store – This is what has to be used to upload to the store.

The error above says you used ether type 1 or 2 when you need to use 3.

Rob

#48

Hi Rob: I checked and it was set up for Distribution to the Store. I’ve deleted and rebuilt my profile certificate, CRS, and provisioning profiles, but I still cannot get it to upload due to this Code Signing error. I feel like I’m running around in circles!!! Very frustrating! Any other suggestions? Thanks! ~ John )-:

#49

Have you rebooted, restarted Corona SDK?  Cleaned out your ~/Library/MobileDevices/Provisioning Profiles folder and re-downloaded your profiles?

Rob

#50

Hi Rob: rebooted, restarted Corona and cleaned out provisioning profiles like you suggested. Strange thing is that the upload goes up fine, no errors. But in two minutes, I get the iTunes message that the binary rejected with the following message: Invalid Signature -Make sure you have signed your
  application with a distribution certificate, not an ad hoc certificate
or a development certificate. Verify that the code signing settings in
Xcode are correct at the target level (which override any values at the
project level). Additionally, make sure the bundle you are uploading
was built using a Release target in Xcode, not a Simulator target. If
you are certain your code signing settings are correct, choose “Clean
All” in Xcode, delete the “build” directory in the Finder, and rebuild
your release target.

 

So now what? This does not make sense! Thanks! ~ John

#51

Rob: I’m pulling my hair out on this submission. I’m now on my 14th rejection with the same error about “Invalid Signature”. I have COMPLETELY deleted my provisioning profiles and rebuilt it; deleted and redid my CSR certificate; downloaded “Watchdog” so that it completely cleans out my X-Code libraries before uploading. I made sure my X-Code targets are in “release” mode. I removed the “Icon” with Sublime Text and compressed a new zip file to upload. NOTHING seems to work and I really, really, need to get this update for my app into the store! Can you please help me? Thanks! ~ John )-:

#52

I asked around and here are some possibilities.

  1. Make 100% sure you’re not using an AdHoc profile.  To test, try and install your .app bundle on your device.  If it installs, it’s an AdHoc profile.  You cannot install a “for the store” app directly through Xcode’s Organizer.

  2. If that fails, try building the HelloWorld sample and upload it and see if you get the same error.

  3. Make sure you are not putting things like the CFBundleIdentifier in your build.settings.  You have to make sure the profile you picked matches the profile iTunes connect is expecting.

Rob

#53

Rob: Checked profile and it is NOT AdHoc as it did not install. Cleaned out X-code Organizer and deleted any project folders. Build only has CFBundleIcon.  See screen shots of my profiles, error message, and build settings. I’ve checked the Bundle ID 20x times and it is correct!!! Appreciate any other ideas on what I’m doing wrong here!

John )-:

#54

Rob: I just got into Terminal to look at my soundsortblends2.app file and made two screen shots. Does the “Resources.car” file need to be renamed? Are the Icon images OK? Any other ideas? My first version was 1.0 and my second version is 2.0, is that OK? Thanks!

~John

#55

Rob: Making some progress…last submission says that my Bundle is not signed, so I went into Terminal and sure enough, it is NOT signed (see screen shots). Should I just delete everything and start all over again with new keys, provisioning profiles, distribution certificates, restart my mac computer? I’m using Corona Simulator 2013.2100 Is that OK? Thanks! ~ John (- :slight_smile:

#56

Well it certainly wouldn’t hurt to clear out and start over, just lets check a couple of things.

You should have two certificates:  A development certificate and a distribution certificate.  You next need to make sure you create a provisioning profile for app store distribution that uses the distribution certificate.

As far as the Icons go, you still seem to not be matching them up with our recommendations.  Your Icon.png and Icon@2x.png are what we recommend for the iOS 6 iPhone and Retina iPhone.   Your errors are still being reported as missing a 152x152.

One last question, are you running Application Loader by hand or are you clicking the “Upload to app store” button after the build?

If you are clicking the button, running it by hand may solve the problem.

Rob

#57

Rob: I cleared everything out and started over. Made a development profile, but I cannot make a “distribution” profile; it says I have duplicates and to delete them, but I don’t have any! Look at the screen shots and you’ll see I only have the development profile. Any idea what’s causing this? I’m running Application Loader by hand, and NOT clicking “Upload to app store”. I always do it manually. I’ll fix the icons. Thanks! ~John

#58

Rob: when I use Sublime Text to remove the “Icon” file in the soundsortblends2.app, it also removes the “code signing” as I verified that in the Terminal command before trying to upload. How do I get around that?  Or is there another way to remove the “Icon” and yet retain the code signing for submission? That seems to be the only thing holding up my upload now. Thanks! John

#59

Don’t remove it from the .app folder.  Remove it from your folder where the main.lua is.  If you remove it there, it won’t make it into your app bundle.  When you try to change the .app bundle, the signing is going to fail because the bundle has been modified.

Rob

#60

Rob: Sorry, but I don’t understand when you say to remove it from the folder that has the main.lua file. As you can see from my screen shot, there is no “Icon” file. It generates on it’s own when I build the submission file in Corona Simulator and is embedded into the SoundSortBlends2.app file that when I open up in Terminal or Sublime Text, it shows that “Icon” is in that .app file. I apologize for my ignorance on this issue. Thanks! ~John