search

tomaz / appledoc

Objective-c code Apple style documentation set generator.
http://gentlebytes.com
4.19k stars 644 forks source link

NSInvalidArgumentException when building w/ Xcode Version 5.0 (5A1412) #402

Open dmcgloin opened 11 years ago

dmcgloin commented 11 years ago

Project built fine in Xcode 4.6.3

Full error:

appledoc[733:707] -[NSCFNumber length]: unrecognized selector sent to instance 0x5c7 ERROR: NSInvalidArgumentException: -[NSCFNumber length]: unrecognized selector sent to instance 0x5c7 appledoc version: 2.2 (build 961)

Going to try some experiments to see if I can find root cause

dmcgloin commented 11 years ago

Quick analysis after building and debugging appledoc from within Xcode:

I am using a plist file to specify my settings, passing the plist file as argument to appledoc.

In my plist file, the "--verbose" property was defined as a Number type (not a String).

The unrecognized selector error was encountered here: [NSScanner scannerWithString:self.verbose] because self.verbose was of type NSNumber instead of NSString.

Changing the plist "--verbose" property type to String resolved the issue.

I'm not sure why the plist parsing is now creating the object as a NSNumber. I did not go that deep.

Actually, I'm still confused why this worked before.

robvdveer commented 11 years ago

Possibly related to https://github.com/tomaz/appledoc/issues/389

—

http://simplicate.weebly.com

On Wed, Sep 11, 2013 at 7:35 AM, dmcgloin notifications@github.com wrote:

Quick analysis after building and debugging appledoc from within Xcode: I am using a plist file to specify my settings, passing the plist file as argument to appledoc. In my plist file, the "--verbose" property was defined as a Number type (not a String). The unrecognized selector error was encountered here: [NSScanner scannerWithString:self.verbose] because self.verbose was of type NSNumber instead of NSString. Changing the plist "--verbose" property type to String resolved the issue. I'm not sure why the plist parsing is now creating the object as a NSNumber. I did not go that deep.

Actually, I'm still confused why this worked before.

Reply to this email directly or view it on GitHub: https://github.com/tomaz/appledoc/issues/402#issuecomment-24214374

tomaz commented 11 years ago

Am abroad at my client site this week, then will be very busy till end of september, so will have to wait till then or someone chimes in with solution....

robvdveer commented 11 years ago

My first analysis: the documentation is wrong. :) wink

"No matter what the documentation says, the source code is the ultimate truth, the best and most definitive and up-to-date documentation you're likely to find. "

http://www.codinghorror.com/blog/2012/04/learn-to-read-the-source-luke.html

—

http://simplicate.weebly.com

On Wed, Sep 11, 2013 at 10:20 AM, tomaz notifications@github.com wrote:

Am abroad at my client site this week, then will be very busy till end of september, so will have to wait till then or someone chimes in with solution....

Reply to this email directly or view it on GitHub: https://github.com/tomaz/appledoc/issues/402#issuecomment-24220415