Search Issue Tracker
Fixed
Fixed in 1.4.X - Physics
Votes
0
Found in [Package]
1.4.X - Physics
Issue ID
ECSB-1726
Regression
No
Generated artifact ID is different between builds when building a content archive after deleting the Library/Artifacts folder
Reproduction steps:
1. Open the project
2. If it asks to upgrade scripts, click "Yes", if the "Link Unity Project" dialog appears, close it
3. Select the “Assets/ContentCatalogs/TestCatalog.asset” asset
4. Click the “Build Content” in the Inspector window
5. Take note of the artifact keys printed in the Console window (Artifact[<guid>] = <artifact key>)
6. Close the Editor
7. Delete the Library/Artifacts folder
8. Reopen the project and repeat steps 2–4
9. Observe the Console window and compare the new artifact keys to those saved in step 5
Expected result: The generated artifact keys should remain the same between builds
Actual result: The generated artifact keys are different between builds
Reproducible with: 6000.0.40f1
Couldn't test with: 6000.0.51f1, 6000.1.7f1, 6000.2.0b4 (Could not resolve compilation errors)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: If the Library/Artifacts folder is not deleted and the "Build Content" button is clicked again, the artifact keys will remain consistent
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
- Render Graph Viewer Capture button plays the click animation but does not do anything when the Capture button is pressed with the “Enter” key on the keyboard
- UI Builder Scrollview is unable to scroll all the way down when the window is downsized vertically
- Celestial bodies order remains unchanged when the Distance setting is modified
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
Resolution Note (fix version 1.4.X - Physics):
The issue with artifact hashes being unstable due to physics colliders has been resolved and will be supplied with an upcoming 1.4.x release. The team is currently evaluating whether additional observed artifact instabilities in the provided project are due to user components.