Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.1f1
2022.1
Issue ID
1381544
Regression
No
Package Manager search request fails when user does not have permission to access one or more packages
Reproduction steps:
1. Authenticate to the registry and create ".upmconfig.toml" file
2. Create a new project
3. Open the Project Settings window and select the Package Manager tab
4. Create New Scoped Registry (see notes)
5. Open the package manager
Expected result: Registry loads with all accessible packages
Actual result: Registry isn't loading any package from the registry and throws errors:
[Package Manager Window] Cannot perform upm operation: Unable to perform online search:
Access to REPOSITORY was denied [Forbidden].
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
...
[Package Manager Window] Error searching for packages.
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
Reproducible with: 2019.4.33f1, 2020.3.24f1, 2021.2.4f1, 2021.1.0b1
Notes:
- URL should be UNITY_URL
- Scope should be UNITY_SCOPE
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a8
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b13
Resolution Note (fix version 2021.2):
Fixed in 2021.2.17f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.33f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.38f1