- Home /
Why does Unity ship official (preview) packages with in-editor-compilation-errors?
Upgraded DOTS. Now this: 15 times something similar to this: "Library\PackageCache\com.unity.entities@0.9.0-preview.6\Unity.Scenes.Editor\BuildStepCreateResourceCatalog.cs(18,51): error CS0619: 'BuildStep' is obsolete: 'Replace with BuildStepBase. (RemovedAfter 2020-07-01)'" Trying to fix it by hand leads you down some obscure rabbit hole where you START by overwriting virtual functions of types that are defined in preprocessor directives.
Why? Unexpected behaviour is one thing, but this [...]!!!
Well, because everyone's so suspiciously silent, I'm hoping that after installing this trash for the FOURTH time(next update...), it will work for the second time for me. And HEY, maybe I can work on my project again, AFTER A $$anonymous$$ONTH
Answer by Casiell · Apr 10, 2020 at 06:56 AM
It looks like this package is not compatible with newest version of the Editor. As stated by this error, BuildStep became obsolete only after 2020-07-01 and 2020 versions are still in Alpha. You are essentialy using preview package (so like beta or early-access however you want to call it) with alpha version of editor. I'm not surprised something doesn't work
Ok so the newer the package, the older your Unity version needs to be. Got it, because it makes sense 100% (not). The new DOT stack was updated yesterday, along with a new 2020 beta version. I personally thought it WASN'T a coincidence. The more important question NOW becomes "why does Unity let you install packages that are incompatible with your Unity version?"
EDIT: Switching back to 2019.3.9f1 does not only include the same errors; it adds more of them. I would've LOVED to be wrong in some way but... Additionally, I don't think it's even a user error. You can see the code that's causing the problem; it has version checking (of Unity) in preprocessor directives. The code that's causing the problem is for versions below 2020.1... $$anonymous$$EANING everything is accounted for in theory, the code is just wrong, because it uses types that were removed FRO$$anonymous$$ THE VERSIONS THAT IT (dots) WAS BUILT FOR.
Answer by DigitalArtsSoftwareEngineers · Apr 16, 2020 at 11:54 AM
is not only 2020 also 2019.3.9 has the same issues like 15 errors and haven't figure out how to fixes yet. I tried following errors suggestions like replacing BuildStepBase with BuildBase but at the end editor crashed.