It turns out NSInvocation is generally unsafe for sending messages with object arguments, and should almost never be used for such. PR #8 switched over to using NSInvocation instead of storing target/action pairs separately. Now, NSInvocation will still store the target, action, and method signature, but will no longer be invoked to send the message.
It turns out NSInvocation is generally unsafe for sending messages with object arguments, and should almost never be used for such. PR #8 switched over to using NSInvocation instead of storing target/action pairs separately. Now, NSInvocation will still store the target, action, and method signature, but will no longer be invoked to send the message.