Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Unable to open Package Manager

Discussion in 'Package Manager' started by jbassking, Apr 19, 2021.

  1. jbassking

    jbassking

    Joined:
    Feb 27, 2014
    Posts:
    106
    I'm running 2020.1.10f1 on Windows 10. Whenever I click Window -> Package Manager I get the following error. I'm getting a similar error on our Mac as well.

    NullReferenceException: Object reference not set to an instance of an object
    UnityEditor.PackageManager.UI.PackageManagerWindow.SelectPackageAndFilter (System.String packageIdOrDisplayName, System.Nullable`1[T] filterTab, System.Boolean refresh, System.String searchText) (at <3037c1046402403280ab8b0782ca806f>:0)
    UnityEditor.PackageManager.UI.PackageManagerWindow.OpenPackageManager (System.String packageNameOrDisplayName) (at <3037c1046402403280ab8b0782ca806f>:0)
    UnityEditor.PackageManager.UI.Window.Open (System.String packageNameOrDisplayName) (at <3037c1046402403280ab8b0782ca806f>:0)
    UnityEditor.PackageManager.UI.Window.ShowPackageManagerWindow (UnityEditor.MenuCommand item) (at <3037c1046402403280ab8b0782ca806f>:0)
     
    jbassking, Apr 19, 2021
    #1

  2. Davidtr_Unity

    Davidtr_Unity

    Unity Technologies

    Joined:
    Mar 5, 2020
    Posts:
    34
    Hi, I am sorry to hear you're having trouble with the package manager. It appears that you're using an older version of the editor, the latest recommended release is 2020.3.4f1 as I am writing this, I would recommend you try to update your editor and see if that fixes it for you.

    I hope this was helpful!
     
    Davidtr_Unity, Apr 29, 2021
    #2

  3. jbassking

    jbassking

    Joined:
    Feb 27, 2014
    Posts:
    106
    Actually all I have to do was update the external-dependency-manager and that fixed it.
     
    jbassking, Apr 29, 2021
    #3