Package Manager scans files it shouldn't

Unity Engine
,
1

I usually rename a unitypackage before I update it with a newer version, I never let the updater replace a file. You never know what breaks with an update and it’s good to have a backup.

Problem: The new package manager gets confused with that.

Example:

I have version 1.3.7 of River Auto Material on my system. So I renamed that unitypackage and clicked update. 1.3.9 is the most current one. The package manager downloaded that new version, however it only provides me the 1.3.7 version for installation.

6184477--677623--pm.png
6184477--677623--pm.png873×622 129 KB

Just for reproduction, the most updated files are in:

C:\Users<username>\AppData\Roaming\Unity\Asset Store-5.x\NatureManufacture\Editor ExtensionsTerrain

  • RAM 2019 - River Auto Material 2019.unitypackage

while the other versions are in a backup folder

C:\Users<username>\AppData\Roaming\Unity\Asset Store-5.x\NatureManufacture\Editor ExtensionsTerrain\Backup

  • RAM 2019 - River Auto Material 2019 - 2020-06-20.unitypackage
  • RAM 2019 - River Auto Material 2019 - 2020-04-08.unitypackage
  • RAM 2019 - River Auto Material 2019 - 2020-03-01.unitypackage

It would be really nice if there were an option to have Package Manager create a backup automatically.

2

Hi Rowlan,

The team is working on a similar issue which happens even though you do not rename your current asset version. For some reason, an older/same version is installed instead of the newest available on the Asset Store: Unity Issue Tracker - Asset Store packages don&#39;t display latest version available if you have an old version on disk

1 Like