Search Issue Tracker
Fixed in 2018.4.0f1
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.0b11
2018.3.4f1
2019.1.0a13
2019.2.0a1
Issue ID
1137372
Regression
Yes
"csc.rsp" files generate "Invalid AssetDatabase path" warning messages if placed in the Package folder
Reproduction steps:
1. Open "1137372" project
2. Reimport "Foo.cs" from the Packages folder
3. Notice error "Invalid AssetDatabase path ... Use path relative to the project folder."
Expected Result: "csc.rsp" files do not generate warning messages if placed in the Package folder
Actual Result: "csc.rsp" files generate warning messages if placed in the Package folder
Fixed in: 2019.3.0a1
Reproduced with: 2019.2.0a9, 2019.1.0b8, 2019.1.0b1, 2019.1.0a15, 2019.1.0a13, 2018.3.10f1, 2018.3.0f1, 2018.3.0b11
Did not reproduce on: 2019.1.0a12, 2019.1.0a8, 2019.1.0a5, 2019.1.0a1, 2018.3.0b10, 2018.3.0b5, 2018.3.0a1, 2017.4.24f1 (No packman)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment