Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a4
Issue ID
1056665
Regression
No
GameObject.Find returns inactive objects
To reproduce:
1. Open the attached project (New Unity Project (36).zip)
2. Open the Sample Scene
3. Enter Play mode
4. Observe the console: all three objects are found, even though the game object "3" is inactive
Expected: GameObject.Find should only return active game objects, as the documentation states
Reproduced in 2017.1.4p2, 2017.2.3p2, 2017.3.2f1, 2017.4.6f1, 2018.1.7f1, 2018.2.0f1, 2018.3.0a4
Comments (1)
-
StarGamingNetwork
Jan 14, 2022 11:54
This a bad decision to not fix. The documentation clearly states the correct behavior and can cause days of debugging as the UWP does return null if the object is inactive. It is so much easier to catch these in the editor instead of the hard to use UWP debugger except it doesn't happen in the editor. Also keep in mind other platforms may do this as well. I did not test them.
I would hope you would change the editor at least if building for UWP or change the documentation and UWP to match the editor.
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
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
- [Multiplayer TPS Sample] Grenade launcher explosion misses the Player when the Collider count exceeds HitColliderBuffer
- OS Notification Documentation is missing when following hyperlink in Notifications Settings in Hub
- Canvas Scaler sets local transforms (Position, Rotation, Scale) to 0 when Canvas is edited in Prefab Mode
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.