Search Issue Tracker
Fixed
Fixed in 1.5.x
Votes
0
Found in [Package]
1.5.4
Issue ID
LOC-1221
Regression
No
Unmodified Addressable Groups are dirtied when reimporting Assets in Localization package
How to reproduce:
1. Open the attached “IN-103549” project
2. Enable Debug mode
3. Open the “AddressablesAssetGroup.cs” (IN-103549\Library\PackageCache\com.unity.addressables@2581a6be7421\Editor\Settings\AddressableAssetGroup.cs) with Rider and put a breakpoint on the line “{{m_CurrentHash = default;}}“ (usually line 655 or 657)
4. Attach the script to the Editor
5. In the project, go to Assets > Localization Data, right click on the “Test” asset and reimport it
6. Observe the result in Rider at the breakpoint
Expected result: The file is not dirtied
Actual result: The file is dirtied and the version control integration checks out the unmodified file
Reproducible with: 1.4.5 (2022.3.32f1), 1.5.4 (6000.0.50f1, 6000.1.6f1, 6000.2.0b4)
Could not test with: 1.3.2 (2023.1.0a12), 1.4.4 (2022.3.63f1) (incompatibilities with other dependent packages)
Reproduced on: Windows 11, Windows 10 (user reported)
Not reproduced on: No other environment tested
Notes:
- Using Visual Studio or VS Code does not show the issue clearly
- Issue sometimes does not reproduce when using Addressables version 2.5.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Add comment