I just got a very similar weird error when I could no longer access the properties in my superclass, and xcode is a givine to me compiler of errors saying "(*) undeclared (first use in this function)". However, in the past I had no problems ...
The problem was that I introduced typos at the top of my .m file, and the output of the xcode compiler was misleading to me. In particular, I had @synthesize operators in which the properties were written with an error, either in the synthesis expression or in the corresponding variable in the header file.
If you have @synthesize operators or other declarations, examine them with a thin jagged comb (i.e., what lines do you enter recently?) Or even comment out a block of them to see if you can compile and narrow down the culprit again .
Again, compiler errors were very misleading, so it was very difficult to debug. Although, like 99.9% of cases, the error was mine. :)
kris
source share