Make sure the SDK doesn't crash comparing data when the server returns invalid data
Merge branch 'develop' of github.com:bitstadium/HockeySDK-iOS into develop
Remove unnecessary checks
Fix double definition of private method and add handling for unlikely malloc failure
Use Keychain for some data

- Added SFHFKeyChainUtils with BIT prefix
- Save username, email or userid (if provided by the app or the user) in the keychain instead of user defaults or property files
update podspec post_install hook to use library_representation
Merge pull request #40 from bdewater/develop

update podspec post_install hook to use library_representation
Suggest only CONFIGURATION_AppStore
Bugfix for a push animation warning appearing when presenting feedback view in a popover and requiring userdata
More changes to the behavior of first forced user data and compose UI presentation

This is a change to previous behavior! Now the SDK by default shows the user data UI and subsequent compose UI always modally to ensure proper functionality on all scenarios the feedback viewer can be presented.

The new property `showFirstRequiredPresentationModal` in `BITFeedbackManager` can be set to `NO` if the previous behavior of pushing the UI and Compose view onto the stack, when those are being forced to be shown on the first presentation of the feedback UI. Especially if you present the UI in a popover, you should NOT change this property!
Adjust size of name and email textfields in feedback UI

Now resizes with device rotation on non iPad and uses max width on both device types.
set ident-width of BitAttributedLabel to 4 spaces

seems this is the used one, so set it in the xcodeproject
fix mem leak
fix warning 'multiple methods length found'

* method accepts either NSStrings and NSAttributedString: assert on that
* explicitly cast to NSAttributedString to get rid of ambiguity warning
fix mem-leak analyzer warning

Although the analyzer is wrong here (highlighFramesetter property is synthesized), it doesn't hurt
to use the instance variables.
fix analyzer warning

it's somewhat more clear to release and set to nil,
then store a new reference directly in the ivar.
Merge pull request #43 from diederich/fix/analyzerWarnings

Fix analyzer warnings