Return to Question

I'm using NSInvocation as a choke point in my app to help manage threading and reduce the amount of redundant code. The purpose of this class is to pass arguments from the view controllers to the API project on a background thread and return success/error/ on the main thread. I also have a log callback that logs api events in the background.

1. Am I creating retain loops by passing self in any of the blocks?
2. Is this possible without using retainArguments: in the NSInvocation category?
3. Are there any other issues with this implementation?

I'm using NSInvocation as a choke point in my app to help manage threading and reduce the amount of redundant code. The purpose of this class is to pass arguments from the view controllers to the API project on a background thread and return success/error on the main thread. I also have a log callback that logs API events in the background.

1. Am I creating retain loops by passing self in any of the blocks?

2. Is this possible without using retainArguments: in the NSInvocation category?

3. Are there any other issues with this implementation?