iOS inconsistensies

iOS6 will error ACErrorAccountNot found if you request access to accounts that do not exist, iOS7 will just ask for permission and allow you on your merry way
Merge pull request #6 from influitive/master

iOS inconsistensies
God forgive me. I am doing some questionable here. I need a shower.
 Get rid of BlocksKit. This will have to do as a cleanse for the horrible shit I did in the past.
Makes sense, I guess. Passing string to alertView message instead of Response dict.
Twitter does not care about keys.
Bump 0.2.10
Merge branch 'release/0.2.10'
Merge branch 'release/0.2.10' into develop
end
Merge branch 'release/0.2.10'
Added support for access not granted error for ACAccountStore requestAccessToAccountsWithType

For access not granted and no account, attempt to create one or login otherwise with performLoginForNewAccount

Fixed performLoginForNewAccount to only attempt saving credentials if access was granted otherwise continue on for oauth non-native based auth

Updated non-granted response to expected dictionary type

Fixed error handler to return not successful for completionBlock on performReverseAuthForAccount

Fixed potential issue when response may not contain oauth_token or oauth_token_secret.

Fixed more potential issues with creating a NSDictionary with nil values

Fixed issue using NSJSONSerialization when data parameter could be nil.

Updated AFOAuth1Client to ~> 0.3.0

Added userInfo property kOmniAuthTwitterUserInfoKeyOverrideExistingAccount to allow overriding existing account on saveAccount if account exists already.

Refactor publicProfile string to use stringByAppendingPathComponent instead of stringWithFormat.