21

I upload my build to app store, after that it show error in Activity.

This is the error shown

Any one help me out.

vikash1307
  • 272
  • 2
  • 12
  • 1
    Can you share EMAIL which iTune would have sent to you (to Account which is having this iTune Account) – Chatar Veer Suthar Feb 02 '16 at 06:45
  • they sent regarding, my app review. how they will test my app. that was long time back. now i want to upload new binary and facing this issues. – vikash1307 Feb 02 '16 at 06:55
  • @vikash1307 whats the reason for this. I am also facing this issue. – sateesh Feb 18 '16 at 09:27
  • 1
    @sateesh, actually my app version was 1.1.7 and i updated to 1.1.13. So iTunes consider that, it was lower version then previous version. It is necessary that you upload a higher version number than previously used. For example, 1.1.71 and 1.1.8 are considered higher version numbers, but 1.1.69 and 1.1.13 are both considered lower than 1.1.7. – vikash1307 Feb 18 '16 at 10:45
  • @vikash1307 your build versions are showing 1.3 and 1.4. And you are telling about 1.1.7 . Am i mistaken about version. How do we know the problem is it . Please let us know. Thanks for your reply. – sateesh Feb 18 '16 at 11:49
  • @sateesh, when you create your new app version , that time you need to check ,That should be always greater than previous version. When you upload binary to App Store it will you bundle version. – vikash1307 Feb 18 '16 at 13:24
  • @vikash1307 how do you know the error actually it is. Have you called to apple or some thing else like trail and error. – sateesh Feb 18 '16 at 13:29
  • @vikash1307 our build versions are proper. So I just want to know the proper way to find the solution. – sateesh Feb 18 '16 at 13:29
  • 1
    @sateesh, ya i sent a email to apple through my apple account and i got response from them. – vikash1307 Feb 19 '16 at 05:59
  • @vikash1307 thanks a lot for your response. I will follow the same. – sateesh Feb 19 '16 at 09:02
  • @sateesh and what is a solution? I have some problem. – alexmorhun Mar 19 '16 at 12:32
  • @alexmorhun in my case it a weird issue. Google maps library has been corrupted. the apple is giving a weird message for this. I go through the apple forums and lot of stack overflow. there are various reasons for this issue. I hope its better to contact apple . – sateesh Mar 19 '16 at 14:39
  • @alexmorhun in the project and targets set enable bitcode to NO. – idris yıldız Mar 19 '16 at 18:54
  • 4
    I'm voting to close this question as off-topic because [we are not customer support for your favorite company](//meta.stackoverflow.com/questions/255745/). – Machavity Apr 27 '17 at 21:56

3 Answers3

5

SOLVED!

Go to Build Settings > Search for "bitcode" > Turn Enable Bitcode to No

This will fix it. Also, if you are apprehensive about disabling bitcode, don't worry. Apple describes bitcode as follows:

Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the App Store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store.

You don't really need to enable it. Read more about bitcode here.

That's it.

Your build should go through now.

Community
  • 1
  • 1
Anish Kumar
  • 1,465
  • 16
  • 20
  • 1
    I was struggling with this error for couple days and Apple didn't react on support request (so far). I uploaded several version numbers (1.1.1, 1.1.2), but this didn't have impact - all builds finished with "there was an error importing this build" Finally I tried this solution and during upload to AppStore switched off flag "bitcode" (in the upload dialog). Now I have my build processed without errors – Nick Entin Mar 30 '16 at 07:57
  • Bitcode cannot be disabled for tvOS. Xcode says "target 'XXX' has bitcode disabled (ENABLE_BITCODE = NO), but it is required for the 'appletvos' platform" :( – flopr Mar 30 '16 at 17:45
  • @flopr you're right, in tvOS you probably need it. Let me try to dig in and see if I can find a solution for you that. I'll tag you if I do.. – Anish Kumar Mar 30 '16 at 18:10
  • OK disabling bitcode works but this isn't really a fix. Still waiting Apple's answer on this. – Alexis Mar 31 '16 at 09:09
  • This issue seems to be fixed now. I have successfully uploaded a tvOS build (with bitcode) yesterday. – flopr Apr 06 '16 at 10:06
  • I am too facing the same issue, did anyone find any other solution to solve the issue, coz i can not disable the the bitcode as it is mandatory for watch os. – Aanchal Chaurasia Sep 13 '16 at 17:46
2

I've spent the last few days battling this issue. I've finally sussed out our specific problem and thought it worthwhile sharing. The error was the same as the original posters with iTunes Connect giving a "There was an error importing this build." error as follows:

enter image description here

I tried all sorts to solve this but in my travels the give away of the problem was that one of our many *.bundle files was appearing in the 'Binary and Entitlments' list during the upload/submission process:

enter image description here

Digging a little further when I inspected the contents of that particular *.bundle (with-in either the *.ipa or in the build folder of derived data) there was an unexpected unix executable file. None of other *.bundle files contained a unix executable.

enter image description here

After some trial and error I was able to prevent the executable from being created and added to the bundle by changing the "VERSION_SYSTEM" build setting to "None" (it had inadvertently been set to "Apple Generic" in some recent xcconfig changes).

Anyway, that solved the problem for us. Hope it helps.

An alternative (but less desirable) solution was to remove the (empty) "Compile Sources" step from the targets "Build Phases".

enter image description here

Oliver Pearmain
  • 19,885
  • 13
  • 86
  • 90
1

You need to update your version number to a higher value. If you change only the build number it won't work. I had the same issue after my app binary had been rejected.

Example:

App 1.0.0 (1) -> rejected for some reason.

App 1.0.0 (2) -> you'll get the "There was an error importing this build"

App 1.0.0 (3) -> same error..

App 1.0.1 (1) -> will work!

Cheers,

Rodolfo Gonçalves
  • 156
  • 1
  • 6