Search Issue Tracker

Fixed in 2019.1.X

Fixed in 2018.3.X



Found in


Issue ID




Find References in Scene shows objects that are not referencing the asset

Scene Hierarchy


Steps to reproduce:
1. Open attached “” Unity project
2. Open “Test" scene
3. Find “Disable" asset in Project tab
4. Right-click on “Disable” asset and select “Find References in Scene”

Expected results:
Only objects referencing “Disable” asset are found
Actual results:
Objects not referencing “Disable” asset are also found

Reproduced in: 2018.1.0a5, 2017.3.0b10, 2017.2.0p2, 2017.1.2p3, 2017.1.0a1

Fixed in: 2019.1.0a4

Comments (19)

  1. 856c7547d14b9dbc7f1f5ff7385ebe58?d=mm


    Jul 29, 2021 13:17

    Still broken in unity 2021.1.5f1. Nearly 4 Years after this bug report, really unity devs? As a workaround I use the following free tool

  2. F2bbba4266abb4a5cf79f0e4228b2a2f?d=mm


    Jul 02, 2021 21:42

    Not fixed in v2019.4.24f1.

  3. A9794a4ed2b3acd3221865a9b1028741?d=mm


    Jun 09, 2020 23:37

    Not working in 2019.3.13f - do we need to open a new bug?

  4. 4fa85ad1215b84d57a1f5c1085255659?d=mm


    Feb 25, 2020 10:14

    NOTE: for people complaining that this bug still exists in 2019.3, read the bug report full body message. That might be fixed.

    What is not fixed in 2019.3 is that if you rightclick an asset in project window and select "Select Dependencies", the results shown in Hierarchy window list objects that have no dependencies to the target object.

    If you want that fixed, file a new bug report. Cheers!

  5. 3397e68ad576561a47b6817e99101b13?d=mm


    Jan 20, 2020 16:30

    This is NOT fixed in 2019.3.0f3, which is making my job really hard right now.

  6. 4b7de6d36068f703fc18475853caf1bf?d=mm


    Dec 13, 2019 12:19

    So this has been open since 2017, and it STILL doesn't work.
    Tried in version: 2018.4.13f1

    Have to say, that's a spectacular fail from support when they can't even make a simple search routine work :(

  7. 73064b9cb0c67721ed65ad5c442551d0?d=mm


    Dec 05, 2019 21:52

    This is not fixed in 2019.2.15f1

  8. 882056d85986aba6e63907e1cdae90d7?d=mm


    Nov 22, 2019 17:38

    Not fixed... 2019.2.9f1

  9. 73064b9cb0c67721ed65ad5c442551d0?d=mm


    Jul 10, 2019 21:26

    This is not fixed in 2019.1.5f1

  10. 372c5f32b49c3b001b542d3e418860f1?d=mm


    Jul 05, 2019 15:50

    Frustratingly enough, not only does this not work (as in "provide a correct result") with Unity 2018.3 here, but on top of that it also ends up *fully freezing Unity for several minutes* on some scenes, before eventually unfreezing and displaying a result (which is, of course, a completely wrong and pretty much unusable result anyway, as described in the issue).
    Freezing Unity for several minutes is just really not helping...

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.