Great solution

Just hit the same issue in in 4.3.4f1 and found this page after a lot of searching. But, shouldn't this have been solved versions ago?

I see the exact same as NICOLASVIDAL
* OnTriggerEnter2D is raised each frame (rotating or not)
* OnTriggerExit2D is never raised

They write it's a duplicate of http://issuetracker.unity3d.com/issues/ontriggerstay2d-is-called-not-properly, but that should be fixed after ver. 4.3.0f4. And I don't see it to be the same issue??

What can we do to reopen this issue?

Same Problem here OnTriggerEnter2D behaves as OnTriggerStay2D

Can't vote so I'll leave a comment instead - this issue is not resolved. 4.3.4f1

This is causing some major headaches on my project aswell.

Still happening, this is not resolved.

Still happening in 4.3.4f1

- still found in 4.3.2f1

OnTriggerEnter2D behaves as OnTriggerStay2D when the object is scaled

Steps to reproduce from scratch :
- create an object with a Rigidbody2D and a Collider2D (trigger)
- create another object with a Collider2D and a RigidBody2D (trigger)
- set gravity scale to 0 for both of them
- set the first one as a child of the second one
- attach a script with debug messages in OnTriggerEnter2D and OnTriggerExit2D on the child
- press play, make the child rotate inside the parent
=> Unexpected behaviours :
* OnTriggerEnter2D is raised each frame we rotate the child
* OnTriggerExit2D is never raised

The same problem exists with OnCollision2D and non trigger colliders.