how to add catagory in the framework about ios-framework HOT 12 CLOSED

You need to use something like this macro found in Nimbus:

https://github.com/jverkoey/nimbus/blob/master/src/core/src/NIPreprocessorMacros.h#L48

from ios-framework.

hi, thank you for your reply. I write a test catagory like this:
————————————————————————————
#import "NSDictionary+SafeObject.h"
NI_FIX_CATEGORY_BUG(NSDictionarySafeObject)
@implementation NSDictionary (SafeObject)

• (id)safeObjectForKey:(id)aKey {
  if (![[self objectForKey:aKey] isKindOfClass:[NSNull class]]) {
  return [self objectForKey:aKey];
  }
  else
  return nil;
  }
  @EnD
  ——————————————————————————————

But I still got the same error in console:
"Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFDictionary safeObjectForKey:]: unrecognized selector sent to instance 0x68a3ac0'"

from ios-framework.

Also make sure that you are using the -Objc linker flag in your application.

from ios-framework.

Just to prevent confusion, the correct flag is -ObjC

from ios-framework.

I still have this issue, are you sure this works?

from ios-framework.

I was able to get this fix working however i didn't need the NI_FIX_CATEGORY_BUG macro.

from ios-framework.

Did you fix it by using -force_load or -all_load? If so, those flags are particularly dangerous and is why the NI_FIX_CATEGORY_BUG macro exists.

from ios-framework.

No I did not have to use -force_load or -all_load. I ran into this problem when I was using JSONKit in my framework. The "JSONKitSerializing", "JSONKitDeserializing", and "JSONKitSerializingBlockAdditions" categories were not loading and caused a problem similar to boboboa32's error (can not respond to the selector).

from ios-framework.

Ah ok. What was your fix then?

from ios-framework.

Simply by adding -ObjC to "Other Linker Flags" under the Build Settings tab of my project target (the project that is including the framework).

from ios-framework.

Sweet :)

from ios-framework.

I wonder, why -ObjC is still needed, whereas standard frameworks do not require it? What do we lack in this custom framework?

from ios-framework.