Also, we can’t use an older Corona build to publish to iOS right? It will produce the same error?
Daily build worked for me. Had problems with trying to re upload a prerelease build but then changed the CFBundleVersion.
CFBundleVersion = “1.0.4.2”,
CFBundleShortVersionString = “1.0.4”,
Apple is my “favorite” platform!
@puppymodz. and every one else, as Walter pointed out, this is on Apple. They set the rules and in this case they created a rule that even their own software won’t pass. You really need to follow Walter’s advice and email Apple. He provided you a form letter and an email address to use. Apple is a company that responds to the volume of complaints they get. If only one or two of you email them, it won’t have the impact of a couple of dozen of you emailing them
There is a good chance that if you all complain enough, they will back out the change on their end and you can then submit. It’s important that you do this.
Rob
Filing a complaint…
Yes please everyone send Apple the email, I’m sure that will be the quickest way to get a resolution, problem is I’m sure they’re also busy with fixing debugging their iOS 8 and planning their next conference.
But anyway, volume of complaints is probably going to get them to respond, since the more apps we make and sell the more revenue they’ll generate as a whole.
And open up a ticket using Apple Bug Reporter, post a # here and maybe when enough accumulates Corona could then give apple a call…
Here’s mine 18257869
@xnailbender, I had no problem removing a binary I uploaded to the App Store. In the new iTunesConnect website there is a “-” (minus sign) next to the build that was uploaded and selected for the App. Click on the “-” and it removes the build selected for that App. This was after I uploaded a build, selected it and clicked Save.
@Tom,
Thanks for the update.
I saw the “-” / delete sign and selected it and saved, but it would not remove, maybe they fixed the interface today, which they would have to do sooner or later. Forgot to mention I tried the delete button in my first post.
Nail
What will Apple say to that email? Will they somehow enable me to upload my app?
P.s has anyone received a reply yet?
I just did my part by sending an email over to Apple. Since I’m on Basic I’m pretty much stuck as well.
@puppymodz regardless whether or not Apple replies, you should still send an email to them using Walter’s template. As Rob mentioned, the more people complain about the issue the more likely Apple will take notice.
@puppymodz, the idea is to make Apple aware of this problem and have them fix it, hopefully with a sense of urgency. With all this happening over the weekend and the big product announcements on Tuesday, I doubt developers will hear back until mid-week. But if you don’t do it, you won’t know their response.
Rob
I sent it . When i sent it i assumed that they had some switch they could flip that would let me submit my app.
Hi Rob
Full appreciate you not being able to provide a date. Personally based on past experience I cant see this being soon. But in the interest of customer service can I make a suggestion.
Can you not just make the daily build (the one with the fix) available to basic users for download ?
Just put it on the web site somewhere and publish the link.
It solves every bodies problem that has been hung out to dry like myself, costs you nothing and would be really really appreciated by “basic” users" who are stuck at the moment and are likely to be for some time.
Comments anybody
???
Allowing everyone to download the daily build with the fix would be really helpful. I had an app in the submission process that I can no longer upload. I’ve sent Apple messages about the issue through every avenue possible, and they haven’t done anything yet.
I’m almost certain that Engineering has considered all their options. It’s probably not possible to just make a daily build available to basic subscribers.
Rob
I would rather wait for Apple to settle down and give the guys time to get Corona to a stable state, even though I have an app ready to go and am anxious to get it on the store 
I think as developers we can ALL agree that you do not want to rush a project out the door without having fully tested it, INCLUDING full regression testing.
I agree with the decision to hold off on a public release until it is once again stable and the team has had a chance to make sure no new bugs are introduced. Let the daily-build guys be the guinea pigs 
(no offense to the Pro+ users, someone has to be the beta tester lol)
Guys you don’t want to rush your app to the store only to have hidden bugs revealed or have previous functionality borked and thus ruining the first impression of your app to users or piss off your current users. Most apps (games) have a pretty short shelf-life anyway…you don’t want to have a bunch of pissed off users because you were too anxious to get your app published and then it never get a chance.
Publishing Apple apps is an exercise in patience anyway.
Android has spoiled us with the quick submission process. Even though the Apple process is slow and frustrating, it DOES push you to make sure your app is pretty rock solid before getting it out there.
So kudos to Rob and Walter and the team for deciding to wait for a stable release (but hurry up, please LOL)
I used that email @Walter wrote and got this response from Apple.
Hello Edi,
Thank you for contacting App Store Developer Support regarding the API error when you try to submit your binary using App Loader.
In order to further assist you, I will need you to reattempt to upload your binary with App Loader and if it produces the error again, press the button labelled "Send ".
This will submit the error log in its entirety to us and we will be able to reply with guidance on how to fix the issue.
I understand your time is valuable; your assistance in this matter is greatly appreciated. Once the requested information is received, your issue will be further investigated.
I did that like 10 times. 
Well that’s a positive!
Rob