Search Issue Tracker
Fixed in 2018.4.X
Votes
0
Found in
2018.4.12f1
Issue ID
1193018
Regression
Yes
[2018.4] Console throws a Warning about corrupted ProjectVersion.txt file which is in another Project
To reproduce:
1. Open Unity and create a New Project or open existing Project
2. When Project is opened, open the Console window
Expected results: No Warning on Error is printed
Actual results: A Warning about corrupted ProjectVersion.txt file which is in another Project is thrown:
"The contents of the ProjectVersion.txt file for the project located in /Users/*/Downloads/SurfaceShader are corrupt. Please fix the contents of the file."
Notes:
- This issue happens on both Windows and macOS
- Sometimes this issue happens when creating 2 Projects with 2018.4.12f1 and the second one says that the Settings for the first one are invalid
- A photo for reference is attached in Comments section
- No security issues were found
Reproduced on Unity 2018.4.12f1
Not reproduced on Unity 2018.4.11f1, 2019.2.10f1, 2019.3.0b8 and 2020.1.0a9
Regression on Unity 2018.4.12f1
Comments (9)
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Thedomib6
Apr 22, 2020 23:26
Not fixed in Unity 2018.4.20f1
Stevens-R-Miller
Mar 27, 2020 12:33
Sure would be nice if it said which release of 2018.4 it was fixed in.