Search Issue Tracker

Fixed

Fixed in 2020.3.42f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a17

Votes

0

Found in

2019.4.40f1

2020.3.40f1

2021.3.10f1

2022.2.0b8

2023.1.0a10

Issue ID

UUM-15081

Regression

No

Importing a .unitypackage does not upgrade its dependencies using the Editor manifest-based upgrade logic

-

Importing a .unitypackage that has UPM dependencies in a newer Editor than the one it was exported with can lead to the following issues:

Dependencies on core packages whose versions are different in the newer Editor will fail to resolve;
Dependencies on any packages whose versions are incompatible with the newer Editor will be imported and broken, even if a higher "minimumVersion" or "version" is specified in the Editor manifest.

Reproduction steps:
1. Create a new project in the latest 2021.3 release.
2. Import the .unitypackage attached to this Issue.

Exported .unitypackage is just a simple URP sample, exported in Unity 2021.3.2f1, where the URP version is 12.1.6. The easiest reproduction is to import said package in a newer version of Unity, where the URP version is higher than 12.1.6.

Expected results: URP package is upgraded to 12.1.7
Actual results: URP package remains 12.1.6, causing invalid package dependency errors

  1. Resolution Note (fix version 2020.3.42f1):

    Fixed in 2020.3.42f1

Add comment

Log in to post comment