NSLog in submitted app

views:

answers:

+1 Q:

NSLog in submitted app

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.

+2 A:

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

tob 2010-09-30 10:47:42

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 2010-09-30 11:05:25

You are answering your own question which I did not ask,

John Smith 2010-09-30 15:48:59

Tob, sorry for the downgrade. I give you the check

John Smith 2010-09-30 19:38:11

I don't think that you can simply leave NSLog in your production code, it's very heavy operation on the iPhone, it even crashes your app if you tries to print a lot. This is what you should do!

sfa 2010-09-30 12:50:48

It already done. I know what I should do. The app is already in review.

John Smith 2010-09-30 15:49:34

I don't see any point for whom to put a downvote here. the answer is correct and right into the question, congrats on doing that!

sfa 2010-09-30 17:05:38

The question is: should I resubmit the binary, or hope for the best? I knew what was needed to be done, it just slipped through and I only realized it after 6 days of waiting for the review.

John Smith 2010-09-30 19:37:12

a downvote is usually for a spam answer or nothing value, I give you the answer to your RIGHT question. If your app crashes, what is the chance for it to be approved by Apple? Think twice before doing that.

sfa 2010-09-30 20:37:29

I thought twice, and it was, as you said "nothing value".

John Smith 2010-09-30 22:45:55

ansaurus

tags:

views:

answers:

NSLog in submitted app

related questions