Forum Discussion

AndreaS1590's avatar
AndreaS1590
Copper Contributor
Dec 20, 2024
Solved

Library conflict

Hi

In unity console I have this "red" error:

 

"......We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored"

This happened after I tried to update the library Microsoft Mesh Toolkit, but after encountering a series of errors that I didn't want to investigate further, I reverted to version 5.2402.240 

I tried deleting the corresponding meta file to force a Packagecache refresh, but the result remains the same. Does anyone have any suggestions?

  • CameronMicka's avatar
    CameronMicka
    Jan 14, 2025

    Hi AndreaS1590 are you able to upgrade your Mesh Toolkit to a newer version? (The latest build is 2414.130) PlayerModule isn't in the toolkit anymore, and has not been for a long time. 

     

    Mesh Toolkit versions older than 5.2406 have being deprecated. We recommend upgrading to the newest version of the Mesh Toolkit.

  • Thanks for reporting this, let me message the toolkit team and get back to you!

    • CameronMicka's avatar
      CameronMicka
      Icon for Microsoft rankMicrosoft

      Hi AndreaS1590 are you able to upgrade your Mesh Toolkit to a newer version? (The latest build is 2414.130) PlayerModule isn't in the toolkit anymore, and has not been for a long time. 

       

      Mesh Toolkit versions older than 5.2406 have being deprecated. We recommend upgrading to the newest version of the Mesh Toolkit.

      • AndreaS1590's avatar
        AndreaS1590
        Copper Contributor

        I installed version 5.2409.244 and the problem is solved. Thanks

  • AndreaS1590's avatar
    AndreaS1590
    Copper Contributor

    Thank you for your suggestion.

    But your link refers to a conflict between two different packages using assemblies with the same namespace. In this case the scenario is clear

    Here the error reports conflict inside the same Package 

     

    Any idea?

    • AndreaS1590's avatar
      AndreaS1590
      Copper Contributor

      Thank you for your suggestion. 

      But your link speak about 2 different packages using 2 assembly with the same namespace.

      This scenario is clear.

       

      My error reports conflict inside the same packege ( microsoft mesh toolkit )

       

      Any idea? What i can check?

Resources