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.
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?
Nobody wants to spend his or her time checking Apple`s documentation and inspecting files one by one when you could be catapulting birds on green pigs. Checking your application with Cong is easy.
You just need to drop your application on Cong`s icon in the Dock or on its default window. There`s no step 2.
When Cong has finished inspecting your application, it will display for each problematic file the glitches it has found inside it. Cong provides data about 3 types of glitches: Errors, Warnings and Notes.
Here are some key features of "Cong":
Supported bundle formats:
· Application
· Framework
· Preferences Pane
Checklist:
Files hierarchy:
· Missing files
· Missing symbolic links
· Incorrect file type
Info.plist files:
· Check XML text format
· Deprecated keys
· Use of private keys
· Invalid value
· Invalid value type
· Invalid value format
· Missing required keys
· Missing files referenced by values
.strings files:
· Improper encoding
· Improper format
· Empty file
· Duplicate entries
· Missing `;`
· Missing `=`
· Typos
· Mix of localized and non localized files
.h files:
· Useless header files
· Header files in Resources folder
.icns files:
· Missing representation
