Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's a known bug with the latest XCode. This happens with some projects which are migrated from XCode 3.X to the new version. For some people it seems to help to go to the organizer, and in the project tab delete the derived data for the project where code sense does not work correctly.</p> <p>If you have a small project, it might also help to create a new project in XCode 4 and import the files from the XCode 3 project.</p> <p><strong>Update:</strong> XCode 4.0.1 made the situation a bit better, at least in some of my projects I have syntax coloring and code sense back. But it's still far from fixed.</p> <p><strong>Update 2:</strong> XCode 4.0.2 did not change much. It seems that the problem is related to subprojects, specifically static libraries. According to comments of <a href="http://blog.slidetorock.com/xcode-4-code-sense-autocompletion-problems" rel="noreferrer">this blog post</a> some people were successful by changing header search paths from relative to absolute paths, e.g. instead of <code>Foo/Bar</code> use <code>$(SOURCE_ROOT)/Foo/Bar</code>. This together with switching all projects to XCode 3.1 format and to use LLVM 2.0 fixed a lot for me as well. It's not perfect yet, but usable.</p> <p><strong>Update 3:</strong> After converting the sub projects to independent projects and putting them in a <a href="https://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/NewProject/NewProject.html#//apple_ref/doc/uid/TP40010215-CH2-SW4" rel="noreferrer">workspace</a> (aka <em>the XCode 4 way</em>) I have now full syntax highlighting and code completion back.</p> <p>My current environment is now a XCode 4 workspace with each projects being 3.1 compatible (as opposed to the default which is 3.2), LLVM GCC 4.2 (system default) and the header search paths are still absolute (using <code>$(SOURCE_ROOT)/.../</code>).</p>
    singulars
    1. This table or related slice is empty.
    1. POCode loses syntax color in Xcode 4
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAlfonso
    1. USAlfonso
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCode loses syntax color in Xcode 4
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI am facing the exact same issue and it is very irritating. 4.0.1 did not made the situation any better in my case, but I read somewhere that turning off the static analyzer in the builds settings can solve the problem. And it did in my case.
      singulars
      1. PO
      1. USromrom
    2. COCan also happen with vanilla Xcode 4 projects. Happens to me with a subproject where I change header search path to include headers from that subproject.
      singulars
      1. PO
      1. USZac Bowling
    3. COI was able to fix my code sense problem when entering the full path. But when I used "$(SOURCE_ROOT)/../OtherProject/**" as user header search path, code sense stopped working again although the project compiled correctly. It seems Code Sense doesn't like relative paths anywhere, like backtracking within a path with ../
      singulars
      1. PO
      1. USLearnCocos2D
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload