nicklockwood/nullsafe

NullSafe is a simple category on NSNull that returns nil for unrecognised messages instead of throwing an exception

nullsafe's Issues

crash in xcode10 and ios12

iOS13.2 Null会崩溃

app occasionally crash in ios13.3.1

+[NSMethodSignature signatureWithObjCTypes:]: type signature is empty.

NSDictionary *total = [NSNull null]; crash

Nullsafe will crash when using in background thread.

We use the latest Nullsafe code in our product and find crashes like this:
SIGSEGV SEGV_ACCERR "-[NSNull(NullSafe) methodSignatureForSelector:] (NullSafe.m:81)"

The reason is that Nullsafe will find all the classes in the system and initialize one instance.
Some classes like UIWebView cannot initialize in background thread thus caused the crash.
A demo code is:
// This code will crash
dispatch_async(dispatch_get_global_queue(0, 0), ^{
UIWebView *v1 = [[UIWebView alloc] init];
[v1 loadRequest:[NSURLRequest requestWithURL:[NSURL URLWithString:@"http://www.baidu.com"]]];
});

Nullsafe's idea is great and we enjoy using it. Can you fix this in the coming version?

• (NSMethodSignature *)methodSignatureForSelector:(SEL)selector
  {
  @synchronized([self class])
  {
  dispatch_async(dispatch_get_main_queue(), ^{
  //push the code here may help.
  });
  }
  }

XCTest/XCTest.h' file not found。why？

XCTest/XCTest.h' file not found。why？

Private methods

I noticed that installing NullSafe (with Cocoapods) made the following being logged when the app runs:

CLTilesManagerClient: initialize, sSharedTilesManagerClient
CLTilesManagerClient: init
CLTilesManagerClient: reconnecting, 0x7fa1c5288290

This looks like a private Apple framework. Can I ship my app with this?

App run Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL initFileURLWithPath:]: nil string parameter'

闪退 ios12

Xcode 7 build warning

When compiling NullSafe in Xcode 7 I get the following warning:

NullSafe.m:128:17: warning: null passed to a callee that requires a non-null argument [-Wnonnull] [invocation invokeWithTarget:nil];

It seems like we might be able to remove this call and it resolves the issue (and still works in my tests)

how to handle “<null>” ??

how to handle “< null >” ??

null调用分类里面的链式语法方法还是会crash

null调用分类里面的链式语法方法还是不能处理，麻烦博主处理一下

NSDictionary *total = [NSNull null]; use the total crash

iOS12.4.1 NSNull is Crash

crashReason=+[NSMethodSignature signatureWithObjCTypes:]: type signature is empty.

jkhgj

jkhjkghjkj

-[NSNull(NullSafe) methodSignatureForSelector:] (NullSafe.m:72)

dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{

});

在这个线程中 发生了闪退

12.1.4,遇到NSNull还是会crash

why not creat a method signature directly to return?

why not creat a valid method signature to return in - (NSMethodSignature *)methodSignatureForSelector:(SEL)selector like this NSString *str = @"123"; NSMethodSignature *sign = [str methodSignatureForSelector:@selector(length)]; return sign; ? because in method - (void)forwardInvocation:(NSInvocation *)invocation you set target to be nil object, so the method signature of invocation is not important.

Is it necessary to look up method signature?

Because in the forwardInvocation method, set the target of the invocation to nil, so I think，whatever the methodSignature, it doesn't matter. why not just return "v@:" , the simplest methodSignature.

- (NSMethodSignature *)methodSignatureForSelector:(SEL)aSelector { NSMethodSignature *signature = [super methodSignatureForSelector:aSelector]; if (!signature) { signature = [NSMethodSignature signatureWithObjCTypes:"v@:"]; } return signature; }

How to get it work?

I imported to my project and if I try to set a value to NSNULL class in NSDictionary it crashes.

How to make it work so that it handles all null pointer exemptions.

signature = [someClass instanceMethodSignatureForSelector:selector];

[someClass instanceMethodSignatureForSelector:selector];
system: iOS12 device:iphone X crash

example:
id test= [NSNull null]
[test isequalTo:xxx] is Crash on IphoneX