Search Issue Tracker
By Design
Votes
0
Found in
2020.2.0a5
2020.2.0a9
Issue ID
1248326
Regression
Yes
[PackMan] Package Manager window isn't refreshed when calling AssetDatabase.Refresh() after making changes to a package
How to reproduce:
1. Open the attached "1248326 repro" project
2. Open the Package Manager window from Window > Package Manager
3. Select the "Simple Package" package from the list
4. Press "Switch Package" from MyMenu > Switch Package
Expected result: description and path of the "Simple Package" are updated and new values are shown in the Package Manager window
Actual result: description and path of the "Simple Package" aren't updated and old values are shown in the Package Manager window
Reproducible with: 2020.2.0a5, 2020.2.0a15
Not reproducible with: 2018.4.23f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a4
Notes:
-The package is updated only after Unity loses and regains focus or the reload button is pressed in the Package Manager
-The .json file in the Assets folder is refreshed as expected after modifying it and calling AssetDatabase.Refresh()
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [MacOS] Crash on [NSApplication endModalSession:] when saving while Play Mode is loading
- Importing a theme through the Inspector allows importing the same theme multiple times
- Editor window disappears when repositioned in a specific way in Editor
- Importing a theme through the Inspector allows circular import
- FocusNextInDirection not focusing when used on multiline TextFields
Resolution Note (2020.2.X):
UnityEditor.PackageManager.Client.Resolve() should be called to resolve this issue.
If it is known that only the package metadata changed, the AssetDatabase.Refresh() call can be replaced with Client.Resolve() entirely.
If it's unknown what has changed in the package, then both AssetDatabase.Refresh() and Client.Resolve() should be called.
The Editor should be updated to the latest 2020.2 version if it does not have access to the Client.Resolve() function.