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
- Economy package throws a CS0619 error in the Console when installed together with Deployment package
- “Screen position out of view frustum” errors are thrown when zooming out in the Scene view with Rect Tool selected
- Only one [UnityOneTimeSetUp] method runs when there are 2 of them in different classes
- Crash with multiple stack traces when Sprites with a high resolution get Sliced to a Grid with a small cell size in the Sprite Editor
- The UI Builder's Data Source Object picker cannot be navigated after triggering a circular dependency dialog box
Add comment