Bug solved! The name of class A conflicts with the name of class B… [but they're the same class?]
October 26th, 2007
I have just done a victory dance for a problem that has plagued me for somtime now, its a random error that decides when it will and won’t show giving the lovely descriptive error:
The name of this class, XXX, conflicts with the name of another class that was loaded …
This is completely down to time stamps on the computer where the files have been saved and the computer when the files are compiled. In my case, the server where all my classes are stored was 2 minutes ahead of my computer - so when the compiler saw the file - it cant really understand why there’s a file from the future and throws its toys out the pram resulting in a compile error.
you may even be experiencing this if your sending your files to a time zone behind your one - same problem as described above.
I solved this problem by making sure the servers time is synced to “Apple Europe (time.euro.apple.com)” and so it my computer, this way, they are running to the same second - after i did that - i made sure all the effected files had been re-saved with the new timestamp - and wola!
May 12th, 2008 at 3:49 am
Yes, very annoying bug. Thanks for clarifying it!