I do the opposite and let Xcode do the work, since Xcode knows where it wants them…
We’ll have to wait and see if the OP can shed some more light on this issue armed with the advice we’ve given…
Hi,
Finally I got that to upload to the app store.
The certificates are all fine, the problem was not with the certificates but strangely with the name of the app. What is more confusing is that the same name was used from xCode and it worked not when build with Corona.
However Apple immediately send an email, which starts that process over again.
Your delivery was successful, but you may wish to correct the following issues in your next delivery:
Missing recommended icon file - The bundle does not contain an app icon for iPhone / iPod Touch of exactly ‘120x120’ pixels, in .png format for iOS versions >= 7.0.
Missing Push Notification Entitlement - Your app appears to include API used to register with the Apple Push Notification service, but the app signature’s entitlements do not include the “aps-environment” entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the “aps-environment” entitlement. See “Provisioning and Development” in the Local and Push Notification Programming Guide for more information. If your app does not use the Apple Push Notification service, no action is required. You may remove the API from future submissions to stop this warning. If you use a third-party framework, you may need to contact the developer for information on removing the API.
If you would like to update your binary for this app, you can reject this binary from the Binary Details page in iTunes Connect. Note that rejecting your binary will remove your app from the review queue and the review process will start over from the beginning when you resubmit your binary.
So, that starts the process over again…
The project has two files of *exactly* 120x120 called Icon-60@2x.png and Icon-120.png which were created for the earlier version of the app and worked, however this time around it did not recognize them. Do I have to create CFBundeIcon entries to resolve that?
UPDATE : I guess I have to add to the build.settings file it is no longer Automagically added as it used to be before.
and what about the ‘aps-environment’ I am only using local notifications not remote, and nothing has been set in the app id entitlements that suggest that I would be using any notifications.
so thanks and suggestions on these two new issues?
Update : From the discussion here http://forums.coronalabs.com/topic/34789-non-public-api-usage-missing-push-notification-entitlement-email-from-itune-store/?hl=%2Bmissing+%2Bpush+%2Bnotification+%2Bentitlement I get that this issue can be ignored for now.
Do I have to update a new build with the 120x120 icon or are solutions to both the issues - Ignore, as AppLoader showed the icon issue as a warning not an error while uploading.
Great news! Finally it worked :lol: !
Just curious though…
Did your app name have anything other than alphanumeric characters?
The Push notification thing can be ignored. Everybody seems to be getting that warning.
I’d say the same could go for the icon warning. However I’d fix that just to be on the safe side. Even though it’s just a warning, you never know if you get a reviewer who’s following the book “200%”. Just specify all your icons in CFBundleIconFiles in build.settings and you should be fine.
Ingemar and Rob, firstly thanks for all the time and effort you put into this, really appreciate that.
No the name had no accented characters or spaces or numbers or punctuation marks and NOT even foul language or banned/censored words.
This was actually quite strange since with that name I could get xCode to upload and work fine, but not otherwise.
I have told the client that if it gets rejected, we’ll fix it otherwise “Don’t fix what’s not broken” 
I will set that, could I also make a request - if the backend at the build servers could add these by default it could save the additional hassles. Especially since Apple makes it mandatory to use these recommendations for iOS7. I personally feel that in a simple application we now have like more files specifying icons - repetitively in so many sizes.
Again, thanks for that - I hope not to face those kind of issues again, but if I do - I know one person to turn to
@007 I have this same exact problem. How did you solve it exactly? Where did you change the name of your app? Here are things that I did recently that may have set this off…
My IOS Distribution Certificate expired 2 weeks ago so I created a new one today.
My Corona Pro recently expired and I just purchased Basic today
What about updating an older app, can you do that?
Good News and Not such Good News.
The App got approved by Apple and the update is available on the app store (must be the WWDC backlog clearance)
Now for the not such good news…
The app breaks Graphically speaking, it is the Graphics 1.0 and 2.0 issue despite the ‘graphicsCompatibility = 1’
I am using the camera and the images snapped do not work. There is no way to debug on the device with Corona so I cannot pin point where and what the issue is.
All my client wanted was to change some text and to simply do that,
- Apple wants you to compile with the latest edition of xCode and support all the lastest, my client does not want to support iOS7
- Corona to fix a workflow pushes Graphics 2.0. Can you not just change the workflow with the earlier version? A lot of fixes in older apps might simply require adding text or simple stuff, no dazzling Graphics 2.0 enhancements, so why force a change and what could have been a 5 minute task becomes a week’s worth.
This is like the iPad Retina issue, where the apps just broke and were displayed oddly on the screen.
Who can I bill for this? The client?? What’s their fault, the problem lies with the new version of CoronaSDK that uses Graphics 2.0.
Sometimes FREE is more expensive than paid for.
@russm305, I do not know what your app does, so when you update it (if it was written with an older version of corona) be prepared for interesting times ahead trying to debug and fix the issues in code.
As for the certificates, I had to delete everything and recreate the certs. Make sure that you remove everything, because Apple has buggered this process, when XCode manages your profiles, it creates TeamID’s and don’t know why, it keeps changing that everytime. I have a bunch of TeamID’s and NONE of them match the ID provided to my account when I create the basic certificate to associate these profiles with.
So let xCode take charge and create everything for you, Apple wants to control the entire process.
Not a happy camper - sheer waste of time and resources on getting a simple thing fixed.
@007 i built with build 2139. I just deleted and re-created all the certificates still didn’t help. You said above…
“The certificates are all fine, the problem was not with the certificates but strangely with the name of the app. What is more confusing is that the same name was used from xCode and it worked not when build with Corona”
…so did you have to change the name of your app, if so where? What about your App Distribution Profiles? Did you use ones you had crated previously or did you have to re-create App Provising Profile for the App?
If for example your app is called ‘clock’ and is not being accepted by App Loader, then try to use ‘clock y’ instead or ‘clock er’ and in the CFBundleName you can set it display ’ clock’
I did not have to re-create any certificates, but if you have changed the keys then you might have to recreate all of the same. However if you want to update your app, you do not have to re-create any new certificates, the same ones will work. Do check that you have updated the version otherwise Apple will not let you uppload the app.
Im sorry where would I change it to ‘Clocky’? In the Application Name when I am creating the IOS build from the simulator?
Where is CFBundleName?
-
The name of the app is generally the name of the directory (in CoronaSDK) where you have the lua files, so if you call it myapp-phaseII-tempfiles, then that is the name it will show by default and compile to that name.app
-
The CFBundlexxxx flags are plist flags and are set in the build.settings file3
-
When you say that your app is being rejected, if you can share, what is it called? Is it a reserved word of any kind?
On what I suggested in the last post, Corona prompts the name of the directory as the name of the app, now your app could be called Clock but since iTunes is not accepting it, you change it to clocky when you go to build the app. But it would be quite odd to see that on the homescreen (after the app is downloaded by an user) that is where you set the CFBundleDisplayName to Clock so the name shown under the icon will still show clock, but the app name is clocky.app
Hope you get to upload your app soon.
Thank you for the help. It turns out what I had to do was go into Keychain Access and delete old and duplicate development and distribution profiles.
How the hell is a someone supposed to know what to do when I had an error exactly like yours…
“The bundle <bundle> at bundle path <application.app> is not signed using an Apple submission Certificate”
When you say that your app is being rejected, if you can share, what is it called? Is it a reserved word of any kind?
“World Cup”
Can you believe 2 these generic words are not available for me in my title?
So I changed it to “World Soccer Cup”…keeping my finger crossed!
I’m sorry you’re having troubles 007, I would suggest dropping back to the last build that worked for you, except that Apple has changed the requirements so our public build has been updated to comply. While you pointed this thread out in another, I’m not sure you and that poster are having the same issue, and others are successfully uploading with this build.
What does your build.settings look llke?
Did you reboot after clearing out your Key Chain?
Rob
Hi Rob, Thanks for the quick response, that helps in building some confidence.
The last build that I had used was 2013.1202 which apparently will not work as it does not support the iOS7 whatever required for xcode 5.1.x compatibility, so I had to move to the current public build of 2014.2189
My Build.settings looks like this
settings =
{
orientation =
{
content = “portrait”,
supported =
{
“portrait”,
},
},
iphone =
{
plist =
{
--CFBundleVersion = “1.1”,
--CFBundleName = “APPNAME”,
--CFBundleIdentifier = “BUNDLEID”,
--CFBundleDisplayName = “APPNAME”,
--CFBundleShortVersionString = “1.1”,
UIStatusBarHidden = true,
UIApplicationExitsOnSuspend = true,
UISupportedInterfaceOrientations = “UIInterfaceOrientationPortrait”,
UIAppFonts = {
“HelveticaNeue-LigCond.ttf”,
“HelveticaNeue-UltraLigCond.ttf”,
“HelveticaNeue-ThinCond.ttf”,
“HelveticaNeue-HeavyCond.ttf”,
},
--CFBundleIconFile = “Icon.png”,
--CFBundleIconFiles = {
– “Icon.png”,
--}
},
},
android =
{
usesPermissions =
{
“android.permission.CAMERA”,
“android.permission.WRITE_EXTERNAL_STORAGE”,
“android.permission.RECEIVE_BOOT_COMPLETED”,
“android.permission.INTERNET”,
},
usesFeatures =
{
{ name = “android.hardware.camera”, required = true },
{ name = “android.hardware.telephony”, required = true},
},
},
}
All of the CFBundle plist settings are commented to avoid any issues still…
I have rebooted the machine and am trying to update it with he OSX 10.9.3 update and the iTunes 11.2.1 update after which I will try one last time. I have wasted more time and stressed on this than getting some work done.
Things did not used to be like this, they just worked.
Unfortunately, the Apple provisioning process is quite difficult and ever since I started using the product, at least some one about once every couple of weeks have these issues. Its not tied to what build we are on. It seems like it bites everyone at least once. Its bitten me before and it took me a couple of days to finally get it straightened out.
Did you clean out your Your /User/yourname/Library/MobileDevice/Provisioning Profiles/ folder? Did you make sure to get everything of yours in the KeyChain folder (any junk certs laying around can byte you. Sometimes you have to open up things to find hidden gems.
update: Tried a new build after restarting and updating… still the same issue.
I so want it to be some silliness from my side but when the only two things involved are BUILD and selecting the Distribution Cert, there is not much that I can do wrong.
So does that mean I am out to swim with the sharks till a miracle (no pun intended) occurs? I thought there would be a solution to this where there could be a way to sign the .app using xcode and create the .xarchive so that xcode signs it and does not give errors. or something that resolves this issue than hang us out to dry.
What Rob is trying to say is that sometimes it’s our local Xcode/certificate setup that’s causing the issue, and not Corona itself.
I’ve been bitten by Xcode’s quirkiness regarding certificates that I suspect could cause the issues you’re seeing. If it *is* a provisioning profile issue, they can unfortunately be tricky to track down.
Rob’s suggestions above are fully valid in this context, and I’d suggest you try them if you haven’t already.
When I had a similar problem there were duplicate certificates in the keychain that had to be removed before things got back to normal.
@ingemar, thanks for the pitch-in, I have tried all that Rob has suggested and can confirm that it is not the xcode certificate. I would so much want it to be a small silly thing that I have overlooked, but in this case sadly it isn’t.
I think I may have found something. It looks like the new 2189 still isn’t compiling with Xcode 5.1.1.
I’m getting that confirmed.
I’ll post back when I know more.
007,
Just to be clear, when you say you did the steps Rob recommended … did you just clear the profiles from the Xcode organizer window (provisioning profiles) and then re-added them there.
The one way to really eliminate that the issue is not with the apple provisional profiles, is to go to the directory path Rob listed above, and see what you have there. There was a post on the forum a while back that lists the steps fairly well on how to ‘Completely’ clear out the provisional profiles, you may have to ‘re-do’ them at iTunes Connect and then re-enter them into your computer. Then remove and re-enter them in your Xcode and then be sure to select the correct ‘distribution’ profile when you build the app. The there are some steps involving the keychain, but you will have to find that post(I do not recall who posted that).
It is a pain and time consuming series of steps to do all that. If you did not do all those things, and only removed and re-entered the profiles in the Xcode organizer window, then you have not really did the clean up of the provisioning profiles that a few other users have had to do to get ‘what appears to be similar problem you have’ corrected. This possibly includes totally re-doing them provisioning profiles and maybe certificates in iTunes Connect.
*** you should call *apple for any cautions before deleting any provision profiles or certificates you have and re-creating new clean ones.
I hope this helps!