Search Issue Tracker
Won't Fix
Won't Fix in 1.21.X
Votes
0
Found in [Package]
1.20.5
1.21.14
Issue ID
ADDR-3458
Regression
No
Addressables Path Variable has an incorrect Bundle Location set when selecting profiles with keyboard keys
Reproduction steps:
1. Open the "IN-46428.zip" project
2. Open Window -> Asset Management -> Addressables -> Profiles window
3. Click on "Foo" in the left panel
4. Observe the “New Entry” Bundle Location field
5. Press the Down key
6. Press the Up key and observe the “New Entry” Bundle Location field
Expected result: The “New Entry” Bundle Location field has the value "Built-In"
Actual result: The “New Entry” Bundle Location field has the value "Custom"
Reproducible with: 1.20.5 (2021.3.28f1, 2022.2.0b12, 2023.1.0a17), 1.21.14 (2021.3.28f1, 2022.3.5f1, 2023.1.5f1, 2023.2.0b1)
Reproducible on: Windows 10
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (1.21.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.