0

Bitcode is really important for me, because it generates dSYM file for crash symbolization. I have a library which has bitcode disabled. Because of it I cannot archive my build with bitcode enabled. I get this error:

‘path to framework’ does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. file 'path to framework’ for architecture arm64

I searched for solutions but the only solution I found was to disable bitcode. But that solution creates more problems with crashes symbolization. Is there another way? Or why it is not possible?

rmaddy
  • 307,833
  • 40
  • 508
  • 550
Simon Moshenko
  • 1,820
  • 13
  • 32
  • 1
    I had the same issue, and there's no way around it: either developers of frameworks provide you with bitcode-enabled version, or you have to disable bitcode in your project too. We considered a very clumsy workaround, where we would create 2 builds: with offending framework, and with it excluded (and corresponding functionality disabled), but it crates whole bunch of other problems: how do you publish both versions, how users select which one they need and so on. So we decided against it. Also see https://stackoverflow.com/questions/30848208/new-warnings-in-ios-9-all-bitcode-will-be-dropped – ohglstr Sep 23 '19 at 17:11

0 Answers0