StoreKit

• FIXED: In-App purchase will not work for developers testing their apps with the iTunes Sandbox.

UI Automation

• NEW: There is a known issue when using the performTaskOnHost API in a UI Automation script. If the task being performed with the API outputs excessively (say, thousands of lines of text) to standard out or standard error, the task may deadlock until the timeout is reached, at which point it will throw a javascript exception.
• The lock() and unlock() functions of UIATarget have been replaced with the lockForDuration() function.
• Starting in iOS 5 beta 2, you can now trigger the execution of an UI Automation script on an iOS device from the host terminal by using the instruments tool. The command is:
  • instruments -w -t

UIKit

• Starting in iOS 5 beta 3, the exclusiveTouch property of UIControl has returned to its original default value of NO.
• Returning nil from the tableView:viewForHeaderInSection: method (or its footer equivalent) is no longer sufficient to hide a header. You must override tableView:heightForHeaderInSection: and return0.0 to hide a header.
• In the iOS 5 beta, the UITableView class has two methods to move one cell from one row to another with defined parameters. These APIs are:
  • moveSection:toSection:
  • moveRowAtIndexPath:toIndexPath:
• Using the UIWebView class in Interface Builder, setting transparent background color is possible in iOS 5. Developers compiling against the new SDK can check their XIB for the UIWebView transparent setting.
• In the iOS 5 beta, the UINavigationBar, UIToolbar, and UITabBar implementations have changed so that the drawRect: method is not called on instances of these classes unless it is implemented in a subclass. Apps that have re-implemented drawRect: in a category on any of these classes will find that the drawRect: method isn't called. UIKit does link-checking to keep the method from being called in apps linked before iOS 5 but does not support this design on iOS 5 or later. Apps can either:
  • Use the customization API for bars that in iOS 5 and later, which is the preferred way.
  • Subclass UINavigationBar (or the other bar classes) and override drawRect: in the subclass.
• The indexPathForRow:inSection:, section, and row methods of NSIndexPath now use NSInteger instead of NSUInteger, so that these types match with methods defined on UITableView.
• Touch events are not getting forwarded to the view in the cameraOverlayView property of UIImagePickerController.
• We have changed the behavior of scrollToRowAtIndexPath:atScrollPosition:animated: such that UITableViewScrollPositionTop and UITableViewScrollPositionBottom now adjust for the top and bottom portions of the contentInset property.
• NEW: In releases prior to iOS 5.0, the UIPopoverController class would unconditionally set the autoresizing masks of view controllers which were the content view controller of the popover controller. It would also unconditionally set the autoresizing masks of the views of view controllers pushed on to a UINavigationController object which was the content view controller of the popover controller.In iOS 5.0, the UIPopoverController class will no longer do this for applications linked on iOS 5.0 or later. Developers should ensure that the autoresizing masks of views are set properly to allow for arbitrary resizing within any container, not just popovers. A mask of (UIViewAutoresizingFlexibleWidth | UIViewAutoresizingFlexibleHeight) would not be unreasonable.
• The completion handler for saveToURL:forSaveOperation:completionHandler: is now being called outside of the coordinated write block, where it used to be called inside.
• NEW: The autosaveWithCompletionHandler: method is now called only for period-based saves and it is safe to return without saving. Documents must save, though, if thesaveToURL:forSaveOperation:completionHandler: method is invoked.