[Build bug] UnityEngine assemblies missing on Game Jolt plugin scripts on build
Tetriser opened this issue · 11 comments
This happens each time I tried to build the project, the build fails as the compiler fails to find Unity-related namespaces in the wrapper scripts.
Is this a bug or something?
that's very strange.
Unity has sometimes problems with assets in the "Plugins" assembly, so you may have to close Unity and reopen it, that might help. If not, could you please tell me which Unity version you are using?
Tried today, still the same error.
I'm using Unity 2017.3.0f3.
Seems like one of those "typical Unity bugs". Every now and then unity fails to import a package correctly. If that happens, the best solution seems to "Reimport All Assets" from the menu. Depending on the size of the project, this may take a while (several minutes).
Tried to do that, but Unity keeps crashing after I do so.
does it really crash or is the reimport just stuck? If the later one, you just have to wait, for example the oculus sdk needs half an hour to reimport and most of the time it seems to be stuck.
You could also try to add the UnityEngine reference manually, but that might be overwritten by unity.
One other solution I found online was to reinstall Unity, but hopefully that isn't necessary.
It crashed, there's one time that I tried again but the Unity process is dead. (Zero memory, disk or CPU usage, but still there)
That's indeed very strange, maybe you find help in the unity forums. I doubt that you're the only one having this issue with Unity, so someone there might have a solution
Well, nobody is answering my question in the forums for 2 days now.
I'm sorry for that, I've expected that the Unity forum could help, because this problem is not tied to this asset, but a general problem with Unity's import instabilities.
What happens if you create a new MonoBehaviour in that location? Does it also mark the usings as errors?
You could also try to delete the folder and reimport it or move the inner folders out of the Plugins folder.
Besides of that I could only recommend the things that I've found on the forums:
Post 1
Post 2
Post 3
I'm closing this issue, it's actually a faulty Unity installation.
Just reinstalled Unity and everything works fine now.
Anyway, thanks for the support.
perfect, I'm glad it worked out 😄