Every time I launch the editor these lines appear in Console (only once) as errors:
Unity extensions are not yet initialized, so we cannot say if the ‘C:/Program Files/Unity/Editor/Data/UnityExtensions/Unity/Advertisements/UnityEngine.Advertisements.dll’ is compatible with platform WindowsStoreApps
Unity extensions are not yet initialized, so we cannot say if the ‘C:/Program Files/Unity/Editor/Data/UnityExtensions/Unity/GUISystem/UnityEngine.UI.dll’ is compatible with platform WindowsStoreApps
[…]
There are 702 of them so I’m only pasting a couple of them as an example.
@Tautvydas-Zilys the link you posted (ok, a year old) was closed as not reproducible, but another case was opened by @codestage with case number 1050190. I cannot find it to check the status.
I really don’t know why there’s hidden bug reports anyway. From what I know, they would be the only possibility to know in which version the bug was fixed, or if it was fixed even, am I right?
Could you give me a quick info about the bugs status, please?
Same there, just upgrade to 2018 and can’t get a single project work. There is few error, one of them is this one. Other is at compilation time (for an HoloLens), where VS can’t find Unity Player 'cause the build did not include it and several other dependency at build-time (because… ??? No logic at all), and so utterly failed to run.
@unity_VAfwBEs32IOz_w Have you had any luck? We’re just getting into HoloLens as our site and would love to know if there’s a workaround before we hit the same snag.
It was closed because we couldn’t reproduce it anymore. If you can, please report another bug with a repro project included so we could fix it once and for all.
I got the exact same problem after upgrading my project from 2018.1.9 to 2018.2.13 just now. Repros 100% on every project reopening. During auto-upgrade I got a warning about missing metadata and I suspect this could be an issue. Also project.dependencies file used to be empty and now it contains list of dependencies (interestingly all of those dependencies are causing those startup errors).
Anyhow, I solved that by removing “Library” folder and reopening the project. Now Unity does not complain anymore.
I have the same problem working on a project with the HoloLens.
The problem does indeed temporarily disappear when deleting the Library folder. However, that is only because the Build Settings are lost. As soon as I switch the Platform back to Universal Windows Platform in Build Settings, save project, close Unity Editor and reopen the project, the annoying error messages reappear. Maybe that helps in reproducing? Let me know if you need more info.
