Here’s a handy tool for running over your OS X apps to look for resource issues — Cong:
What is Cong?
To check for leaks, you use leaks or Instruments. To check for obvious (or less obvious) bugs, you use gcc and LLVM options, or you use the Build and Analyze feature of Xcode. To check that your code works, you test it. But what do you use to check the resources of the bundle of your application? Say hello to Cong.
Checking what is obvious to stop being oblivious
Cong checks multiple points and details that can seem obvious but which are not always known by everyone. Your application may be running fine, may have won Awards and still be not perfect. For instance, did you know that there is a limited set of characters allowed for a bundle identifier and that ‘_’ (underscore) is not one of them? Did you know that the recommended encoding for .strings files is UTF-16? Did you know that the CFBundleGetInfoString key is deprecated for Info.plist files?
Looks handy, yep. So we ran it over our last OS X release, and …
… and so it actually is handy. Fancy that. OK, straight into our regular toolchest that one goes!