Search Issue Tracker
By Design
Votes
0
Found in
2021.3.41f1
2022.3.41f1
6000.0.17f1
Issue ID
UUM-78795
Regression
No
Errors and Warnings produced by Package Manager are inconsistent between different installation types when installations fail
Steps to reproduce:
- Open or create any Project
- Navigate to Window > Package Manager
- Click the "+" icon in the top left corner and select an option with which to install a Package
- Install a non valid Package and observe failed errors
- Try installing Packages with different options from step 3
Actual results: When installing a non valid Package by
From disk: Info warning is printed in Console
By tarball: Error is printed in Console
By Git url: Error is printed in Console
Name: Error panel is opened up inside the Package Manager
Expected results: Errors or information that installation fails should be consistent between all installation types, preferably without errors printed in the Console
Reproducible with versions: 2021.3.41f1, 2022.3.41f1, 6000.0.17f1
Tested on (OS): Windows 11, macOS Sonoma
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
According to Unity errors and messaging standards, it was decided to log these errors in the console.