Search Unity

unity 2018 UPM scoped registry package is not auto compiling when updated

Discussion in 'Package Manager' started by senfield, Jun 25, 2019.

  1. senfield

    senfield

    Joined:
    Apr 1, 2019
    Posts:
    31
    Has anyone else been using a scoped registry and experienced their package not recompiling when the version is updated via the unity package manager?
    Instead, it has been needed to manually select reimport on the package to encourage it to compile.
    We are using unity 2018.4.2f1 and package manager 2.0.7 (the latest available on unity 2018)
     
    senfield, Jun 25, 2019
    #1

  2. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    756
    Hi,

    There was a known issue that we fixed (and pretty sure we fixed it in in 2018.4.2f1 too though!). The same behaviour would happen if you publish your package on your scoped registry through npm CLI 6.0.0 or higher. What happens is the npm client is now always setting package files modification date to October 21st, 1985. This would fool the Asset Database thinking that no files have changed in your package. Can you try publishing your package with npm 5.6.0 or earlier and see if the problem persist?

    Regards,

    Pascal
     
    okcompute_unity, Jun 26, 2019
    #2
    senfield likes this.

  3. senfield

    senfield

    Joined:
    Apr 1, 2019
    Posts:
    31
    Thank you, I'll look into this.
     
    senfield, Jun 26, 2019
    #3