• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Problems with Indexing in Xcode 8
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems with Indexing in Xcode 8


  • Subject: Re: Problems with Indexing in Xcode 8
  • From: Simon Wilson <email@hidden>
  • Date: Mon, 07 Nov 2016 13:47:51 +0100

Thanks for your input.

> So have you tried building all of the targets in your project to make sure they all work?

The project is structured as follows:

FrameworkA
  -> FrameworkB
  -> FrameworkC
    -> FrameworkD
  -> FrameworkD

with “->” denoting a dependency.

These are all private frameworks of ours. All build without a single warning in isolation. FrameworkC builds perfectly without errors when #importing FrameworkD, yet FrameworkA raises errors when #importing FrameworkD directly.

> But yeah, in general I do run into a lot of cases where the live-syntax-check shows bogus errors that vanish when I do a real compile, or conversely where it won’t highlight real errors until I compile.

Xcode has generally been pretty good in the past for us. Sure, we also have intermittent issues with syntax highlighting, but nothing that couldn’t be fixed by switching target platform or restarting the IDE.

But we’ve never seen anything like this before.

Cheers,
Simon

> On 4 Nov 2016, at 18:58 PM, Jens Alfke <email@hidden> wrote:
>
>
>> On Nov 4, 2016, at 3:11 AM, Simon Wilson <email@hidden> wrote:
>>
>> I have a framework project that builds without errors or warnings, but whenever I open a source code file I get an error displayed next to the first #import statement for a framework dependency. The error text is:
>>
>> ‘<MyFramework/MyFramework.h>’ file not found’
>
> I’ve had this happen to me. Sometimes I couldn’t find any reason, but IIRC sometimes it’s because some other target (that isn’t in the current scheme) does actually have such an error on that line. So have you tried building all of the targets in your project to make sure they all work?
>
> But yeah, in general I do run into a lot of cases where the live-syntax-check shows bogus errors that vanish when I do a real compile, or conversely where it won’t highlight real errors until I compile. This has been going on since at least Xcode 7. I’ve just learned to grit my teeth and live with this, because it’s too intermittent to file bug reports on.
>
> —Jens


 _______________________________________________
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


References: 
 >Problems with Indexing in Xcode 8 (From: Simon Wilson <email@hidden>)
 >Re: Problems with Indexing in Xcode 8 (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: Problems with Indexing in Xcode 8
  • Next by Date: Swift Outlet collections in Xcode 8 (macOS)?
  • Previous by thread: Re: Problems with Indexing in Xcode 8
  • Next by thread: Swift Outlet collections in Xcode 8 (macOS)?
  • Index(es):
    • Date
    • Thread