Merge lp:~rockstar/ubuntuone-ios-music/upgrade-testflight into lp:ubuntuone-ios-music

[Paul Hummer]

Upgrade TestFlight

Upgrade the TestFlight lib to 1.0 - Seems there was some weirdness in how it sends crash reports in earlier versions (including the version we were using from back in August 2011).

[Zachery Bir (urbanape)]

Do it.

review: Approve

=== modified file 'TestFlight SDK/README.txt'
--- TestFlight SDK/README.txt	2011-10-18 19:18:05 +0000
+++ TestFlight SDK/README.txt	2012-08-29 20:24:18 +0000
@@ -1,16 +1,19 @@
-Thanks for downloading the TestFlight SDK! 
+Thanks for downloading the TestFlight SDK 1.0!
 
-This document is also availale on the web at https://www.testflightapp.com/sdk/doc
+This document is also available on the web at https://www.testflightapp.com/sdk/doc
 
 1. Why use the TestFlight SDK?
 2. Considerations
 3. How do I integrate the SDK into my project?
-4. Using the Checkpoint API
-5. Using the Feedback API
-6. Upload your build
-7. Questions API
-8. View your results
-9. Advanced Exception Handling
+4. Beta Testing and Release Differentiation
+5. Using the Checkpoint API
+6. Using the Feedback API
+7. Upload your build
+8. Questions API
+9. View your results
+10. Advanced Exception Handling
+11. Remote Logging
+12. iOS 3
 
 START
 
@@ -21,27 +24,30 @@
 
 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 find 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.
+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.
+
 2. 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.
+This SDK can be run from both the iPhone Simulator and Device and has been tested using Xcode 4.0.
 
 3. How do I integrate the SDK into my project?
 
 
-1. Add the files to your project: Project -> Add to Project -> TestFlightSDK
-
-    1. Copy items into destination folder (if needed): Checked
-    2. Reference Type: Default
-    3. Recursively create groups for added folders
-
-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. Add the files to your project: File -> Add Files to "<your project name>" 
+
+    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 and 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
@@ -50,72 +56,111 @@
     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. In your Application Delegate:
-
-    1. Import TestFlight -> #import "TestFlight.h"
-    NOTE: If you do not want to import TestFlight.h in every file you may add the above line into you precompiled header (<projectname>_Prefix.pch) file inside of the 
-
-            #ifdef __OBJC__ section. 
+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: If you do not want to import 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 then choose edit.
-    3. Launch TestFlight with your Team Token, if you do not currently use an unhandled exception handler you can skip to step 4
+        
+    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 unhandled exception handler. If you are not currently using an exception handler of your own then all you need ot 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.
-
-4. 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 Postprocessing
+    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 Postrocessing
     2. Strip Debug Symbols During Copy
     3. Strip Linked Product
 
-4. Use the Checkpoint API to create important checkpoints throughout your application.
-
-When a tester passes a level, or adds a new todo item, you can pass a checkpoint.  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.
-
-5. Using the Feedback API
-
-To launch unguided feedback call the openFeedbackView method. We recommend that you call this from a GUI element. 
+
+4. 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. Here is the recommended code for providing the device unique identifier.
+
+    #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.
+
+5. Use the Checkpoint API to create important checkpoints throughout your application.
+
+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.
+
+6. Using the 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 submitCustomFeedback: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.
 
-6. 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 here https://testflightapp.com/api/doc/ 
-
-7. Add Questions to Checkpoints
+7. 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/>
+
+8. Add Questions to Checkpoints
 
 In order to ask a question, you'll need to associate it with a checkpoint. Make sure your checkpoints are initialized by running your app and hitting them all yourself before you start adding questions.
 
 There are three question types available: Yes/No, Multiple Choice, and Long Answer.
 
-To create questions, visit your build's Questions page, and click on 'Add Question'. If you choose Multiple Choice, you'll need to enter a list of possible answers for your testers to choose from &mdash; otherwise, you'll only need to enter your question's, well, question. If your build has no questions, you can also choose to migrate questions from another build (because seriously &mdash; who wants to do all that typing again)?
+To create questions, visit your builds Questions page and click on 'Add Question'. If you choose Multiple Choice, you'll need to enter a list of possible answers for your testers to choose from &mdash; otherwise, you'll only need to enter your question's, well, question. If your build has no questions, you can also choose to migrate questions from another build (because seriously &mdash; who wants to do all that typing again)?
 
-After restarting your application on an approved device when you pass the checkpoint associated with your questions a Test Flight modal question form will appear on the screen asking the beta tester to answer your question.
+After restarting your application on an approved device, when you pass the checkpoint associated with your questions a TestFlight modal question form will appear on the screen asking the beta tester to answer your question.
 
 After you upload a new build to TestFlight you will need to associate questions once again. However if your checkpoints and questions have remained the same you can choose "copy questions from an older build" and choose which build to copy the questions from.
 
-8. View your results.
+9. View your results.
 
 As testers install your build and start to test it you will see their session data on the web on the build report page for the build you've uploaded.
 
-9. Advanced Exception Handling
+10. Advanced Exception Handling
 
-An unhandled exception means that your application is in an unknown state and there is not much that you can do but try and exit gracefully. Our SDK does its best to get the data we collect in this situation to you while it is crashing but it is designed in such a way that the important act of saving the data occurs in as safe way a way as possible before trying to send anything. If you do use unhandled exception or signal handlers install your handlers before calling takeOff our SDK will then call your handler while ours is running. For example:
+An uncaught exception means that your application is in an unknown state and there is not much that you can do but try and exit gracefully. Our SDK does its best to get the data we collect in this situation to you while it is crashing, but it is designed in such a way that the important act of saving the data occurs in as safe way a way as possible before trying to send anything. If you do use uncaught exception or signal handlers install your handlers before calling `takeOff`. Our SDK will then call your handler while ours is running. For example:
 
             /*
-             My Apps Custom unhandled exception catcher, we do special stuff here, and TestFlight takes care of the rest
+             My Apps Custom uncaught exception catcher, we do special stuff here, and TestFlight takes care of the rest
             **/
             void HandleExceptions(NSException *exception) {
                 NSLog(@"This is where we save the application data during a exception");
@@ -135,7 +180,7 @@
                 NSSetUncaughtExceptionHandler(&HandleExceptions);
                 // create the signal action structure 
                 struct sigaction newSignalAction;
-                // intialize the signal action structure
+                // initialize the signal action structure
                 memset(&newSignalAction, 0, sizeof(newSignalAction));
                 // set SignalHandler as the handler in the signal action structure
                 newSignalAction.sa_handler = &SignalHandler;
@@ -145,11 +190,54 @@
                 sigaction(SIGBUS, &newSignalAction, NULL);
                 // Call takeOff after install your own unhandled exception and signal handlers
                 [TestFlight takeOff:@"Insert your Team Token here"];
-                // continue with your application intialization
+                // continue with your application initialization
             }
 
 You do not need to add the above code if your application does not use exception handling already.
 
