Search Issue Tracker
Fixed
Fixed in 2021.3.13f1, 2023.1.0a17
Votes
0
Found in
2021.3.5f1
Issue ID
UUM-11857
Regression
No
[Linux] Editor doesn't build a project when "Install into source code 'build' folder" is enabled after switching projects
How to reproduce:
# Download both user-attached projects from (projectA.zip) file
# Download and build the Unity Editor for Linux and the LinuxPlayer from source
# Open “ProjectA“
# In the BuildSettings enable “Install into source code 'build' folder“ option and build and run the project
# Observe the text in the player window
# Close the player and project and open “ProjectB“
# Repeat steps 4 and 5
Expected results: the text in the second player window says “Project B“ which is different when compared with the previous project’s build
Actual results: the text in the second player window says “Project A“ which is the same as in the previous project’s build
Reproducible with: 2021.3.5f1
Could not test with: 2023.1.0a5 (no “Install into source code 'build' folder“ option in the BuildSettings window)
Reproducible on: Ubuntu 20.04
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (fix version 2023.1.0a17):
Fixed in 2023.1.0a16
Resolution Note (fix version 2021.3.13f1):
Fixed in 2021.3.14f1