Search Unity

Known Issues

Discussion in 'Package Manager' started by okcompute_unity, May 10, 2019.

Thread Status:
Not open for further replies.
  1. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    584
    Hello, Package Manager users.

    Before asking a question, please take the time to look at the known list of issues below (Some of them even have workarounds). If you don't find the issue listed here, please either ask a question or create a new bug.

    • The
      Window->Package Manager
      menu item disappears in Unity 2018.3, 2018.4, 2019.1 if you upgrade a project with compilations errors. This will be fixed in an upcoming 2019.1 patch release. Workaround: You can try to close Unity and reopen your project. Sometimes, the Package Manager window will reappear.
    • Package Manager fails to start on Windows 7. Workaround: Install Windows security update KB2533623. Thanks to @GuyMauve5 for finding this solution.
    • The Package Manager window does not automatically refresh after changing the registry or scopedRegistries properties of manifest.json.Workaround: close/re-open the Package Manager Window.
    • When a package that is not installed in your project (All tab) does have published documentation, clicking on the
      View documentation
      link will open a web browser on page 404.
    • Removing the
      package.json
      file from an embedded package folder causes unintuitive errors.
    • Adding a local package when the same one is already embedded causes unintuitive console errors
    • Packages installed per dependency are not shown in In Project filter list but are shown as installed in All Packages filter list.
    • Progress on large package installation only shown on package item in packages list. Not intuitive.
    • Dependencies in package manifest (
      package.json
      ) are limited to SemVer versions (e.g: 1.0.0). The reason for not allowing file and Git dependencies is because it would introduce non-determinism in package resolution.
    • Prior to Unity 2019.2, Package Manager does not work when the package registry needs to be accessed through a self-signed certificate. This can be required by some proxy configuration, or if you are hosting a private registry. The only workaround is to set the
      NODE_EXTRA_CA_CERTS
      environment variable (See NodeJS documentation for more details). This works because the UnityPackageManager application is developed in NodeJS. Be aware that on Windows, modifying this environment variable at the system or user level may have an impact on other node applications installed on your system. If you are using 2019.2 already, see Unity User manual for more info.
    • SCP Git URI form is not supported as this moment (e.g.
      git@git.repos.com:my-repo.git
      ). Workaround: use the SSH scheme URL (e.g.
      ssh://git.repos.com/my-repo.git
      ).

    Thank you!

    The Unity Package Manager team
     
    Last edited: Jun 18, 2019
    Gunvald and technicat like this.
Thread Status:
Not open for further replies.