Search Unity

"Failed to fetch versions information" error on non-official Git based packages.

Discussion in 'Package Manager' started by james7132, Nov 22, 2018.

  1. james7132

    james7132

    Joined:
    Mar 6, 2015
    Posts:
    166
    upload_2018-11-22_0-0-43.png

    The package works and compiles properly, but this error shows up on every non-official package provided. This seems like it's not supposed to happen for non-registry packages.

    Unity 2018.3.0b7
    Package: https://github.com/HouraiTeahouse/LZF
     
    james7132, Nov 22, 2018
    #1

  2. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    756
    Local path dependencies (file:) are not allowed inside a package manifest. Only in a project manifest:

    Code (JavaScript):
    1.   "dependencies": {
    2.     "com.houraiteahouse.core": "file:HouraiCOre"
    3.   }
     
    okcompute_unity, Nov 22, 2018
    #2

  3. james7132

    james7132

    Joined:
    Mar 6, 2015
    Posts:
    166
    Thanks for the note: I definitely need to fix that (was previously working in a git submodules -> Local Package project setup).

    However, this doesn't seem to fix the issue. This happens with all packages fetched via git that don't match a Unity supported package registry endpoint.
     
    james7132, Nov 22, 2018
    #3

  4. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    756
    I can't reproduce your issue on my end. I could not use your package since it doesn't load at all for me (local package error). I used a test package of my own to test it.

    Can you try with the latest beta of 2018.3? https://unity3d.com/unity/beta/2018.3#download

    Regards,

    Pascal
     
    okcompute_unity, Nov 23, 2018
    #4

  5. benoitv_unity

    benoitv_unity

    Unity Technologies

    Joined:
    Aug 3, 2017
    Posts:
    40
    Hi,

    We found an issue in the handling of 404 response codes from npm registries. This issue will be fixed in the next patch.
     
    benoitv_unity, Nov 23, 2018
    #5

  6. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
    I've had this recently on all Unity versions when using custom packages (non-git, just placed the package inside Packages -folder manually). This happens even on 2018.1 and 2018.2 which didn't used to throw this error when I started testing custom packages.

    So what I'm really asking now is that will this be backported through all 2018.x since it's a regression on 2018.1 and 2018.2?
     
    rz_0lento, Dec 3, 2018
    #6

  7. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    756
    @rizu Really sorry you were affected by this issue. Our backend provider changed their API and we had to go back and push fixes in all previous Unity releases. We fixed the issue in 2018.2, 2018.3 and 2017.4 releases but not 2018.1. 2018.1 is not supported anymore (see our LTS support page https://unity3d.com/unity/qa/lts-releases ). Is it possible for you to update your work environment to 2018.2? If it is not, may I suggest that you open a bug report and request a new 2018.1 release (https://unity3d.com/unity/qa/bug-reporting)?

    Regards,

    Pascal
     
    okcompute_unity, Dec 4, 2018
    #7