Search Issue Tracker
Fixed
Votes
0
Found in
2019.4
2020.2.7f1
2020.3
2021.1
2021.2
Issue ID
1322064
Regression
No
Unity allows to export a package that has an invalid path and does not strip illegal symbols when importing it
How to reproduce:
1. Open the attached project (case_1322064-InvalidPath)
2. Observe that the 'folder ' directory in the assets has a trailing space
3. Click Assets/Export Package
4. Try to import the package to a new project
Expected result: Unity detects the space at the end of the directory and does not allow the export
Actual result: Unity exports the package
Reproducible with: 2019.4.23f1, 2020.3.2f1, 2021.1.2f1, 2021.2.0a10
Could not test with: 2018.4.33f1 (Unity ignores the directory)
Notes:
1. *"<>?| are symbols only allowed on MacOS. If a package with these symbols was exported on Mac and imported on Windows Unity should strip them
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment