This should fix https://github.com/bitstadium/HockeySDK-iOS/issues/181
It's the best I could come up with so far. We make sure the number of sections and messages doesn't change while the UI is redrawn on rotation and updating it afterwards again.
Older devices (iPhone 4S and iPad 3 running iOS 8) would still show a previously captured screenshot instead of the current one, because it takes too long to get the image from the Asset Library than the assumed 0.5s. Increasing to 1.5s fixes the issue also for these.
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.
This fixes an issue of the following scenario:
- Autosending crash reports is disabled, so alerts appear
- The app crashes
- The app restarts, shows the UI and sending is approved
- The device is offline can't send the report
- The app crashes again
- The app restarts, shows the UI and sending is approved
- The device is offline can't send the report
- The app goes background or exits
- The app starts again and shows the UI again and again and again, even though it is already approved.
Only the device coming back online fixed this issue so far.
This commit fixes this issue for all scenarios.
Added `allowAutomaticFetchingForNewFeedbackForManager:` which allows the developer to influence if the SDK should fetch for new messages on app startup and when the app is coming into foreground.
By default the SDK always checks in those cases if there are already messages existing.
Building e.g. only with crash reporting activated caused compiler warnings to appear even with the binary distribution when e.g. forward declaration checks are enabled.
This commit adds additional checks in all relevant header and code files to make sure the header files only consider the features that have been enabled
The code wronly assumed that when crashManager startManager is invoked, it will always be in the foreground, which causes false reports in some scenarios. The fix checks if the app is really active when this code is running.
- Change property name to be more explicit
- Reset proptery to nil, so we can are making sure the logic always works safely and is only triggered before the photo picker is invoked
* the statusBar shows up when the UIImagePickerController opens
* the status bar does not disappear again when the UIImagePickerController is dismissed
