Thanks @Rob. Can confirm it is happening on our Enterprise apps and normal apps. All mixed configurations. Something changed on Apple's servers.
Jump to content
Hello @Rob, please feel free to delete this post - https://forums.coronalabs.com/topic/65456-an-error-importing-this-build-for-itunes-connect/. I didn't find this thread until after I did deeper searching.
Today, the Apple Developer Support team took on our case #100018694114 and asked me to provide the iTunes connect email and my IPA file that stopped processing.
This tells me that Apple's support engineers had not yet connected with the proper developers by the end-of-day today. I can only hope that CoronaLabs is ahead of us on this and that the Apple support department is so large that it will take them a couple of days to consolidate numerous support requests.
My point here is that we should never assume that others have reported such an error.
@troylyndon, I'm the enterprise user that explicitly turned off bitcode so the app thinning would hopefully continue. Just reiterating here that it didn't work and as Rob has indicated - it's not just Corona users but spread throughout several platforms.
A post went up today on ADM's website https://appdevelopermagazine.com/4390/2016/9/9/Developers-Experiencing-Apple-App-Store-Upload-Trouble-With-App-Thinning:-Tech-Note-2432/ and we reached out to Apple ourselves for comment but no word back just yet.
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?
For anyone else that's reporting this issue to Apple, it'll help to streamline the process by providing these answers:
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:
@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.
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:
Community Forum Software by IP.Board