iOS源码大全（24个）

##Introduction The TestFlight SDK allows you to track how beta testers are testing your application. Out of the box we track simple usage information, such as which tester is using your application, their device model/OS, how long they used the application, logs of their test session, and automatic recording of any crashes they encounter. To get the most out of the SDK we have provided the Checkpoint API. The Checkpoint API is used to help you track exactly how your testers are using your application. Curious about which users passed level 5 in your game, or posted their high score to Twitter, or found that obscure feature? With a single line of code you can finally gather all this information. Wondering how many times your app has crashed? Wondering who your power testers are? We've got you covered. See more information on the Checkpoint API in section 4. Alongside the Checkpoint API is the Questions interface. The Questions interface is managed on a per build basis on the TestFlight website. Find out more about the Questions Interface in section 6. For more detailed debugging we have a remote logging solution. Find out more about our logging system with TFLog in the Remote Logging section. ##Considerations Information gathered by the SDK is sent to the website in real time. When an application is put into the background (iOS 4.x) or terminated (iOS 3.x) we try to send the finalizing information for the session during the time allowed for finalizing the application. Should all of the data not get sent the remaining data will be sent the next time the application is launched. As such, to get the most out of the SDK we recommend your application support iOS 4.0 and higher. This SDK can be run from both the iPhone Simulator and Device and has been tested using Xcode 4.0. ##Integration 1. Add the files to your project: File -&gt; Add Files to " " 1. Find and select the folder that contains the SDK 2. Make sure that "Copy items into destination folder (if needed)" is checked 3. Set Folders to "Create groups for any added folders" 4. Select all targets that you want to add the SDK to 2. Verify that libTestFlight.a has been added to the Link Binary With Libraries Build Phase for the targets you want to use the SDK with 1. Select your Project in the Project Navigator 2. Select the target you want to enable the SDK for 3. Select the Build Phases tab 4. Open the Link Binary With Libraries Phase 5. If libTestFlight.a is not listed, drag and drop the library from your Project Navigator to the Link Binary With Libraries area 6. Repeat Steps 2 - 5 until all targets you want to use the SDK with have the SDK linked 3. Add libz to your Link Binary With Libraries Build Phase 1. Select your Project in the Project Navigator 2. Select the target you want to enable the SDK for 3. Select the Build Phases tab 4. Open the Link Binary With Libraries Phase 5. Click the + to add a new library 6. Find libz.dylib in the list and add it 7. Repeat Steps 2 - 6 until all targets you want to use the SDK with have libz.dylib 4. In your Application Delegate: 1. Import TestFlight: `#import "TestFlight.h"` ***NOTE:*** Rather than importing `TestFlight.h` in every file you may add the above line into you pre-compiled header (`<projectname>_Prefix.pch`) file inside of the #ifdef __OBJC__ section. This will give you access to the SDK across all files. 2. Get your Team Token which you can find at [http://testflightapp.com/dashboard/team/](http://testflightapp.com/dashboard/team/) select the team you are using from the team selection drop down list on the top of the page and then select Team Info. 3. Launch TestFlight with your Team Token -(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { // start of your application:didFinishLaunchingWithOptions // ... [TestFlight takeOff:@"Insert your Team Token here"]; // The rest of your application:didFinishLaunchingWithOptions method // ... } 4. To report crashes to you we install our own uncaught exception handler. If you are not currently using an exception handler of your own then all you need to do is go to the next step. If you currently use an Exception Handler, or you use another framework that does please go to the section on advanced exception handling. 5. To enable the best crash reporting possible we recommend setting the following project build settings in Xcode to NO for all targets that you want to have live crash reporting for. You can find build settings by opening the Project Navigator (default command+1 or command+shift+j) then clicking on the project you are configuring (usually the first selection in the list). From there you can choose to either change the global project settings or settings on an individual project basis. All settings below are in the Deployment Section. 1. Deployment Post Processing 2. Strip Debug Symbols During Copy 3. Strip Linked Product ##Beta Testing and Release Differentiation In order to provide more information about your testers while beta testing you will need to provide the device's unique identifier. This identifier is not something that the SDK will collect from the device and we do not recommend using this in production. To send the device identifier to us put the following code before your call to takeOff. #define TESTING 1 #ifdef TESTING [TestFlight setDeviceIdentifier:[[UIDevice currentDevice] uniqueIdentifier]]; #endif This will allow you to have the best possible information during testing, but disable getting and sending of the device unique identifier when you release your application. When it is time to release simply comment out #define TESTING 1. If you decide to not include the device's unique identifier during your testing phase TestFlight will still collect all of the information that you send but it may be anonymized. ##Checkpoint API When a tester does something you care about in your app you can pass a checkpoint. For example completing a level, adding a todo item, etc. The checkpoint progress is used to provide insight into how your testers are testing your apps. The passed checkpoints are also attached to crashes, which can help when creating steps to replicate. `[TestFlight passCheckpoint:@"CHECKPOINT_NAME"];` Use `passCheckpoint:` to track when a user performs certain tasks in your application. This can be useful for making sure testers are hitting all parts of your application, as well as tracking which testers are being thorough. ##Feedback API To launch unguided feedback call the openFeedbackView method. We recommend that you call this from a GUI element. -(IBAction)launchFeedback { [TestFlight openFeedbackView]; } If you want to create your own feedback form you can use the submitCustomFeedback method to submit the feedback that the user has entered. -(IBAction)submitFeedbackPressed:(id)sender { NSString *feedback = [self getUserFeedback]; [TestFlight submitFeedback:feedback]; } The above sample assumes that [self getUserFeedback] is implemented such that it obtains the users feedback from the GUI element you have created and that submitFeedbackPressed is the action for your submit button. Once users have submitted feedback from inside of the application you can view it in the feedback area of your build page. ##Upload your build After you have integrated the SDK into your application you need to upload your build to TestFlight. You can upload from your dashboard or or using the Upload API, full documentation at [https://testflightapp.com/api/doc/](https://testflightapp.com/api/doc/) ##Questions I