iOS Annoying error

[drf1229]

For some odd reason, my app returns this error:
warning .o file ... more recent than executable timestamp

Is it possible to diagnose this error without giving further information? If not, I can provide more specifics.

 

[PhoneyDeveloper]

Check the time on your computer. Is it correct?

Delete the build folder and try again.

Is this a linker error?

If nothing fixes this then post the link line from your build transcript and the lines that include the error in the build transcript.

 

[drf1229]

Check the time on your computer. Is it correct?

Delete the build folder and try again.

Is this a linker error?

If nothing fixes this then post the link line from your build transcript and the lines that include the error in the build transcript.

Thanks for your reply! My time is correct (or atleast I think it is since I set it to automatic) and I deleted the build folder. Since then I no longer get this error but my app crashes at the same spot it did during the error. Is the build transcript the display from [Session started] in the debugger console? If so, here it is:

[Session started at 2009-12-22 18:23:23 -0500.]
2009-12-22 18:23:23.950 TiltTimer[34155:20b] 36.000000
GNU gdb 6.3.50-20050815 (Apple version gdb-967) (Tue Jul 14 02:11:58 UTC 2009)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin".sharedlibrary apply-load-rules all
Attaching to process 34155.
(gdb)

Thanks for your help once again!

 

[PhoneyDeveloper]

OK, I think that error/warning comes from the debugger. It's telling you that when you tried to debug a certain file that file had been recompiled. If it's gone away then you've gotten everything up to date so the build transcript isn't required anymore (what you showed is the debugger console, not the build transcript).

You just have to debug your crash in the usual way to find the bug in your app.

 

[drf1229]

Ok, thats what I thought. Thanks for your help!