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/
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