Search Issue Tracker
Fixed in 2020.3.42f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a17
Unknown (hidden) 2019.4.X
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.
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- When the project name contains a ";" character, the editor crashes while creating a script.
- New Cubemap is inserted at the end of the array when baking an individual Probe
- Crash on GfxTaskExecutorD3D12::AddRequiredResourceBarriers when opening the project
- WebGL build fails with a UnicodeDecodeError
- MSB3073 error is thrown when building App Packages in Visual Studio