+11. Remote Logging
+
+To perform remote logging you can use the TFLog method which logs in a few different methods described below. In order to make the transition from NSLog to TFLog easy we have used the same method signature for TFLog as NSLog. You can easily switch over to TFLog by adding the following macro to your header
+
+    #define NSLog TFLog
+
+That will do a switch from NSLog to TFLog, if you want more information, such as file name and line number you can use a macro like
+
+    #define NSLog(__FORMAT__, ...) TFLog((@"%s [Line %d] " __FORMAT__), __PRETTY_FUNCTION__, __LINE__, ##__VA_ARGS__)
+
+Which will produce output that looks like
+
+    -[HTFCheckpointsController showYesNoQuestion:] [Line 45] Pressed YES/NO
+
+We have implemented three different loggers.
+
+    1. TestFlight logger
+    2. Apple System Log logger
+    3. STDERR logger
+
+Each of the loggers log asynchronously and all TFLog calls are non blocking. The TestFlight logger writes its data to a file which is then sent to our servers on Session End events. The Apple System Logger sends its messages to the Apple System Log and are viewable using the Organizer in Xcode when the device is attached to your computer. The ASL logger can be disabled by turning it off in your TestFlight options
+
+    [TestFlight setOptions:[NSDictionary dictionaryWithObject:[NSNumber numberWithBool:NO] forKey:@"logToConsole"]];
+
+The default option is YES.
+
+The STDERR logger sends log messages to STDERR so that you can see your log statements while debugging. The STDERR logger is only active when a debugger is attached to your application. If you do not wish to use the STDERR logger you can disable it by turning it off in your TestFlight options
+
+    [TestFlight setOptions:[NSDictionary dictionaryWithObject:[NSNumber numberWithBool:NO] forKey:@"logToSTDERR"]];
+
+The default option is YES.
+
+12. iOS3
+
+We now require that anyone who is writing an application that supports iOS3 add the System.framework as an optional link. In order to provide a better shutdown experience we send any large log files to our servers in the background. To add System.framework as an optional link:
+    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 libSystem.dylib in the list and add it
+    7. To the right of libSystem.dylib in the Link Binary With Libraries pane change "Required" to "Optional"
+
 END
 
 Please contact us if you have any questions.

=== modified file 'TestFlight SDK/TestFlight.h'
--- TestFlight SDK/TestFlight.h	2011-10-18 19:18:05 +0000
+++ TestFlight SDK/TestFlight.h	2012-08-29 20:24:18 +0000
@@ -2,34 +2,95 @@
 //  TestFlight.h
 //  libTestFlight
 //
-//  Created by Colin Humber on 8/25/10.
-//  Copyright 2010 23 Divide Apps. All rights reserved.
+//  Created by Jonathan Janzen on 06/11/11.
+//  Copyright 2011 TestFlight. All rights reserved.
 
 #import <Foundation/Foundation.h>
-
+#define TESTFLIGHT_SDK_VERSION @"1.0"
+#undef TFLog
+
+#if __cplusplus
+extern "C" { 
+#endif
+    void TFLog(NSString *format, ...);   
+#if __cplusplus
+}
+#endif
+
+/**
+ * TestFlight object
+ * All methods are class level
+ */
 @interface TestFlight : NSObject {
 
 }
 
 /**
- Add custom environment information
- If you want to track a user name from your application you can add it here
+ * Add custom environment information
+ * If you want to track custom information such as a user name from your application you can add it here
+ * 
+ * @param information A string containing the environment you are storing
+ * @param key The key to store the information with
  */
 + (void)addCustomEnvironmentInformation:(NSString *)information forKey:(NSString*)key;
 
 /**
- Starts a TestFlight session
+ * Starts a TestFlight session
+ *
+ * @param teamToken Will be your team token obtained from https://testflightapp.com/dashboard/team/edit/ 
  */
 + (void)takeOff:(NSString *)teamToken;
 
 /**
- Track when a user has passed a checkpoint after the flight has taken off. Eg. passed level 1, posted high score
+ * Sets custom options
+ *
+ * @param options NSDictionary containing the options you want to set available options are described below
+ *
+ *   Option                      Accepted Values                 Description
+ *   reinstallCrashHandlers      [ NSNumber numberWithBool:YES ] Reinstalls crash handlers, to be used if a third party 
+ *                                                               library installs crash handlers overtop of the TestFlight Crash Handlers
+ *   logToConsole                [ NSNumber numberWithBool:YES ] YES - default, sends log statements to Apple System Log and TestFlight log 
+ *                                                               NO  - sends log statements to TestFlight log only
+ *   logToSTDERR                 [ NSNumber numberWithBool:YES ] YES - default, sends log statements to STDERR when debugger is attached
+ *                                                               NO  - sends log statements to TestFlight log only
+ *   sendLogOnlyOnCrash          [ NSNumber numberWithBool:YES ] NO  - default, sends logs to TestFlight at the end of every session
+ *                                                               YES - sends logs statements to TestFlight only if there was a crash
+ */
++ (void)setOptions:(NSDictionary*)options;
+
+/**
+ * Track when a user has passed a checkpoint after the flight has taken off. Eg. passed level 1, posted high score
+ *
+ * @param checkpointName The name of the checkpoint, this should be a static string
  */
 + (void)passCheckpoint:(NSString *)checkpointName;
 
 /**
- Opens a feeback window that is not attached to a checkpoint
+ * Opens a feedback window that is not attached to a checkpoint
  */
 + (void)openFeedbackView;
 
