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.
NSLog() output on the simulator does indeed show up in the Console Mac OS X application. Go to All Messages and then filter based on your app name to get rid of the fluff, and run again. You'll see it in your output if the NSLog code is actually being hit during the execution of your program.
dSYM files, go to Project->Edit Project Settings->Build->Build Options->Debug Information Format and make sure you have a dSYM file. You should keep these files around for every build you release. The iPhone SDK generates these files by default but you will need to turn in on manually for Mac builds.
In short, os_log makes it possible for you to add logs to your application in a more structured way. It allows you to filter your logs in the Console. app application. This way, you get a better view on why a certain error occurred. You can see it as an advanced version of the Xcode Console.
We can print the double value using both %f and %lf format specifier because printf treats both float and double are same. So, we can use both %f and %lf to print a double value.
I don't think there will be any problem. I've submitted several apps containing NSLog output which were accepted flawlessly.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With