3. Let the AppDelegate implement the protocols `BITHockeyManagerDelegate`:
@interface AppDelegate(HockeyProtocols) < BITHockeyManagerDelegate > {}
@end
4. Search for the method `application:didFinishLaunchingWithOptions:`
5. Add the following lines:
[[BITHockeyManager sharedHockeyManager] configureWithBetaIdentifier:@"BETA_IDENTIFIER"
liveIdentifier:@"LIVE_IDENTIFIER"
delegate:self];
[[BITHockeyManager sharedHockeyManager] startManager];
6. Replace `BETA_IDENTIFIER` with the app identifier of your beta app. If you don't know what the app identifier is or how to find it, please read [this how-to](http://support.hockeyapp.net/kb/how-tos/how-to-find-the-app-identifier).
7. Replace `LIVE_IDENTIFIER` with the app identifier of your release app. We suggest to setup different apps on HockeyApp for your test and production builds. You usually will have way more test versions, but your production version usually has way more crash reports. This helps to keep data separated, getting a better overview and less trouble setting the right app versions downloadable for your beta users.
8. If you want to use the beta distribution feature on iOS 7 or later with In-App Updates, restrict versions to specific users or want to know who is actually testing your app, you need to follow the instructions on our guide [Identify and authenticate users of Ad-Hoc or Enterprise builds](HowTo-Authenticating-Users-on-iOS)
*Note:* The SDK is optimized to defer everything possible to a later time while making sure e.g. crashes on startup can also be caught and each module executes other code with a delay some seconds. This ensures that applicationDidFinishLaunching will process as fast as possible and the SDK will not block the startup sequence resulting in a possible kill by the watchdog process.
## Additional Options
### Mac Desktop Uploader
The Mac Desktop Uploader can provide easy uploading of your app versions to HockeyApp. Check out the [installation tutorial](Guide-Installation-Mac-App).
### Xcode Documentation
This documentation provides integrated help in Xcode for all public APIs and a set of additional tutorials and HowTos.
1. Copy `de.bitstadium.HockeySDK-iOS-3.5.0.docset` into ~`/Library/Developer/Shared/Documentation/DocSet`
The documentation is also available via the following URL: [http://hockeyapp.net/help/sdk/ios/3.5.0/](http://hockeyapp.net/help/sdk/ios/3.5.0/)
### Set up with xcconfig
Instead of manually adding the missing frameworks, you can also use our bundled xcconfig file.
1. Select your project in the `Project Navigator` (⌘+1).
2. Select your project.
3. Select the tab `Info`.
4. Expand `Configurations`.
5. Select `HockeySDK.xcconfig` for all your configurations (if you don't already use a `.xcconfig` file)
**Note:** You can also add the required frameworks manually to your targets `Build Phases` and continue with step `7.` instead.
6. If you are already using a `.xcconfig` file, simply add the following line to it
`#include "../Vendor/HockeySDK/Support/HockeySDK.xcconfig"`
(Adjust the path depending where the `Project.xcconfig` file is located related to the Xcode project package)
**Important note:** Check if you overwrite any of the build settings and add a missing `$(inherited)` entry on the projects build settings level, so the `HockeySDK.xcconfig` settings will be passed through successfully.
7. If you are getting build warnings, then the `.xcconfig` setting wasn't included successfully or its settings in `Other Linker Flags` get ignored because `$(inherited)` is missing on project or target level. Either add `$(inherited)` or link the following frameworks manually in `Link Binary With Libraries` under `Build Phases`:
- `CoreText`
- `CoreGraphics`
- `Foundation`
- `QuartzCore`
- `Security`
- `SystemConfiguration`
- `UIKit`