FYI, the developer who posted this same problem on stackoverflow, posted this interesting solution:
[ After trying for 24 hours and sending like 10+ builds, I finally enabled bitcode in my project and got rid of sdks(in my case it was GooglePlus) which were not supporting bitcode. My build is accepted now. I’m not aware why Apple has imposed this thing all of sudden. Maybe they did mentioned it somewhere and I failed to pick it up. ]
MDB, the email we all received discusses bitcode failure. This seems to imply that “disabling” bitcode should solve the problem.
Oddly, the stackoverflow developer solved this same problem by “enabling” bitcode. Being that you have an Enterprise version of Corona SDK, does it resolve if you “enable” bitcode when making a build?
You can’t compile if you enable bitcode on enterprise. Corona does not support it.
For anyone else that’s reporting this issue to Apple, it’ll help to streamline the process by providing these answers:
• Steps you took to produce this issue
• Full window screenshots illustrating the issue
• Web browsers that you were able to reproduce the issue in
• Web browser version numbers
• What’s the OS version
• What’s the xcode version
In my initial email, I included the xcode version, screenshots, a copy of the email, that I was using Corona SDK, and how the error occurred. This information apparently wasn’t enough since they emailed me back requesting the information above. I’m not sure how web browsers affect this issue, but ¯_(ツ)_/¯
sounds like apple is just trying to find any excuse other then their own mistakes as the reason for these errors.
i can’t upload App. on Store because Ituness Connect: Processing…???
Because Server Corona enable bitcode ??
I’m getting the same error.
Corona simulator version: Build: 2016.2906. Any feedback on how to avoid it?
This is the list of plugins in use:
[“plugin.googleAnalytics”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true, android=true, }
},
[“plugin.OneSignal”] =
{
publisherId = “com.onesignal”,
},
[“plugin.google.play.services”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true, android=true, [“android-kindle”]=true }
},
[“CoronaProvider.gameNetwork.apple”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true, [“iphone-sim”]=true },
},
[“plugin.facebook.v4”] =
{
publisherId = “com.coronalabs”
},
[“CoronaProvider.ads.iads”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true }
},
[“plugin.google.iap.v3”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { android=true }
},
@oquesada It does not matter what plugins you use, apps without plugins yield the same result. On a side note, Apple replied today to my support request. Sent a ton of screenshots, multiple steps to reproduce the issue, a link to this forum, a signed IPA, and thoroughly explained what the issue was.
Hello,
I just received the below response from iTunes Connect. I contacted iTunes Connect based on the face that @tntwickey said the code level support told @tntwickey to contact iTunes Connect. @tntwickey, do you have the reference case number you used? I can reply to Lucretia with the case number to avoid an endless loop.
Message from Apple:
Thank you for contacting Apple Developer Program Support. My name is Lucretia and I’m following up with you regarding your recent email about the app thinning and bit code issue.
We did receive the information you provided the previous advisor. Although we will admit the Apple Developer Program only offers administrative support for developer program memberships, we definitely will try our best to assist you.
Technical Note 2432 does provide some great troubleshooting steps you can try. If those steps were unsuccessful, please submit your request to Apple Developer Technical Support at:
https://developer.apple.com/support/technical/
Our coding level support would be glad to assist you. Please don’t hesitate to let us know if you have any questions or need further assistance. You can reach us via phone, Monday through Friday, 9:00 a.m. to 7:00 p.m., central time, at 800-633-2152 or by replying to this email. You can reference case number 100019595273. Best regards, Lucretia Apple Inc.
Follow-up: 647490501
Hello Tim,
Thank you for contacting Apple Developer Technical Support (DTS). We provide support for code-level questions on hardware & software development, and are unable to help you with your question.
[…]
If you are not able to find the information you need in the iTunes Connect Developer Guide and you are still not able to resolve your issue, please direct your inquiry through the iTunes Connect Contact Us system:
<www.apple.com/itunes/go/itunesconnect/contactus>
Submitting an inquiry through the iTC Contact Us system will expedite your response time from the proper Apple representative.
This is where I contacted iTC
Thanks @tntwickey!
If other people that have received a response want to post their ticket numbers, I’ll forward them to Apple. I want them to understand it’s not just one or two people experiencing this issue. The squeaky wheel gets the grease!
Does anybody call them =)? Maybe it will be more productive?
Hello everyone, I need to get an update in to fix my app for iOS 10 and that’s why I’m on here so much. Here’s the latest reply from Apple:
Hello,
Thank you for your email to Lucretia regarding the message you received from The App Store Team. My name is Maegan, I’m a senior Advisor, and I will be happy to continue to assist you.
I understand from your email that you received a message, when submitting your build to iTunes Connect:
"While processing your iOS app, App Name, errors occurred in the app thinning process, and your app couldn’t be thinned. If your app contains bitcode, bitcode processing may have failed. Because of these errors, this build of your app will not be able to be submitted for review or placed on the App Store. For information that may help resolve this issue, see Tech Note 2432.”
I can completely understand your concern with this message and wanting to obtain additional information to resolve this issue. As Lucretia stated, we provide only administrative support for members of the Apple Developer Program, so I may not be able to troubleshoot this issue for you, however, I can provide some suggestions of things to try.
First, did you and your team attempt the troubleshooting from TN2432? If so, what were your results?
Secondly, have you contacted Corona SDK to request a verification that your binary does not include any Bitcode?
Here are a few additional documents I found regarding Bitcode:
This section of the iTunes Connect Developer Guide will provide information on why you may want to use Bitcode and how to disable it, if you do not.
This section of the guide explains App Thinning and using Bitcode in your app. It also provides additional information on Slicing and On-Demand Resources.
After reviewing this information, if you are still encountering an issue, you may try to submit a new build to iTunes Connect and see what happens. From the forum posts you provided developers have either been able to get past the message when uploading a new build, while others are finding technical issues in their app that are causing the error.
You may also consider reviewing the Apple Developer Forums:
https://forums.developer.apple.com
You can post questions and share thoughts with fellow developers and Apple engineers, which may be beneficial to obtaining additional troubleshooting steps.
Let me know if you are unable to resolve your issue after reviewing this information and I will see if there are any other suggestions I can provide.
Thank you, for your assistance. I hope the information in this email is helpful. If you have any additional questions or concerns, feel free to reply to this email and let me know. I’m happy to help.
Best regards,
Maegan
Apple Inc.
@Corona, are we 100% sure it’s nothing to do with Corona? I’ve tried the latest daily builds and latest public build to no avail.
I tried the exact same build, same code, same everything except build number using enterprise and had the same issue. Previously submitted about 10 days before on that app without issue. Clearly something changed on apple’s side.
I understand where Apple is coming from. They cannot support 3rd party products any more than we can. They are going to make 100% sure it’s not our problem before they are going to push this on.
Are we sure its not just us?
First, what was working isn’t working. We don’t go back and change builds. Only daily builds have new features. Since you could submit with 2906 before and now you can’t and with us ruling out plugins, it has to be a change on Apple’s side. It also happened right as the started accepting iOS 10 builds. While that is potentially a coincidence, it’s a mighty big one.
It’s happening to Native developers:
https://forums.developer.apple.com/thread/43126 – Note this is a thread from March when this problem happened once before, but if you scroll down you find new people reporting it.
https://forums.developer.apple.com/thread/62370
https://forums.developer.apple.com/thread/62266
https://appdevelopermagazine.com/4390/2016/9/9/Developers-Experiencing-Apple-App-Store-Upload-Trouble-With-App-Thinning:-Tech-Note-2432 – Apple Developer Magazine story about the problem.
It’s happening to Adobie Air developers:
https://forums.adobe.com/thread/2205923
That’s a lot of evidence that it’s not just us. But it’s potentially circumstantial enough that it might be us which is why Apple is pushing back on this.
We are taking this very seriouslly and I’m pretty sure we’ve been trying everything we can think of, including submitting purely native apps (no Corona involved). If we can come up with a solution, we will and we will let you know what that is.
Rob
After submitting 4 builds with the same code but different build number (using Corona build 2906), it seems I’m also experiencing this issue. Something’s definitely up with Apple. I submitted an update for one of my apps before the Apple event last September 7 (using the same setup I have now) and it processed nicely. After the event, THIS happened.
What’s confusing is that the error message simply said “There was an error importing this build” and they did not even say what the error was.
I also filed a ticket but no response yet.
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.
