Search Unity

  1. Unity 2018.3 is now released.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We've updated our Terms of Service. Please read our blog post from Unity CTO and Co-Founder Joachim Ante here
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Apple rejecting apps built with burst compiler

Discussion in 'Entity Component System and C# Job system' started by FrankvHoof, Jan 11, 2019.

  1. FrankvHoof

    FrankvHoof

    Joined:
    Nov 3, 2014
    Posts:
    21
    When uploading an (iOS) app to TestFlight, Apple rejected it over the fact that Burst Compilation had been enabled. The lib_burst_generated.bundle is seen as a standalone executable, which apparently is not currently allowed by Apple. Is there any communication between Apple and Unity about this?
    https://gyazo.com/2b99235d40444c62084be7993b862bc0
     
  2. xoofx

    xoofx

    Unity Technologies

    Joined:
    Nov 5, 2016
    Posts:
    89
    Thanks for bringing this up to our attention.
    As burst is still in preview/alpha, we haven't had a chance to check with TestFlight for iOS, we will have to find a fix for this in a future release. We will keep you informed.
     
    GilCat, tarahugger, any_user and 4 others like this.
  3. StevenTicToc

    StevenTicToc

    Joined:
    Mar 16, 2018
    Posts:
    1
    We are also seeing this same exact error. We've been uploading to testflight regularly and just recently (2 weeks ago) started seeing this error with a build that hadn't changed aside from some textures, so I'd assume this is something that recently changed on apples end.
     
  4. xoofx

    xoofx

    Unity Technologies

    Joined:
    Nov 5, 2016
    Posts:
    89
    Really?! That's quite unexpected... I don't know what to say. At the time we implemented this feature using dynamic library, we wanted to use the same loading model across all platforms, and while checking for iOS support for dynamic libraries on Internet forums, we found contradictory claims about it, but when testing in dev mode it was working smoothly. But we didn't go up to verify this with TestFlight.

    We are working on bringing static linking support for burst but it not be available before a few weeks (including the release of Unity editor/engine patches and backports)
     
  5. rizu

    rizu

    Joined:
    Oct 8, 2013
    Posts:
    669
    I hope you implement this on Windows IL2CPP standalone as well. While not critical (like the Apple issue), would be nice to get rid of that extra dll there.
     
  6. capyvara

    capyvara

    Joined:
    Mar 11, 2010
    Posts:
    66
    So this blocks any burst iOS app basically? any temporary workarounds (like disabling burst globally)?
     
  7. 5argon

    5argon

    Joined:
    Jun 10, 2013
    Posts:
    903
    Uncheck enable burst compilation in the top menu?