Build Error after installing Runtime

Miles2650 · 19 янв 2023

Ever since installing the Spine Runtime in my Unity project, I've had these errors when I try to do a test build. My understanding is this can happen with new packages, and may or may not be caused by my use of Virtual Studio. I've followed the online suggestions I could find, including deleting the VS files and the Library directory. I even tried removing the Projects folder and reinstalling everything. The errors come up every time I try to build. The project runs fine inside of Unity, including the Spine animations I've added so far. Everything is up to date (Unity, Spine, VS)

Can anybody please clue me in as to what I need to do here?

Script updater for Library\Bee\artifacts\1900b0aP.dag\spine-unity.dll failed to produce updates.txt file

Assets\Spine\Runtime\spine-unity\Components\SkeletonMecanim.cs(31,19): error CS0234: The type or namespace name 'Animations' does not exist in the namespace 'UnityEditor' (are you missing an assembly reference?)

Assets\Spine\Runtime\spine-unity\Components\SkeletonRenderer.cs(54,19): error CS0234: The type or namespace name 'SceneManagement' does not exist in the namespace 'UnityEditor' (are you missing an assembly reference?)

Error building Player because scripts had compiler errors

Miles2650 · 19 янв 2023

Harald · 19 янв 2023

Do these errors only occur when starting a build from inside Visual Studio and not when building in Unity (both when scripts are compiled automatically upon any change, and when building your executable)?

I assume you have already tried what can be seen in this forum posting, as Misaki mentioned here to you on this other thread:

I just found a potential reason for this type of problem: when using an older Visual Studio Editor package in the Unity Package Manager, an issue as described by your posting can be reproduced. Could you please have a try upgrading the Visual Studio Editor package via the Unity Package Manager and then hit Assets - Open C# Project?

If all of the above did not resolve your issue, how are you importing the spine-unity runtime? If you are using the Unity Package Manager, please have a try removing and re-adding the spine-unity packages, in order spine-csharp before spine-unity.

Miles2650 · 19 янв 2023

I just deleted my last reply, as I have now resolved the issue thanks to your reply. Installing the Runtime using the Package Manager did the trick.

I wasn't sure how to fully remove the Runtime that hadn't been installed with Package Manager. I just started a new project, installed all my packages including Spine Runtime, and then transferred my assets and scenes to the new project. It builds fine now!

I am loving Spine Pro and appreciate you helping out a slow-brained newcomer.

Harald · 20 янв 2023

Glad to hear your issue could be resolved! Thanks for your kind words, great to hear that you like using Spine! :nerd:

You did nothing wrong, such issues with the generated Visual Studio project unfortunately seem to occur sometimes without any known reason. (If anyone knows what leads to such an issue, we're happy to hear.)