Search Issue Tracker
Duplicate
Votes
0
Found in
2.4.3
Issue ID
UUM-131146
Regression
No
[Addressables] DefaultSchemaSettings has "androidLocalSettings" assigned twice
Reproduction steps:
1. Open any project
2. Install the Addressables for Android package
3. In the Project window, search for and open the “BundledAssetGroupSchema.cs” package script
4. Go to Line 1756 and observe it
Expected result: the “defaultSettings” has both “androidLocalSettings” and “androidRemoteSettings” assigned
Actual result: the “androidLocalSettings” is assigned twice
Reproducible with: 2.0.3 (2022.3.62f1), 2.3.16, 2.4.6 (6000.0.49f1, 6000.1.3f1, 6000.2.0b1)
Couldn’t test with: 1.25.0 (Couldn’t find the defaultSettings code part)
Reproducible environments: macOS 15.4.1
Not reproducible environments: No other environments tested
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. This bug has already been resolved and is in Addressables v2.7.0. You can use Install by Name in the Package Manager to install this exact version.
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. This bug has already been resolved and is in Addressables v2.7.0. You can use Install by Name in the Package Manager to install this exact version.