UnityEvent triggers method on wrong component when 2 of same type are assigned (2018.2.2f1)

Here's the situation:

• One gameobject with:
  • a component containing a UnityEvent
  • a custom component, call it CustomBehaviourA
  • a 2nd custom component, call it CustomBehaviourB
• The initial UnityEvent has 2 entries assigned, e.g.:
  • CustomBehaviourA.DoSomething()
  • CustomBehaviourB.DoSomething()

When I call Invoke on the UnityEvent, it actually executes CustomBehaviourA.DoSomething() twice and does not execute CustomBehaviourB.DoSomething() at all.

This looks a lot like this problem on Unity Answers.

Is this a known bug? Has it been fixed since 2018.2.2f1?

 

Bump! Would be nice to get a second opinion.

 

There's no way to distinguish between two components of same type in Unity. I had same problem whith networking when added second gun script to player object trying to implement 2 hands shooting. I've just added GunID field to message and forgot bout that.