Use `kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly` instead of `kSecAttrAccessibleWhenUnlockedThisDeviceOnly` when storing data into the keychain to allow the data to be also fetched when the app is launched in the background
Notify the developer about the issues by logging a warning to the console when the SDK is initialized more than once or startManager is invoked multiple times
If the `configure` initializers or `startManager` are invoked multiple times, this can cause undefined behaviour and crashes. Hence we simply ignore if they are invoked multiple times.
Resizable iPhone causes modal presentations not to be full screen any longer, so we always should use the views width and never the device-width for the version update data presentation. This also works just fine when build with iOS <= 7.1.x
The values are used by the `BITCrashManager` to attach to a crash report and`BITFeedbackManager for assigning the user to a discussion thread.
The value can be set at any time and will be stored in the keychain on the current device only! To delete the value from the keychain set the value to `nil`.
These properties are optional and alternatives to the delegates. If you want to define specific values for each component, use the delegate instead which do overwrite the values set by these properties.
Also fixed a typo in the delegates documentation.
Goal: make BITFeedbackComposeViewControllerDelegate usable for the view controller used by BITFeedbackListViewController
- The delegate is automatically set to the global BITHockeyManager delegate
- When invoking your BITFeedbackComposeViewController, it is possible to overwrite the delegate
This results in crash report alerts by default showing the `Always` button, so they will never be asked again and future crash reports will be send automatically.
If this occurs, the user has to authenticate every time the app starts or even when the app comes into foreground, depending on the `restrictionEnforcementFrequency` setting
If there would not be any rootViewController (which iOS now requires though), it could happen that the auth window would not disappear upon successful authentication. The app would have had to be killed and started again to proceed.
- The authentication controller now sets the buttons tintColor always to the default blue color. This fixes white UIWindow tintColor, since the auth view is using white as background.
- Navigation controllers for modal views now also set the tintColor of the navigationBar to the default blue color on iOS 7, if the developer did not set the `navigationBarTintColor`. This fixes white UIWindow tintColor for feedback and beta update modal views as they are defined to use the default style.
