Search Issue Tracker
Fixed in 1.2.0
Votes
1
Found in [Package]
2018.3.2f1
Issue ID
1118962
Regression
No
[Addressables] Profile Entries variables are not automatically updated with every build
How to reproduce:
1. Open tester-submitted project(AddressableVariables)
2. Build Player Content via the 'Addressable Assets' window
3. Check if the newly generated folder matches the current Application version
4. In Player Settings change the Application version
5. Build Player Content again
Expected result: a new folder reflecting the updated Application version is generated
Actual result: Player Content was built with the old Application version variable
Reproducible with Unity versions: 2018.3.8f1, 2019.1.0b6, 2019.2.0a8
Could not test with Unity versions: 2017.4.23f1(Addressables Package incompatible with this version)
Reproducible with Package versions: 0.5.2, 0.6.7
Could not test with Package versions: 0.4.8(Cannot Build Player Content)
Notes:
Building Player Content after entering Play Mode or after forcing a script recompilation does not cause this issue
Cleaning Player Content does not solve this issue
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (fix version 1.2.0):
Should work as expected