Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Unity 5.3.0f4 "iOS: Added Bitcode support." not working

Discussion in 'iOS and tvOS' started by dwit_mass_creation, Dec 10, 2015.

  1. dwit_mass_creation

    dwit_mass_creation

    Joined:
    Jun 18, 2015
    Posts:
    72
    It's in release notes:
    "iOS: Added Bitcode support."

    But it still doesn't work. Standard error:
     
    Fabryka-Gier likes this.
  2. benacler

    benacler

    Joined:
    Oct 26, 2013
    Posts:
    6
    same problem here...
     
  3. Fabryka-Gier

    Fabryka-Gier

    Joined:
    Nov 23, 2015
    Posts:
    5
    +1

    ld: '/Users/myuser/tmp/myproj/Libraries/libiPhone-lib.a(stb_image_resize.o)' 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. for architecture arm64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
     
  4. MartinLaursen

    MartinLaursen

    Joined:
    Jun 11, 2015
    Posts:
    5
    Same issue arising here. Any news/workarounds?
     
  5. 4fthawaiian

    4fthawaiian

    Joined:
    Dec 18, 2013
    Posts:
    33
    Definitely seeing this too. Hoping to upload to itunes connect today. Guess not :/
     
  6. David-Berger

    David-Berger

    Unity Technologies

    Joined:
    Jul 16, 2014
    Posts:
    740
  7. rwbennet

    rwbennet

    Joined:
    Feb 19, 2014
    Posts:
    2
    David, any idea when this will drop?
     
  8. povilas

    povilas

    Unity Technologies

    Joined:
    Jan 28, 2014
    Posts:
    427
    This will be fixed in 5.3.1p1.