+/**
+ * Submits custom feedback to the site. Sends the data in feedback to the site. This is to be used as the method to submit
+ * feedback from custom feedback forms.
+ *
+ * @param feedback Your users feedback, method does nothing if feedback is nil
+ */
++ (void)submitFeedback:(NSString*)feedback;
+
+/**
+ * Sets the Device Identifier. 
+ * The SDK no longer obtains the device unique identifier. This method should only be used during testing so that you can 
+ * identify a testers test data with them. If you do not provide the identifier you will still see all session data, with checkpoints 
+ * and logs, but the data will be anonymized.
+ * It is recommended that you only use this method during testing. We also recommended that you wrap this method with a pre-processor
+ * directive that is only active for non-app store builds. 
+ * #ifndef RELEASE 
+ * [TestFlight setDeviceIdentifier:[[UIDevice currentDevice] uniqueIdentifier]];
+ * #endif
+ *
+ * @param deviceIdentifier The current devices device identifier
+ */
++ (void)setDeviceIdentifier:(NSString*)deviceIdentifer;
+
 @end

=== modified file 'TestFlight SDK/libTestFlight.a'
Binary files TestFlight SDK/libTestFlight.a	2011-10-20 17:36:00 +0000 and TestFlight SDK/libTestFlight.a	2012-08-29 20:24:18 +0000 differ
=== modified file 'TestFlight SDK/release_notes.txt'
--- TestFlight SDK/release_notes.txt	2011-10-18 19:18:05 +0000
+++ TestFlight SDK/release_notes.txt	2012-08-29 20:24:18 +0000
@@ -1,8 +1,125 @@
+1.0 - March 29, 2012
+Resolved occurrences of exceptions with the message "No background task exists with identifier 0"
+
+1.0 BETA 1  - March 23, 2012
+Privacy Updates
+    UDID is no longer collected by the SDK. During testing please use [TestFlight setDeviceIdentifier:[[UIDevice currentDevice] uniqueIdentifier]]; to send the UDID so you can identify your testers. For release do not set +setDeviceIdentifier. See Beta Testing and Release Differentiation in the README or online at https://testflightapp.com/sdk/doc/1.0beta1/
+
+0.8.3 - February 14, 2012
+Rolled previous beta code into release builds
+No longer allow in application updates to occur in applications that were obtained from the app store.
+
+Tested compiled library with:
+Xcode 4.3
+Xcode 4.2
+Xcode 4.1
+Xcode 3.2.6
+
+0.8.3 BETA 5 - February 10, 2012
+Changed logging from asynchronous to synchronous.
+Resolved crash when looking for a log path failed.
+Added submitFeedback to the TestFlight class to allow for custom feedback forms.
+
+0.8.3 BETA 4 - January 20, 2012
+Resolved an issue that occured when an application was upgraded from 0.8.3 BETA 1 to 0.8.3 BETA 3+ with unsent data from 0.8.3 BETA 1
+
+0.8.3 BETA 3 - January 19, 2012
+On crash log files over 64k will not be sent until next launch.
+
+Known Issues:
+Logging massive amounts of data at the end of a session may prevent the application from launching in time on next launch
+
+0.8.3 BETA 2 - January 13, 2012
+libz.dylib is now required to be added to your "Link Binary with Libraries" build phase
+Log file compression, The compression is done on an as needed basis rather than before sending
+Changed all outgoing data from JSON to MessagePack
+Added option logToSTDERR to disable the STDERR logger
+
+0.8.3 BETA 1 - December 29, 2011
+In rare occurrences old session data that had not been sent to our server may have been discarded or attached to the wrong build. It is now no longer discarded
+Made sending of Session End events more robust
+Network queuing system does better bursting of unsent data
+Log files that are larger than 64K are now sent sometime after the next launch
+Log files that are larger than 16MB are no longer supported and will be replaced with a message indicating the log file was too large
+Fixed crashes while resuming from background
+
+0.8.2 - December 20, 2011
+Promoted 0.8.2 BETA 4 to stable
+
+Known Issues:
+Under some circumstances Session End events may not be sent until the next launch.
+With large log files Session End events may take a long time to show up.
+
+Tested compiled library with:
+Xcode 4.3
+Xcode 4.2
+Xcode 4.1
+Xcode 3.2.6
+
+0.8.2 BETA 4 - December 12, 2011
+Prevented "The string argument is NULL" from occuring during finishedHandshake in rare cases
+Resolved issue where data recorded while offline may not be sent
+
+0.8.2 BETA 3 - December 8, 2011
+Added auto-release pools to background setup and tear down 
+ 
+0.8.2 BETA 2 - December 5, 2011
+Fixed the "pointer being freed was not allocated" bug
+
+0.8.1 - November 18, 2011
+Implemented TFLog logging system, see README for more information
+Fixed an issue where Session End events may not be sent until next launch
+Fixed an issue where duplicate events could be sent
+Fixed an issue with Session End events not being sent from some iPod touch models
+
+Tested compiled library with:
+Xcode 4.2
+Xcode 4.1
+Xcode 3.2.6
+
+0.8 - November 8, 2011
+Added SIGTRAP as a signal type that we catch
+Removed all Objective-c from crash reporting
+Removed the use of non signal safe functions from signal handling
+Created a signal safe way to get symbols from a stack trace
+Changed the keyboardType for Long Answer Questions and Feedback to allow for international character input
+Changed TESTFLIGHT_SDK_VERSION string to be an NSString
+Changed cache folder from Library/Caches/TestFlight to Library/Caches/com.testflight.testflightsdk
+Fixed issue with saving data when device is offline
+Fixed compability issues with iOS 3
+Added calling into the rootViewController shouldAutorotateToInterfaceOrientation if a rootViewController is set
+Made the comments in TestFlight.h compatible with Appledoc
+
+Tested compiled library with:
+Xcode 4.2
+Xcode 4.1
+Xcode 3.2
+
+0.7.2 - September 29, 2011
+Changed TESTFLIGHT_SDK_VERSION string to be an NSString
+Fixed an issue where exiting an application while the SDK is active caused modal views to be dismissed
+0.7.1 - September 22, 2011
+Internal release
+Refactoring
+0.7 - September 21, 2011
+Moved TestFlight images and data to the Library/Caches folder
+Resolved an issue where sometimes the rootViewController could not be found and feedback, questions and upgrade views would not be displayed
+In application upgrade changed to allow skipping until the next version is installed and allows upgrades to be forced
+Fixed a memory leak when launching questions
+0.6 - September 2, 2011
+Renamed base64_encode to testflight_base64_encode to remove a conflict with other third party libraries
+Added ability to reinstall crash handlers when they are overwritten using the setOptions API
+Fixed an issue where crash reports might not get sent under certain circumstances
+Fixed a deadlock when the application is put in the background and then resumed before all information can be sent
+Fixed an issue when attempting to un-install all signal handlers during a signal
+Added support for landscape mode on the iPad to the Questions and Feedback views
+Crash reporting now works in versions of Xcode earlier than 4.2
+Fixed a memory leak during handshake
 0.5 - August 19, 2011
 Feedback that is not attached to a checkpoint [TestFlight openFeedbackView]
 Usability changes to question views
 Removed pause and resume sessions, replaced with sessions being stopped and started
-Added text autocorrection to the Long Answer question type
+Added text auto correction to the Long Answer question type
 Crash reports now send on crash instead of next launch
 0.4 - August 15, 2011
 In Application Feedback with Questions