Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b3
2022.1
Issue ID
1349064
Regression
No
Importing package causes import loop when its path is child of another imported package
Reproduction steps:
1. Open the attached project "ImportPackageLoop.zip"
2. Open Window > Package Manager
3. Click the plus and "Add package from disk..."
4. Import "FeatureSets/package.json"
5. Import "FeatureSets/Sub/package.json"
Expected result: Package is imported
Actual result: Import starts looping, attempting to import the root package and then the child package
Reproducible with: 2019.4.29f1, 2020.3.14f1, 2021.1.14f1, 2021.2.0b3, 2022.1.0a2
Could not test with: 2018.4.36f1 (unable to add package)
Note: If unable to open project due to import loop, delete the "Packages" folder
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Having a package inside a package is not supported