Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.16.6
Issue ID
ADDR-1893
Regression
Yes
Addressables Profile variable value gets overrided when switching Profiles while one of the fields is selected
How to reproduce:
1. Open the attached '1325345.zip' project
2. Open Window > Asset Management > Addressables > Profiles
3. In the Addressables Profiles window select the 'Test1' Profile
4. Select the Build Target field and enter 'aaa'
5. Without deselecting the field or pressing 'Enter' select the 'Test2' Profile
6. Observe the Build Target field of both Profiles
Expected result: The Build Target of the Test1 Profile is set to 'aaa'
Actual result: The Build Target of the Test2 Profile is set to 'aaa'
Reproducible with: Addressables 1.16.6 (2018.4.33f1, 2019.4.23f1, 2020.2.7f1, 2020.3.3f1, 2021.1.1f1, 2021.2.0a11), 1.17.15 (2019.4.23f1, 2020.2.7f1, 2021.1.1f1, 2021.2.0a11)
Not reproducible with: Addressables 1.16.1 (2018.4.33f1, 2019.4.23f1, 2020.2.7f1, 2020.3.3f1, 2021.1.1f1, 2021.2.0a11)
Note:
- The issue is reproducible with all of the Addressables Profiles window fields
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Since it now uses a TextField rather than a DelayedTextField and also compares the previous profile with the current profile, it will save to the proper profile while the user enters the value in.