Skip to content

WARN Invalid reference found, unknown object! #253

Open
cccooolll opened this Issue Sep 22, 2012 · 10 comments

5 participants

@cccooolll

WARN | Invalid [[NSFileManager defaultManager] reference found near MyClass.h@199, unknown object : [NSFileManager !

many warning when I add some sample code in my comments

/**
 [[NSFileManager defaultManager] isFolder]
 */
@tomaz
Owner
tomaz commented Sep 24, 2012
@matzew
matzew commented Oct 22, 2012

This is still the case in 2.1 (build 840).

This comment:
https://github.com/aerogear/aerogear-ios/blob/appledoc/AeroGear-iOS/AeroGear-iOS/AGPipeline.h#L22

causes these warnings:

WARN | Invalid [NSURL URLWithString:@"http://todo-aerogear.rhcloud.com/todo-server/"] reference found near AGPipeline.h@22, unknown object : NSURL !
WARN | Invalid [AGPipeline pipeline:serverURL] reference found near AGPipeline.h@22, unknown method!

@matzew
matzew commented Oct 22, 2012

Also - I think even worse - these URL is rendered twice, see:

http://people.apache.org/~matzew/AppleDocDoubleURL.png

@tomaz
Owner
tomaz commented Oct 22, 2012

2.1 didn't touch Markdown handling; until I change to parser with callbacks, such errors will be very difficult to deal with. I wrote about this in other tickets and my blog.

FYI: 3.0 uses sundown and feels much more reliable.

@matzew
matzew commented Oct 29, 2012

@tomaz thanks for the feedback, can you point me to the 3.0 branch ?

@tomaz
Owner
tomaz commented Oct 29, 2012

It's called experimental because it's still very early in dev process. Besides parsing it doesn't do much.

I just started work on Markdown parsing couple of months ago, but don't think I've pushed it to GitHub yet. Then I had to jump to other projects so effectively it lied stagnant for all this time. My current engagement is slowly coming to an end, so I expect to come back in the following week(s).

@neilgall

Is there a workaround for this warning in the 2.x version?

@tomaz
Owner
tomaz commented Mar 28, 2013

Unfortunately not...

@rsanchezsaez

Is there any update on this issue? It seems to produce a lot of warnings when building ResearchKit documentation.

@rsanchezsaez

A workaround for this issue is now possible on the referenced pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.