FWIW, I’ve got the same issue submitting my app today and again tonight. This was a first upload attempt.
“There was an error importing this build” - no explanation what the error is.
Nail
Rob, thank you for the update. Although my release schedule is behind every day this isn’t resolved, I’m spending this time to improve the game before release - so just know, I’m counting on you to notify us here when you have updates. I appreciate you and the Corona team for doing all that you can. Kindly as always. -Troy
Heres hoping Apple get it sorted when they get to work today. Just experienced the app thinning error myself this morning so I am glad I’m not alone with it.
phil_s, welcome to the CLUB =)
Same here . and i think Apple will fix it on its own
Hello,
Same problem here. We hope the fix will come soon . Rob, thank you very much to warn us when you have information on the matter and an eventual issue.
I’m stuck here as well…
Tried with different daily builds.
As far as I have read there’s no workaround…
Trying different daily builds isn’t going to help. This is an issue on Apple’s side they have to fix, or if we can come up with a work around it will be in a new daily build that doesn’t exist yet. We will let you know if we can solve this on our end. Periodically try to resubmit in case Apple fixes this.
Rob
Just wanted to update an app and now this. Things really stay interesting! 
Just wanted to add that I also got this error over the weekend when submitting a new build - exactly the same as everyone else, nothing changed in the build apart from a few lines of Lua and bamm - no more app 8-(
Glad to see Corona are taking this so seriously (and secretly glad others are getting the same error so I know it’s nothing I messed up).
Looking forward to a quick resolution, many thansk to Rob & the team for providing the extra support.
Hello,
Just another update, Apple has requested that I send my .ipa file to them along with additional screenshots. They also said this:
Once I receive this information, I will notify my teams and further investigate the error. I currently cannot confirm if the issue is from an Apple server or if it’s from the build information we’re receiving. I can confirm that I do see a note in every build submitted that there is an issue with App Thinning. I cannot verify where that issue is occurring, however.
I’m happy to heard that they are at least considering the chance it’s on their servers.
Has anyone had any further news on this at all? We can’t submit any builds at all either. Getting very frustrating now - been 5 days and can’t get an update out. Thanks.
After nearly 6 days of this problem with Apple, I believe XCode 8 might resolve this problem - but until Corona upgrades our SDK, we won’t know. The reason I have come to this assumption is because A) Apple’s responsiveness has been uncharacteristically vague; B) iOS 10 goes LIVE today; and C) a previously hacked version of XCode 7 was responsible for the huge security leak that was announced last month. Of course, I could be wrong. But why else would this be happening? This kind of issue is consistent with Apple’s pattern to protect the platform, often making changes that can impact our Apps each time they upgrade iOS. If my speculation is nothing more than worthless conjecture, thank you for allowing me to vent my frustrations with Apple here in our beloved forums. I must believe that Corona Labs is an Enterprise level Apple Developer (the $299 tier), and thereby is both getting the best support from Apple, while also working day and night to solve this for us all.
Not according to Apple. They support apps build with xcode 6 onwards.
Same problem here. I am curious to know if anyone succeded in submitting a build the last couple of days?
2 apps submitted before our problem has been rejected this morning.
Message from apple :
Performance - 2.5.1
Your app uses or references the following non-public APIs:
setResult
The use of non-public APIs is not permitted on the App Store because it can lead to a poor user experience should these APIs change.
Rob, do you think it could be the same problem?
Thanks a lot for your great support!
@GBF Comm, Can you post (via copy/paste) the entire message about the non-public APIs? As far as I know we are not using any non-public APIs. This is a new/different error and probably should be another thread.,
Rob
Same problem. Fortunately i finally found this thread. Too bad i found it so late though…
Rob : could it have something to see with the CFBundleSupportedPlatforms (iPhoneSimulator) ? Tn2432 mentions : “Failure handling apps where the CFBundleSupportedPlatforms key in an Info.plist file is missing or specifies an invalid platform”
According to this thread (http://stackoverflow.com/questions/32726939/error-itms-90542-invalid-cfbundlesupportedplatforms-value), " iPhoneSimulator" might not be a proper value.
d.
@dimd, this thread is discussing an email sent by Apple after submitting an app complaining about not being able to thin the app because of bitcode. The folks reporting this problem haven’t mentioned anything about a CFBundleSupportedPlatforms key error. Please create a new thread so we can discuss your and avoid hijacking this thread.
Thanks for understanding
Rob
@GBF Comm, please start a new thread. I need more information before I can go to engineering. I don’t want to hijack this thread.