Search Unity

Packages not always imported correctly when opening the project

Discussion in 'Package Manager' started by MagicDesignEmerick, Aug 14, 2019.

  1. MagicDesignEmerick

    MagicDesignEmerick

    Joined:
    Oct 4, 2017
    Posts:
    9
    Sometimes when opening unity we have a flurry of messages similar to this one :
    Code (CSharp):
    1. The type or namespace name 'AddressableAssets' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)
    .

    Reimporting the packages usually clears that, but it also happen on our build machine, making builds unreliable. Is this something other people have experienced?
     
  2. erick_unity

    erick_unity

    Unity Technologies

    Joined:
    Jan 4, 2017
    Posts:
    41
  3. MagicDesignEmerick

    MagicDesignEmerick

    Joined:
    Oct 4, 2017
    Posts:
    9
    Yes, we're using the version 1.1.7, and have the package correctly setup and integrated in the project. Except sometimes it seems it fails to loadq. I'm not 100% sure but I recall other packages having the sme issue so I doubt it's linked to this package in particular.