NSLog in submitted app

Question

I had the misfortune of submitting an app with an NSLog still active. It very rarely fires, but I would like to know what are the chances of my app being rejected because of that?

I am NOT asking how to supress NSLogs. I already know how to. It is just a stray NSLog which made it in by mistake.

So what happened? Did the app get rejected on grounds of having too many NSLogs, or was the accepted answer on the money? — Dan Rosenstark, Jan 03 '12 at 00:19
@Yar: no, it went through with no problems at all. I later sent in a corrected version, but I doubt they noticed the issue. — John Smith, Jan 03 '12 at 01:34
Thanks, I really appreciate it. I think I removed mine, but some aggressive GIT operations after-the-fact leave me in doubt :) — Dan Rosenstark, Jan 03 '12 at 01:38

score 10 · Accepted Answer · answered Sep 30 '10 at 10:47

10

I don't think there will be any problem. I've submitted several apps containing NSLog output which were accepted flawlessly.

answered Sep 30 '10 at 10:47

tobiasbayer

10,069
4
43
64

1

Do a search here for Dlog debug, you should find a preprocessor directive that'll only print nslog in debug mode. Therefore, no worries when you submit app to store. Code will get stripped. – Jordan Sep 30 '10 at 11:05
You are answering your own question which I did not ask, – John Smith Sep 30 '10 at 15:48
Tob, sorry for the downgrade. I give you the check – John Smith Sep 30 '10 at 19:38

NSLog in submitted app

1 Answers1