Search Issue Tracker
Fixed in 2020.3.X
Votes
0
Found in
2019.4
2020.3
2020.3.1f1
Issue ID
1330738
Regression
No
File could not be read errors thrown when Importing package with Sprites
Reproduction steps:
1. Create a new empty Project
2. Import the attached Package
Expected result: The packages is imported
Actual result: File could not be read errors are thrown
Reproducible with: 2019.4.25f1, 2020.3.7f1
Not reproducible with: 2019.4.26f1, 2020.3.8f1, 2021.1.8f1, 2021.2.0a18
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
- 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
Resolution Note (fix version 2020.3):
Fixed in 2020.3.8f1