Uses iOS 6 ASIdentifierManager class or identifierForVendor if the class is not available. Fallback on iOS 5 is to use app path UUID which is generated by iOS when installing the app
Conflicts:
Classes/BITCrashManager.m
Classes/BITHockeyHelper.h
Classes/BITHockeyHelper.m
* only define JIRA_MOBILE_CONNECT_SUPPORT_ENABLED if it's not already defined.
default is to disable it
* cleanup usage of JIRA_MOBILE_CONNECT_SUPPORT_ENABLED
it's always defined, so no need to check
if the user has UINavigationButton's text attributes customized
iOS 6 beta 4 calls viewWillAppear if a navigationButton is set
on the navigationItem in viewDidLoad (rdar://12214613)
As BITUpdateViewController thinks the view was already loaded
in viewWillAppear, the button state is not properly set.
Setting the navigationButton in init fixes this.
The flag shouldn't be required, and worked in the demo project absolutely fine. But from now to then there was an Xcode bug that made it required again and some non reproducible scenarios where reported by users where it doesn't work without the flag. To fix this for always and forever, we don't use categories any more.
- checkForUpdateOnLaunch was not used when it should
- checkForTracker should still work, if UpdateManager is disabled! (This needs to be refactored in a future version)
- Also fixes sending two update check requests on startup instead of only 1
- Also make sure that the requests are really send if checkForTracker is enabled, no matter if updateManager is disabled or checkForUpdateOnLaunch is disabled, but don't show the update alert in those cases
- Don't send usage information when run from the app store and checkForTracker is enabled
If the framework search path still has the path to an older PLCrashReporter framework set and that is set before the path to HockeySDK, then it would link against the old one causing the app to crash when trying to send a bug report, because the old PLCrashReporter version is missing some new properties.
The delegates can still be access and set directly, if the dev wants to have different classes implementing them.
For the general user this improves the ease of setup, because the submodules delegates don't have to be set specifically and by setting the delegate protocols in the header the missing required delegates will still be shown as warning
