Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
1
Found in
2021.3.28f1
2022.3.4f1
2023.1.3f1
2023.2.0a22
Issue ID
UUM-41439
Regression
No
Player crash and "The file 'none' is corrupted! Remove it and launch unity again!" error message is displayed when instantiating Asset Bundles
Reproduction steps:
1. Open the attached “repro-project“
2. Open the “Assets/Scenes/SampleScene.unity” scene
3. Build And Run
Expected result: Asset bundles load successfully without causing the Player to crash or displaying any error messages
Actual result: The Player crashes, producing an error message stating, "The file 'none' is corrupted! Remove it and launch unity again!"
Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a22
Reproduced on: Windows 10 Pro, Windows 11 (by reporter)
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.