When I try to publish the App by application loader.
It was always ok before but not this time. What’s the hell, anybody know it?
I am also getting the exact same error using build 2014.2404 and build 2014.2393a
Chiming in with a “me too”, have tried build 2401 as well with the same error.
For the record I took a look inside the IPA file and CFBundleShortVersionString does not exist in the info.plist
I wonder if this is a change on Apples end getting ready for iOS 8, making an optional field mandatory? that said, I would have that field was mandatory.
I found an old reference to CFBundleShortVersionString and it was not a mandatory field, which could explain why Corona don’t appear to include it. Possibly Apple are now enforcing it. Speculation of course.
Time to raise a support ticket about it. I’ll do that now.
Is this something that just came up today?
Tried to upload a version created today and got the same exact message as well.
Seems to be pretty recent. I raised a support ticket so hopefully we will hear soon.
Ok so I made an edit to my build.settings file as such:
CFBundleShortVersionString = “1.0”,
Where the “string” matches my version number in the iTunes Connect and also the build version when composing using Corona. So far the app was accepted by iTunes Connect, hopefully it’ll get approved this way, not going to know of course for another week until they review the app but hopefully this is a simple solution.
Hi @PickionGames,
Yes, I was going to suggest this approach for the moment. We’ll check into it though and see what steps may be necessary on our side.
Thanks,
Brent
Just to let everyone know that we added the CFBundleShortVersionString fix to the next Daily Build (2405 and higher). This will set the version string to the value set in the Version field in the iOS build window.
As for previous builds of CoronaSDK (including the 2393 Public Release), you will need to manually add the following to the plist section of the build.settings file.
CFBundleShortVersionString = “1.0”,
You need to change the “1.0” to match what you have in Version field.
I did a Google search of this issue and found a number of other sites reporting the problem. It looks like Apple starting requiring this plist setting two days ago.
Here’s an example build.settings based on the HelloWorld sample:
Ya gotta love the fast resolutions here! Thanks!
I still have it - http://forums.coronalabs.com/topic/50942-certificate-not-installed-20142428-20140908/
even with latest corona. Any suggestions or what to do - whould be great.
This thread’s issue is related to: http://coronalabs.com/blog/2014/08/21/ios-building-issue/
However, in preparation for iOS 8, Apple is making more changes to their servers. This is causing other issues which are affecting all developers, not just Corona developers:
I am also getting the exact same error using build 2014.2404 and build 2014.2393a
Chiming in with a “me too”, have tried build 2401 as well with the same error.
For the record I took a look inside the IPA file and CFBundleShortVersionString does not exist in the info.plist
I wonder if this is a change on Apples end getting ready for iOS 8, making an optional field mandatory? that said, I would have that field was mandatory.
I found an old reference to CFBundleShortVersionString and it was not a mandatory field, which could explain why Corona don’t appear to include it. Possibly Apple are now enforcing it. Speculation of course.
Time to raise a support ticket about it. I’ll do that now.
Is this something that just came up today?
Tried to upload a version created today and got the same exact message as well.