Re: Xcode 4 isn't always able to jump to analyzer warnings
Re: Xcode 4 isn't always able to jump to analyzer warnings
- Subject: Re: Xcode 4 isn't always able to jump to analyzer warnings
- From: Joar Wingfors <email@hidden>
- Date: Tue, 19 Apr 2011 15:17:32 -0700
On 19 apr 2011, at 14.46, G S wrote:
> > Is this a known problem or is there a workaround, or should I submit a bug?
>
> There's an inversion of this problem where Xcode will highlight errors and warnings in your code, but the things it's complaining about no longer exist. No amount of saving, restarting, whatever will clear these erroneous messages.
>
> Turns out that these are left over from a build of a different target. For example, you build for simulator and then device. Xcode will often continue to present phantom error messages referring to nonexistent code, until you rebuild every target.
I think that this is the intended behavior - Issues are presented for all schemes, not just the active scheme. There is a filter for the issue navigator to only show issues for the active scheme, but it doesn't affect all places where issues are shown.
If you're not a fan of this behavior, please file a bug report and let us know.
j o a r
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden