Search Issue Tracker
By Design
Votes
7
Found in
2021.3.44f1
2022.3.48f1
6000.0.22f1
6000.1.0a7
Issue ID
UUM-83328
Regression
No
Artifact ID value changes when reimporting an asset when a mobile platform is selected and Unity Accelerator is enabled
Reproduction steps:
1. Open the attached “ASDQWE” project
2. In the top menu, select (Tools > Test)
3. In the Console Window, observe the “artifact id” value in the log
4. Open the Preferences Window (Unity > Settings)
5. Enable the Unity Accelerator (Asset Pipeline > Unity Accelerator (Cache Server) > Default Mode > Enabled)
6. Close and reopen the Unity Editor
7. In the Project Window, select the “Assets/ acs_110_00031001_04_BM.png” texture
8. Right-click it and select “Reimport”
9. Repeat the 2 - 3 steps
Expected result: The “artifact id” value remains the same
Actual result: The “artifact id” and value has changed
Reproducible with: 2021.3.44f1, 2022.3.48f1, 6000.0.22f1
Reproducible on: MacOS 14.61 (Intel, M2 (user’s))
Not reproducible on: No other environment tested
Notes:
- Not reproducible when a Standalone platform is selected
- When the 8th step is performed “Importer(TextureImporter) generated inconsistent result for asset(guid:0e482cb99c033d44f9ff7cac2bfae8e1) "Assets/acs_110_00031001_04_BM.png"“ warning is thrown
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
After a thorough investigation, we have the following observations regarding this case:
The artifact key associated with the specific asset in question is linked to three different artifact IDs. When retrieving the dependency hashes for these artifact IDs, we found that the same dependency hashes are associated with different artifact IDs, resulting in inconsistency. Unfortunately, the corrupted values were already present in the database, leaving no way to recover or repair the asset with corrupted artifacts. We are not sure of the origin of this corrupted state.
As a workaround, we found that completely deleting and reimporting the affected asset resolves the inconsistency. Once reimported, the issue no longer occurs. Based on this, we believe the issue is due to asset corruption and can be addressed by reimporting the affected assets without requiring any code changes