Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
Issue ID
858327
Regression
No
Mac Editor crashes at end of Android APK build or project export
Steps to reproduce:
1. Open new project
2. Switch to iOS or Android
3. Go to 'Player Settings' and change the following options:
- Scripting Backend: Mono2x
- Stripping Level: 'Strip Byte Code' or 'Use micro mscorlib'
4. Trigger a build
5. Before 'AOT' part in the building progress bar shows up, drag some other window on top of Unity's progress bar and focus it so that the progress bar becomes hidden
6. Wait a couple seconds, Unity Editor will crash
Notes:
This might be happening on some different setups as well (besides Mono2x scripting backend and 'Strip Byte Code' or 'Use micro mscorlib' stripping levels), but I was only able to reproduce this issue on these conditions.
Building for Android with the same scripting backend and stripping levels doesn't crash the editor.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Scene View drop-down fields reopen when clicking them again to close it
- Crash on UnityEngine.Rendering.RenderPipelineAsset:InternalCreatePipeline when opening a specific project
- [STW 6.1] UI Builder Inspector fields get corrupted when docked UI Builder is maximized
- Pickers and ‘+'/’-' buttons are not visible on the right side of parameter fields when the width of the "Project Settings... -> Quality" window is small
- "AssertionException: Assertion failure. Value was False" error is thrown when unmaximizing a docked UI Builder Window
JanusAnderson
Mar 10, 2017 13:06
How about 5.4? I have a live game and I'm unable to make builds from my macbook now because of this.
azix
Mar 02, 2017 10:26
Will this fix be backported to Unity 5.5 ?
I use a custom build function that makes use of EditorUtility.DisplayProgressBar and Unity is constantly crashing even before the build has completed