Search Issue Tracker
By Design
Votes
0
Found in
2018.2.0b8
2018.2.0b11
Issue ID
1058480
Regression
Yes
Building with read-only manifest.json causes build to fail
Steps to reproduce:
1. Open attached project
2. In Packages/ set manifest.json to read-only
3. In the project folder edit build-exe.bat file and set the path to your unity.exe file
4. Start the build-exe.bat file
(Optional)
5. Check Editor.log
Expected: Unity can build a project from read-only source files, e.g. a Perforce checkout, without needing to check out and make modifications.
Actual: Unity build fails with error*
Reproduced in: b8, 2018.2.0b8, 2018.2.0f2, b6, 2018.3.0a4
Not reproduced in: 2017.1.4p2, 2017.2.3p2, 2017.3.2p2, 2017.4.7f1, 2018.1.8f1, 2018.2.0a1, 2018.2.0b7
*Error:
[Package Manager] A change to the read-only file [E:/Downloads/case_1058480-simple-app/Packages/manifest.json] is required to continue.
Resolution:
This was done by design. It will happen in cases where the project is used with a different Unity version and an upgrade is required. Not performing the upgrade would result in a different result, and likely introduce errors (compilation failures due to missing packages for instance).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment