Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0p1
Issue ID
984727
Regression
No
Moving asmdef file together with scripts causes nonstandard compile errors
Steps to reproduce:
1. Open user attached project
2. Drag-and-drop the script and the asmdef file into the folder. Make sure to drag-and-drop both at the same time
3. Console outputs: Source file `Assets/NewBehaviourScript.cs' could not be found
Expected result: moving asmdef file together with scripts should not cause nonstandard compile errors
Reproduced in: 2018.1.0b1, 2017.3.0p1, 2017.3.0b1
-
DrummerB
Jun 12, 2019 15:25
I believe this issue is breaking some CI tools. It also makes it more difficult to switch between branches of the project.
Example:
A - Initial commit
B - Another commit
C - Commit, where the above issue is introduced
D - Another commit
E - Latest commitIf I check out B, then try to check out E, I get the above compile error. If there are some branches at older commits (before C) and other branches on more recent commits (after C), then an automatic build tool will fail any time it goes from an older to a newer branch. Unless it runs a completely clean build every time, which ideally would only happen for the nightly build and not for the push-triggered incremental builds.
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
- A bright horizontal line appears in Game view while underwater, when the cloud layer is enabled
- [HDRP] Clear coat materials produce screen-space reflections when the clear coat value is 0 in "Forward Only" Lit Shader Mode
- The alpha blending of transparent objects rendered to a RenderTexture is not rendered correctly in the Game View when in Play mode
- Scrolling on a default ScrollView in a WebGL build is too sensitive when compared to other platform builds and the Editor
- "Fix All" button does not disappear after applying fixes when setting up DXR
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.