Search Issue Tracker
Fixed
Fixed in 2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b9, 2023.2.0a6
Votes
0
Found in
2020.3.45f1
2021.3.17f1
2023.1.0b3
2023.2.0a1
Issue ID
UUM-26502
Regression
No
Asset corruption when using the Accelerator cache server
Reproduction steps:
1. Start an empty Accelerator cache server
2. Create and open a Unity project
3. In Project Settings set Cache Server Mode to Enabled and IP address to “localhost:10080”
4. Import the “DemonGirlMesh.FBX“ FBX to the project Assets
5. Open Editor Log and find the artifact name corresponding to the FBX (i.e. “content hash=NAME) uploaded to cacheserver”)
6. Close the project, and open the artifact file (e.g. “Library/Artifacts/NA/NAME”) with a hex editor and remove the first 64 KB
7. Open the project and select the FBX ("File may be corrupted or was serialized with a newer version of Unity" error should be logged)
8. Reimport the FBX (the error should stay, and the asset will be uploaded to the cache server)
9. Close the project and delete its Library
10. Open the project and observe the Console
Expected result: no errors
Actual result: the "File may be corrupted or was serialized with a newer version of Unity" error
Reproduced in: 2020.3.45f1, 2021.3.17f1, 2023.1.0b3, 2023.2.0a1
Not reproduced in: 2021.3.18f1, 2022.2.6f1
Reproduced using: macOS 13.0.1 (Intel), Windows 10 (by the reporter)
Notes:
1. It is not clear what is causing asset corruption. In this reproduction, the asset is manually corrupted to demonstrate how a corrupt asset is uploaded to the cache server and then distributed
2. Accelerator cache server can be emptied by navigating to its location (e.g. “User/Library/Unity/accelerator”) and emptying the “cachedb“ and “cachedbpending“ folders
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2023.2.0a6):
Fixed in 2023.2.0a6
Resolution Note (fix version 2023.1.0b9):
Fixed in 2023.1.0b9
Resolution Note (fix version 2022.2.13f1):
Fixed in 2022.2.13f1
Resolution Note (fix version 2021.3.22f1):
Fixed in 2021.3.22f1
Resolution Note (fix version 2020.3.47f1):
Fixed in 2020.3.47f1