- Use one common static lib target
- create embeddedFramework as binary distribution including docset in one zip
- Add HockeySDK.xcconfig for easier build setting setup
- Move everything into a single directory, too many problems making binary and subproject work without requing recursive header search paths
- Documentation update pending
- Update feedback list reloading actions depending on loading status
- Reload feedback list from network if last request is older than 30 seconds when appearing
- Queue submitting message if there is another network request already in progress
Also has the problem, that we would need to copy the modal view code in there, since it can be a subclass from BITBaseViewController right now, since that is a subclass of UITableViewController to get the iOS6 pull to refresh feature
- Mark messages as archived that got deleted on the server
- Send message even if the thread got deleted on the server, so create a new thread
- Support Pull-To-Refresh in iOS6
- Update feedback and send pending message when the app gets into the foreground again
- Always update user data via delegates before sending a new message, since those could have changed in the app
- First implementation on feedback, not finished yet!
- Move all components into their own subdirectory
- Restructure common delegates into BITHockeyManagerDelegate
- Restructure common component methods into new superclass (not finished yet)
* 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.
