iphone - Is there any danger in leaving NSLog statements when building an app for distribution?

Question

For some reason, during my development cycle I find myself deleting NSLog statements that I had inserted to aid in debugging. I don't really know why I have this habit, I just do it.

On occasion, during development I'll find that I'll run into a problem I've had before, and then wind up re-adding an old NSLog statement. And then deleting it again later.

Is there any good reason to delete NSLog statements? From my experience leaving one or two in hasn't caused any app rejection. And since, to my knowledge, they don't log anything anywhere when an app is in distribution (please correct me if I am wrong on this), it doesn't seem like they are harming anything. Is there a performance hit that I should be worried about?

Answer 1

What I do is add a macro that does the logging only when I am in Debug mode. Put this in your <APP_NAME>_Prefix.pch file

#ifdef DEBUG
#define DebugLog( s, ... ) NSLog( @"<%p %@:%d (%@)> %@", self, [[NSString stringWithUTF8String:__FILE__] lastPathComponent], __LINE__,  NSStringFromSelector(_cmd), [NSString stringWithFormat:(s), ##__VA_ARGS__] )
#else
#define DebugLog( s, ... ) 
#endif

As a bonus to the regular log, you get filename, method name, and line number.

Then in the project info, add this under the debug build only. It goes in the User-defined sections under GCC_PREPROCESSOR_DEFINITIONS:

DEBUG

Then replace any of the NSLog's you have in your project with DebugLog (it takes the same args as NSLog) and you won't have to worry about releasing debug statements live.

In answer to your question, logging can slow down the performance of an app and unless you require them for help debugging in the wild, I would leave them out.