Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
IOS Build stuck
#1
Hi. i cant make ios buid, builb stuck at this status http://prntscr.com/sjuieg
unity 2019.3.13, xcode 11.4
Reply
#2
(19-05-2020, 07:02 PM)marad747 Wrote: Hi. i cant make ios buid, builb stuck at this status http://prntscr.com/sjuieg
unity 2019.3.13, xcode 11.4

Hi,

This is a known bug in Xcode, reported and confirmed by Apple. See: http://obi.virtualmethodstudio.com/forum...p?tid=2124

For now the only workaround is to build using Xcode 11.3 our 11.3.1 and Obi 5.1. Write to support(at)virtualmethodstudio.com and we'll provide any Obi version you need.
Reply
#3
(19-05-2020, 07:03 PM)josemendez Wrote: Hi,

This is a known bug in Xcode, reported and confirmed by Apple. See: http://obi.virtualmethodstudio.com/forum...p?tid=2124

For now the only workaround is to build using Xcode 11.3 our 11.3.1 and Obi 5.1. Write to support(at)virtualmethodstudio.com and we'll provide any Obi version you need.

Thanks, but it not fixed issue
We use unity cloud build, with obi fluid 5.1 and xcode 11.3.1 and we have issue - ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '1103.0.32.29.0_0' Reader: '1100.0.33.17_0')', using libLTO version 'LLVM version 11.0.0, (clang-1100.0.33.17)' for architecture armv7
When we disable bitcode - error still
Reply
#4
(19-05-2020, 07:44 PM)marad747 Wrote: Thanks, but it not fixed issue
We use unity cloud build, with obi fluid 5.1 and xcode 11.3.1 and we have issue - ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '1103.0.32.29.0_0' Reader: '1100.0.33.17_0')', using libLTO version 'LLVM version 11.0.0, (clang-1100.0.33.17)' for architecture armv7
When we disable bitcode - error still

Hi,

What Unity version are you using?
Reply
#5
(19-05-2020, 07:44 PM)marad747 Wrote: Thanks, but it not fixed issue
We use unity cloud build, with obi fluid 5.1 and xcode 11.3.1 and we have issue - ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '1103.0.32.29.0_0' Reader: '1100.0.33.17_0')', using libLTO version 'LLVM version 11.0.0, (clang-1100.0.33.17)' for architecture armv7
When we disable bitcode - error still

Hi,

We are unable to reproduce this, it builds fine with 11.3.1 + 5.1. What Unity version are you using?
Reply
#6
(20-05-2020, 10:30 AM)josemendez Wrote: Hi,

We are unable to reproduce this, it builds fine with 11.3.1 + 5.1. What Unity version are you using?

2019,3,13
Reply
#7
(20-05-2020, 10:53 AM)marad747 Wrote: 2019,3,13

What file is it complaining about the bitcode version mismatch?
Reply
#8
(20-05-2020, 11:15 AM)josemendez Wrote: What file is it complaining about the bitcode version mismatch?

I use xcode 11.3.1 and 5.1 obi fluid. When i press at build and run - build succes and i install app to my iphone. BUT when i want to archive and upload to TF i have problems http://prntscr.com/skfx6n http://prntscr.com/skfz88
What library use bitcode?
full error http://prntscr.com/skg9sw
Reply
#9
(20-05-2020, 03:33 PM)marad747 Wrote: I use xcode 11.3.1 and 5.1 obi fluid. When i press at build and run - build succes and i install app to my iphone. BUT when i want to archive and upload to TF i have problems http://prntscr.com/skfx6n http://prntscr.com/skfz88
What library use bitcode?

Hi,

We're unable to reproduce this. Try deleting derived data for your project (File->Project Settings->click the little arrow right next to the derived data folder, and delete it), and build archive from scratch

Also, if you're building an app for iOS (not tvOS or watchOS), disabling bitcode might solve bitcode version-related options.
Reply
#10
(20-05-2020, 03:51 PM)josemendez Wrote: Hi,

We're unable to reproduce this. Try deleting derived data for your project (File->Project Settings->click the little arrow right next to the derived data folder, and delete it), and build archive from scratch

Also, if you're building an app for iOS (not tvOS or watchOS), disabling bitcode might solve bitcode version-related options.

Bitcode enable - No - same problem
Reply