Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.16f1
2023.2.4f1
2023.3.0a19
Issue ID
UUM-58997
Regression
Yes
Error "Opening file failed: Opening file VirtualArtifacts/Primary/: No such file or directory" when opening a specific project with corrupt library
Reproduction steps:
1. Open the attached project “ReproProj”
Expected result: The project opens
Actual result: “Opening file failed” message appears
Reproducible with: 2022.2.0a15, 2022.2.21f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0a19
Not reproducible with: 2021.3.33f1, 2022.1.24f1, 2022.2.0a14
Reproducible on: macOS 14.2 (M1 Max), Windows 10
Not reproducible on: No other environment tested
Note: The issue stops reproducing when the library is deleted
Comments (1)
-
soleron
Mar 05, 2024 08:57
Why is this marked as Won't Fix?
Deleting the library folder does NOT fix it.
It also happens on Windows 11 and 2021 LTS 32, and 35.
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
- Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a specific project
- Scene flickers when using Mesh Output with SpriteLit Shader in 2D project
- “Cache Management” text is misaligned in Preferences > Package Manager
- [macOS] network permission shows the name of previously closed app when different app requests network access
- Delta value returned by mouse movementsMonitor is different when changing Screen Resolution
Resolution Note:
This issue is specific to the project and the project has a corrupted library folder.