Search Issue Tracker

Fixed in 2017.1.X

Votes

3

Found in

5.6.0f3

Issue ID

899412

Regression

Yes

UnusedBytecodeStripper2 throws exceptions after iOS build completes

Scripting

-

Steps to reproduce:
1. Open the project attached
2. Build to iOS
3. Observe the console

Result: Errors are thrown after build completes
1) Failed running /Applications/Unity 5.6.0f3/Unity 5.6.0f3.app/Contents/Tools/UnusedByteCodeStripper2/UnusedBytecodeStripper2.exe <...>"
2) Exception: /Applications/Unity 5.6.0f3/Unity 5.6.0f3.app/Contents/Tools/UnusedByteCodeStripper2/UnusedBytecodeStripper2.exe did not run properly! <...>

Expected result: build completes with no errors

Reproduced with: 5.6.0f3
Did not reproduce with: 5.5.3p1 (regression)

Notes:

  • Unable to test on 2017.1.0 (compile errors related to TouchScreenKeyboard)
  • Including full error messages in note
  • Error persists on both .NET 2.0 and .NET 2.0 Subset API compatibility levels

Workaround: reimporting the assemblies (right click on Assets folder in Project window -> Reimport) fixes the issue.
Log in to vote on this issue

Comments (13)

  1. raydekk

    Apr 21, 2017 20:29

    as a workaround - right clicking on Assets (root folder) and then Reimport fixed it for me

  2. raydekk

    Apr 21, 2017 20:06

    happens on 5.6.0p1 too

  3. greg-harding

    Apr 18, 2017 08:51

    I'm having problems building for iOS in Unit 5.6.0f3 as well. An example of our editor output just after UnusedByteCodeStripper2 is run;

    Fatal error in Mono CIL Linker
    System.ArgumentException: Member 'UnityEngine.AudioClip' is declared in another module and needs to be imported

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues