Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2018.2.12f1
2018.3.0a6
2019.1.0a1
2019.2.0a1
Issue ID
1115674
Regression
Yes
Inconsistent behaviour for reloading scripting assemblies after building a project
How to reproduce:
1. Create a new Unity project with version 2018.3.0a5 or older
2. Build the empty project into a player
3. Check Editor.log for build results - assemblies were reloaded after the build was completed
4. Create a new Unity project with version 2018.3.0a6 or newer
5. Build the empty project into a player
6. Check Editor.log for build results
Expected result: the log indicates that assemblies were reloaded after the build was completed
Actual result: there is no mention of an assembly reload after the build was completed
Reproducible with: 2018.3.0a6, 2018.3.3f1, 2019.1.0a14, 2019.2.0a2
Not reproducible with: 2017.4.19f1, 2018.3.0a5
Notes:
It was possible to bypass the assembly reload before 2018.3.0a6 by building the project in batchmode, altering scripting define symbols before starting the build and restoring them to what they were before building was complete
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Add comment