Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.17.13
1.21.10
Issue ID
ADDR-3334
Regression
No
“AssetReferenceSprite.subAsset” name is not updated after renaming Addressable Asset
How to reproduce:
1. Open the user’s attached “My project (2).zip” project
2. Rename the “UI_IMG_SA_Square.png” file
3. Select “MyScriptable.asset”
4. In the Inspector window, observe the Subasset of the “My Test Sprite”
Expected result: Addressable Asset and Subasset have the updated names
Actual result: Just the Addressable Asset has the updated name, and Subasset has the old name
Reproducible with: 1.17.13 (2020.3.47f1), 1.21.10 (2020.3.47f1, 2021.3.22f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11)
Reproduced on: macOS 13.2.1 (Intel)
Notes:
Subasset is set to “<none>” after renaming it when using packages from 1.16.19 and lower
“m_SubObjectName“ in the “MyScriptable.asset” is not renamed either
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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.