Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.20
2.0.8
Issue ID
ADDR-3671
Regression
No
The ResourceLocation.PrimaryKey points to the folder address when it is used with an AssetReference during Buildtime
Reproduction steps:
1. Open the attached “Test” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. In the Game View, observe the text in the middle of the screen
Expected result: The text displays “Results: Test/New Prefab.prefab”
Actual result: The text displays “Results: Assets/New Folder”
Reproducible with: 1.20.5 (2021.3.37f1), 1.21.20 (2021.3.37f1, 2022.3.25f1, 2023.2.19f1), 2.0.8 (2023.2.19f1, 6000.0.0b15)
Reproducible on: MacOS Sonoma 14.4.1 (Intel) Buildtime, Window 11 (user’s)
Not reproducible on:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00146, Htc 10 (HTC 10), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Could not test on: MacOS Sonoma 14.4.1 (Intel) Standalone Runtime (The Standalone Player displays dark or blue screen)
Workaround:
- Use the string path of the asset instead of the AssetReference
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
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
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.