Such inexplicable exceptions are often a result of an unclean xib
file.
Open the xib
in xcode, select File’s Owner and click on the “Connection Inspector” (upper right arrow), to see all outlets at once.
Look for !
s which indicates a missing outlet.
More Related Contents:
- How to print out the method name and line number and conditionally disable NSLog?
- Is there a way to suppress warnings in Xcode?
- How does an underscore in front of a variable in a cocoa objective-c class work?
- NSString property: copy or retain?
- Having trouble adding objects to NSMutableArray in Objective C
- Xcode build failure “Undefined symbols for architecture x86_64”
- Objective-C Introspection/Reflection
- Hidden Features of Xcode
- @synthesize vs @dynamic, what are the differences?
- Managing multiple asynchronous NSURLConnection connections
- Xcode doesn’t show the line that causes a crash
- Objective C NSString* property retain count oddity
- Sorting two NSArrays together side by side
- Difference between self.var and simply var
- If “a == b” is false when comparing two NSString objects
- Avoiding “NSArray was mutated while being enumerated”
- Embed font in a mac bundle
- With ARC, what’s better: alloc or autorelease initializers?
- 2D arrays using NSMutableArray
- RootViewController Switch Transition Animation
- Class Foo is implemented in both MyApp and MyAppTestCase. One of the two will be used. Which one is undefined
- Animate infinite scrolling of an image in a seamless loop
- Front most window using CGWindowListCopyWindowInfo
- NSPrivateQueueConcurrencyType Not saving properly
- Properties and Instance Variables in Objective-C
- Objective C – getting line number or full stack trace from debugger error?
- Looping using NSRange
- Xcode linker error: file too small for architecture x86_64
- What’s the difference between [NSNull null] and nil?
- +[NSString stringWithString:] — what’s the point?