38

I'm working on an iOS app that last week had a build successfully uploaded to iTunes Connect and then distributed for testing via TestFlight.

This week, I updated to Xcode 7.3 and now when I update the same project (with changes just for Swift 2.2 compatibility and some other bug fixes I did), I am able to archive and submit the build through Xcode, but then instead of processing and receiving an email that the build is ready to test, the build shows up in iTunes Connect like this, with the displayed error message. I don't receive any email or other error message about what could be wrong:

enter image description here

I haven't found any other solutions searching online about this issue. I've gotten in contact with Apple and the issue has been escalated but haven't heard back yet.

Update - Apple has escalated to engineering, awaiting response.

Update 2 - Apple replied that this is a known issue with Xcode 7.3 and Bitcode, see answer below for solution.

Eric Aya
  • 69,473
  • 35
  • 181
  • 253
sschale
  • 5,168
  • 3
  • 29
  • 36
  • What happens if you delete a previous build from itunes connect and re-upload it from an old archive that was compiled with your old x-code version? – DudeOnRock Mar 24 '16 at 00:54
  • Hitting the same issue did you resolve it? Application loader was no help. – Rich Dominelli Mar 24 '16 at 02:18
  • This has hit me recently as well. With the number of people reporting this in the apple forums and stackoverflow we can almost certainly conclude it's a problem on Apple's side. – chris Mar 24 '16 at 15:28
  • Did you find any solution ? Seeing same issue since 2 days. – Bhumeshwer katre Mar 24 '16 at 17:45
  • 1
    Thanks for keeping us posted on this. – chris Mar 25 '16 at 11:46
  • This issue seems to be fixed now. I have successfully uploaded a tvOS build (with bitcode) yesterday. – flopr Apr 06 '16 at 10:07
  • I can confirm, builds are now working - I'll make a note about it being resolved in the answer. Thanks @flopr – sschale Apr 08 '16 at 01:31
  • Looks like the issue is back. Xcode 8 and I'm uploading an app that doesn't have bitcode. :-( – Daniel T. Oct 18 '16 at 18:19
  • @DanielT. - I'd contact Apple directly (and let us know if they say what it could be - this error message is nonspecific), but do check for bit code in your settings as it can be enabled in a couple spots. – sschale Oct 19 '16 at 06:21
  • @sschale I incremented the build number and tried again and it worked. – Daniel T. Oct 19 '16 at 10:11
  • Possible duplicate of [All Build for iTunes Connect, there was an error importing this build](https://stackoverflow.com/questions/35146731/all-build-for-itunes-connect-there-was-an-error-importing-this-build) – kris May 23 '17 at 20:41

5 Answers5

24

Apple has replied that this is a known issue with Xcode 7.3 and Bitcode. So, I disabled including Bitcode uploading with the binary and it successfully processed!:

enter image description here

You do not need to disable it for the entire project, but it works that way too (tested with both project Bitcode enabled/disabled with Bitcode upload inclusion disabled).

Edit: Builds as of 4/7/16 are now successfully uploading and processing with Bitcode.

sschale
  • 5,168
  • 3
  • 29
  • 36
  • I disabled bit code just as you instructed and it worked fine. My app just got successfully uploaded and is now in a "Processing" status. Hopefully, disabling bit code does not negatively impact my app when i go to production. – drvannostran98 Mar 29 '16 at 21:03
  • You cannot disable bitcode for AppleTV targets. Might also apply to WatchKit targets. – flopr Mar 30 '16 at 18:11
  • Very true - there have been separate threads about this for tvOS in the past on apple developer forums. – sschale Mar 30 '16 at 19:13
10

I received this error for the first time yesterday.
I did not have bitcode turned on.
I had no other message beyond the iTunes "There was an error importing this build".

Today I bumped up the version number and resubmitted and it worked.

enter image description here

kris
  • 11,868
  • 9
  • 88
  • 110
  • This should be the first thing to try - I'm using fastlane to deliver and hit this problem yesterday. Today I just re-ran fastlane which auto-bumped the number and it succeeded, no other changes. – CupawnTae Aug 15 '17 at 08:47
  • I ran into this problem after I accidentally closed my Mac while the app was being uploaded to iTC. Bumping the build number and resubmitting (without closing my Mac) was successful. – mharper Apr 10 '18 at 18:10
  • I only needed to bump up the build number and it worked for me – Ben Mar 13 '20 at 00:08
3

Random problems like this happen to me sometimes and instead of uploading from the Xcode organizer what I do is use the organizer to export a build and then use Application Loader (available from the Xcode menu -> Open Developer Tool) to actually upload it. Sometimes it helps and sometimes it doesn't, but it's worth a try.

dbmrq
  • 1,451
  • 13
  • 32
1

Just in case if aforementioned solution not worked for you try the following. Cause none of the listed solution worked for me.

  1. Check for the Xcode Version. It should not be a BETA release.
  2. If still getting issue the upload it using Application Loader. Don't use CMD + Space to launch Application Loader. It might open old or different version Application Loader. Which leads you to ambiguous bugs. Launch from the Xcode menu Xcode -> Open developer tool -> Application Loader solves the problem. Please make sure you do it from the version of the Xcode that you used to build your app.

Cheers!! :)

shim
  • 9,289
  • 12
  • 69
  • 108
Rahul Verma
  • 688
  • 5
  • 17
1

Give it some time(an hour or two). It auto-solves.

May or may not work be a good advice, but this is what worked for me.

atitpatel
  • 3,104
  • 1
  • 24
  • 34