Blocks are not working

[davidhorvath]

Hi

If you use other cocoaPods , (e.g : TapjoySDK) beside UIAlertView+Blocks the blocks are not returning.

[ryanmaxwell]

Hi - I've used this pod with other pods many times - Perhaps this is a case of category collision? The TapjoySDK is closed-source, so I can't tell if they are doing anything to UIAlertView, but it seems to be problem when using this pod in conjunction with TapJoy. If I find a workaround i'll post it here.

[davidhorvath]

Yeah, i thought it's not necessarily the problem with your pod but i wanted you to know.
Thanks for the answer.

[macinux]

I have the same problem. Just wonder if there is any workaround available. I have been changing the category name and method name. but no luck

[ryanmaxwell]

@macinux are you using the same library (TapJoy) or is another incompatibility?

[macinux]

yes. same library (TapJoy). thanks

[davidhorvath]

Unfortunately i had to use TapJoy library so i stopped using this category.
My solution was to set my block as a property and called that from clickedButtonAtIndex.

typedef void (^TapBlock) ();
@Property (nonatomic, copy) TapBlock savedTapBlock;

• (void)showAlertWithBlock:(TapBlock)block
  {
  self.savedTapBlock = block;
  // Show alertView
  }

• (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex
  {
  // ...
  if (_savedTapBlock)
  {
  _savedTapBlock();
  }

  // ...
  }

[ryanmaxwell]

Thanks @davidhorvath for sharing your solution. It would be good to find a permanent workaround

[AzotKZN]

The bug also repeated to me. After adding the lib: Tapjoy

[ryanmaxwell]

They should call it Tapsad.

[mattwilliamson]

This is a category name collision. If you just change to (Blocks2) for example, it will work.