Search Issue Tracker
Fixed in 2020.3.41f1
Fixed in 2023.1.0a11
Votes
0
Found in
2020.3.39f1
2021.3.9f1
2022.1.14f1
2022.2.0b6
2023.1.0a8
Issue ID
UUM-12669
Regression
No
[M2] Project created with M2 MacBook fails to resolve packages when opening the project
Reproduction steps:
1. Open the user’s attached project
2. At appeared “Unity package manager error” Window press “Retry”
Expected result: Project is opened and packages are successfully added
Actual result: Editor doesn’t open
Reproducible with: 2020.3.39f1, 2021.3.9f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a8
Reproducible on: MacOS 12.5 (M1 Max), Windows 10, MacOS 12.2.1 (Intel)
Notes: When pressing continue at “Unity package manager error” Window Editor opens with “An error occurred while resolving packages:”
In Package Manager there are no errors
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note (fix version 2020.3.41f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-13252
Resolution Note (fix version 2023.1.0a11):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-13252