Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
3.0.1
Issue ID
1228299
Regression
No
Importing the 2D Pixel Perfect package may result in exceeded path symbol count
How to reproduce:
1. Create a new project. Make sure that the project path is at least 89 symbols long
2. Open the Package Manager window.
3. Import the 2D Pixel Perfect package
4. Observe the Console and Package Manager windows
Expected result: Package imports without any issues
Actual result: "Package Manager Window had an error while completing an operation: Could not find file" error is thrown and the Package Manager window breaks
Reproducible with: 2018.4.191f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Could not test with: 2017.4.38f1(No package manager)
Workarounds:
- Shortening the path to the project
- Using symbolic links
Notes:
- The issue is not limited to the Pixel Perfect package, however, Pixel Perfect has a deep folder depth which results in a long path that showcases the underlying path length problem
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
- [Android] The warning "Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak" is displayed when ShaderVariantCollection.WarmUp is called
- RectangleContainsScreenPoint returns false for some points even when the points are in the rectangle
- [iOS] Stacked camera does not render when using post effects
- TextField cannot be edited in an extended Editor window when double-clicking it
- [VisionOS] visionos build do not add plugin or frameworks
Resolution Note:
The 2D Pixel Perfect Package will be fixed, we will try to shorten the paths to some of our sample assets.
Currently, the issue will remain on the Package Manager side, so similar problems caused by exceeded path length can be encountered in certain situations. It was decided not to address this issue for the moment as it would require a major refactoring to be done. However, this may get addressed in the future once certain improvements will reach the Package Manager.
Trying to reduce an overall project path is advised to work around this issue.