The new property will cause the app to generate a new `installString` value every time the app is cold started.
The property is only considered in App Store Environment, since it would otherwise affect the `BITUpdateManager` and `BITAuthenticator` functionalities!
Default is NO.
When the authentication mechanism couldn't save the auth token to the keychain, now only show a message in the console. The user will have to login on the next app start anyway until the developer fixes the keychain signing or entitlements issue.
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.
remove dispatch_once. It should be safe to call this multiple times.
Although in the default use case this makes pretty much no sense,
but for the demo app it's nice to have.
* factor out common validate method
* call it in authenticate and after validation-error was dismissed
* don't reset identification if validation failed - it might have only been
a short network outage.
This solves multiple issues:
- Possible crashes at startup because the app is already in the process of presenting another modal view. This way the developer can make sure that only one modal view is being presented
- If the app is showing e.g. a login view on startup, it is now not needed to turn off automatic mode and setup the complete auth workflow manually and simply invoke `authenticateInstallation` after the login view is either fully presented (`viewDidLoad` finished) or the user did log in
This helps especially in case of a custom URL scheme, so that
BITAuthenticator doesn't reset the identification token if a URL
is passed in that wasn't meant to parsed by BITAuthenticator.
fixes#70
