onProfileUpdate Listener condition update/bugfix

Can you give a specific instance where this is not fired?

One example is if we update a user's usergroup through code, for example (rather than through the UI) and don't edit any other field.

$changes will only have one entry, so the extra condition will stop the listener from firing.

Why? The condition is => if it is one entry and if this entry is last_activity and not "if it's one entry"

\count( $changes ) === 1 AND isset( $changes['last_activity'] )

4 hours ago, Steven W. said:

One example is if we update a user's usergroup through code, for example (rather than through the UI) and don't edit any other field.

$changes will only have one entry, so the extra condition will stop the listener from firing.

I tested this specifically and it works just fine.

This was a misunderstanding, I got it crossed with something else.  This can be closed.