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
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
Resolution Note (fix version 2020.3):
Fixed in 2020.3.8f1