iOS SDK Release Notes for iOS 6 beta 3
iOS SDK 6.0 provides support for developing iOS apps and includes the complete set of Xcode tools, compilers, and frameworks for creating apps for iOS and OS X. These tools include the Xcode IDE and the Instruments analysis tool among many others.
With this software you can develop apps that run on iPhone, iPad, or iPod touch running iOS 6. You can also test your apps using the included iOS Simulator, which supports iOS 6. iOS SDK 6.0 requires a Macintosh computer running OS X 10.7.4 or higher (Lion).
This version of iOS is intended only for installation on devices registered with Apple's developer program. Attempting to install this version of iOS in an unauthorized manner could put your device in an unusable state.
For more information and additional support resources, visit:
Please report any bugs not mentioned in the “Notes and Known Issues” section using the Apple Bug Reporter on the Apple Developer website (http://developer.apple.com/bugreporter/). Additionally, you may discuss these issues and iOS SDK 6 in the Apple Developer Forums: http://devforums.apple.com. You can get more information about iCloud for Developers at: http://developer.apple.com/icloud
Notes and Known Issues
The following issues relate to using iOS SDK 6.0 to develop code.
When an app is in a fresh privacy state and tries to present a
ABNewPersonViewController, the user cannot dismiss that view controller properly even if they allow access to contacts. The user must force quit the app and relaunch.
Requesting access to contacts:
Users are able to grant or deny access to contact data on a per-app basis. To request access to contact data, call the
ABAddressBookRequestAccessWithCompletionfunction after calling the
ABAddressBookRequestAccessWithCompletionfunction does not block the app while the user is being asked to grant or deny access. Until access has been granted, the
ABAddressBookRefobject will not contain any contacts and any attempt to modify contacts fails with a
kABOperationNotPermittedByUserErrorerror. The user is prompted only the first time access is requested; any subsequent calls to
ABAddressBookCreateWithOptionswill use the existing permissions. The completion handler is called on an arbitrary queue. If the
ABAddressBookRefobject is used throughout the app, then all usage must be dispatched to the same queue to use
ABAddressBookRefin a thread-safe manner.
Checking access authorization status:
An app can use the authorization status API to check if it can access contacts, calendars, reminders or photo library. This API is independent from the the request access API and will not prompt the user to grant or deny access. With this API an app can adjust the display of its UI elements that would access the data class. For example, if access to contacts is authorized or not determined then a UI button to pick a contact can be displayed.
For Address Book, call the
ABAddressBookGetAuthorizationStatusfunction. For Event Kit, call the
authorizationStatusForEntityType:class method of
EKEventStore. For Assets Library, call the
authorizationStatusclass method of
ALAssetsLibrary. The meaning of the status values that are returned is as follows:
Authorization Status Not Determined - The user has not yet made a choice regarding whether this app can access the data class.
Authorization Status Restricted - This app is not authorized to access the data class. The user cannot change this app’s status, possibly due to active restrictions such as parental controls being in place.
Authorization Status Denied - The user explicitly denied access to the data class for this app.
Authorization Status Authorized - This app is authorized to access the data class.
In some cases, the screen may show the wrong resolution. Restart your Apple TV to return it to the correct resolution.
FIXED: Netflix videos may not resume where you left off.
FIXED: The History list in the YouTube app gets cleared when you exit and reenter the app.
Apple TV may be slow to respond while a download is in progress in the background.
Apple TV may restart while using the Remote app.
Apple TV may restart when changing the system language.
Photo Stream does not load when logging in a second time. Restart Apple TV to resolve.
Music does not play during photo slideshows.
Pick remote speakers in Settings > AirPlay.
Set an onscreen code for AirPlay in Settings > AirPlay.
Save multiple iTunes Store accounts in Settings > iTunes Store.
Press and hold the Select button to rearrange icons on the main menu.
Hide the main menu icons in Settings > General > Parental Controls.
NSNetServiceclass and CFNetService APIs do not include P2P interfaces by default. To browse, register, or resolve services over P2P interfaces, an app needs to use the Bonjour
DNSService*()APIs noted below.
Setting the interfaceIndex parameter to
kDNSServiceInterfaceIndexAnyin the following API's will not include P2P interfaces by default. To include P2P interfaces, you must now set the
kDNSServiceFlagsIncludeP2Pflag when using
kDNSServiceInterfaceIndexAnyor set the interfaceIndex to
kDNSServiceInterfaceIndexP2P. The affected APIs are:
There is a known issue with dictionaries when attempting to define a word in any language other than English or Japanese. When the reference library is presented, the user is presented with the option to download a dictionary - that download may not begin. The user can tap outside the popover on an iPad or tap the "Done" button on the iPhone or iPod touch in order to dismiss the download request.
Requesting access to calendars or reminders:
Users are able to grant or deny access to event and reminder data on a per-app basis. To request access to event and/or reminder data, call the
EKEventStore. This will not block the app while the user is being asked to grant or deny access. Until access has been granted for an entity type, the event store will not contain any calendars for that entity type, and any attempt to save data will fail.
The user will only be prompted the first time access is requested; any subsequent instantiations of
EKEventStorewill use the existing permissions. The completion handler is called on an arbitrary queue.
When creating a new Game Center account in-app on the iPad, the popover for selecting the month for your date of birth shows up with no content to select.
GKLocalPlayerhas been removed. Authentication will automatically commence when the completion handler is set.
When creating an iCloud account, you can use any email based Apple ID, or you can use your existing iCloud account. If you had a MobileMe account that you have not yet moved to iCloud, you must move it first by visiting http://me.com. Moving to iCloud is only available for a limited time. Logging into a MobileMe account is not supported in iOS 6.
icloud.comemail addresses are now available for iCloud mail users. Users signing up for new Apple IDs, or enabling Mail on their iCloud account for the first time, will automatically receive an
@icloud.comemail address instead of a
me.comemail address. iCloud users with
@me.comaddresses that have been used with iOS 6 beta 3 will receive an
@icloud.comemail address that matches their
Provisioning profiles must be enabled for iCloud in the iOS Provisioning Portal. To enable a provisioning profile for iCloud, navigate to the App ID section of the iOS Provisioning Portal and configure your App ID for iCloud. After enabling the App ID for iCloud, regenerate your provisioning profiles to enable them for iCloud.
NSMetadataQueryis not supported.
In iOS 6, files that are protected via Data Protection cannot be used with iCloud Storage APIs.
File names are case-insensitive in OS X but case-sensitive in iOS. This can lead to problems when sharing files between the two platforms using iCloud. You should take steps on iOS to avoid creating files whose names differ only by case.
The behavior of coordinated read operations on iCloud Documents has changed.
On previous iOS releases, when your app performed a coordinated read operation on a file or package, and the iCloud daemon noticed that there was a newer version of the item available, the coordinated read operation blocked until the newer version of the item was downloaded and written to the disk.
Starting in iOS 6 beta 3, when you start a coordinated read operation on a file or package for which you already have a local version, the coordinated read will be granted as soon as possible, and the new version, if any, will download in the background. This call will block for downloading reasons only if you do not have any version of the file available locally.
Additionally, when the file is conflicted, the iCloud daemon will not wait until it has all the conflict losers of the file available to make the file available to your app. It will make the different versions of the conflicted file available as soon as it can. Your app can use the existing file coordination and the
UIDocumentcallbacks to be notified when the conflict losers have been downloaded and are available.
iMessage & FaceTime
FIXED: The Answer and Decline buttons are missing when receiving calls in landscape orientations.
iTunes 10.6.3 is required for iOS SDK 6.0.
FIXED: When restoring from an iTunes backup, the device intermittently shows up as a new device after rebooting. If that happens, set up the device as a “new device” when prompted to restore for the 2nd time. All data should have been restored correctly but sync settings including App arrangement in iTunes are lost.
In iOS 6 and later, Map Kit is built on a new infrastructure hosted by Apple. Earlier iOS releases will continue to use Google’s service.
API compatibility will be maintained (see known issues below).
Maps are now supported in the Simulator.
Map data will continue to evolve—only a limited amount of high resolution satellite imagery is currently available.
FIXED: If Maps is not running in the background, a "Maps cannot connect to the internet" error is displayed when it is launched from a 3rd party app.
FIXED: If Maps has not yet been launched, the current location does not show up when it is launched from a 3rd-party app.
Routing apps that do not specify a coverage file during development will always be displayed in the Maps routing search results.
Testing and debugging of coverage files for routing apps is only supported during development through the Xcode "Run" workflow. (You can specify the coverage file for a given Run scheme using the Options pane of the Run section of the scheme editor.) Apps that are archived and distributed (outside of the App Store) onto devices will not have access to the app's coverage files.
Maps does not zoom into the current location when launched from a 3rd party app.
Only simple http downloads will work with Newsstand.
FIXED: An airplane icon appears between the origin and destination for all transit types.
The "Description" field is now a required field for a Pass. All passes created without it will fail to validate and will not ingest.
FIXED: The Passbook database has been reset. You’ll need to add your passes again.
Passbook in the simulator no longer requires
sslwhen using a
webServiceURLwhen ingesting a pass.
Unable to show boarding passes on lock screen.
FIXED: There are issues when adding and editing reminders in the Reminders app on iPhone devices:
The Done button is missing when adding a new reminder.
The app crashes when you tap the Edit button to edit a reminder.
In iOS 5, signing a certificate with an MD5 signature is not supported. Please ensure that certificates use signature algorithms based on SHA1 or SHA2.
In iOS 6, there are improved privacy controls for Calendars, Reminders, Contacts, and Photos.
Users will see access dialogs when an app tries to access any of those data types. The user can switch access on and off in Settings > Privacy.
Developers can set a "purpose" string for each class of isolated data. iOS displays this string to users to help them understand why their data is being requested. These strings can be added using Xcode's Project editor, in the Info tab. The relevant key names begin with the string "Privacy -".
There are changes to the Event Kit and Address Book frameworks to help developers with this feature.
The app delete confirmation alert panel takes a while to show up in iOS Simulator.
FIXED: Tapping the buy button in the view of an
SKStoreProductViewControllerobject in iOS Simulator causes the app to crash.
No privacy alerts are displayed in iOS Simulator for apps that access Photos, Contacts, Calendar and Reminders.
Downloading in-app purchase hosted content in iOS Simulator is not supported.
When attempting to play an MP3 sound in the Simulator, you will hear a popping sound instead.
FIXED: Using the iOS 5.1 SDK with the iPad (Retina) profile will result in a SpringBoard crash. The iOS 5.1 SDK works with all other profiles and the iPad (Retina) SDK works with the iOS 6.0 SDK.
FIXED: Ads of type
ADAdTypeMediumRectangledo not appear in iPad Simulator.
Shared Photo Stream
User must go to Settings > iCloud to ensure that they receive Shared Photo Stream Notifications.
In order to share a Photo Stream with iOS 6 beta, you must invite someone using their iCloud email address or they will not receive the invitation.
Upgrading from iOS 6 beta 1 to beta 2 will cause your device to re-download all of your Shared Photo Streams.
The Shared Photo Stream feature is set to OFF when updating from iOS 6 beta 1 to a later release. The default setting should be ON.
Turning off Shared Photo Streams may leave camera in an unresponsive state, force quitting camera will resolve this issue.
Weibo shows up in the Settings app only if a Chinese keyboard is enabled.
ACAccountStoreis now deprecated. To access user accounts, please use the
In the options parameter of this new method, pass
nilto access Twitter and Weibo accounts. To access Facebook accounts, pass a dictionary with the following keys (which are documented in
You should no longer add this dictionary to your app's
Info.plistfile, as was required in beta 1.
FIXED: After restoring a device in iTunes or performing an "Erase All Contents and Settings", the current wallpaper may not appear until the device is rebooted once.
It is now possible to set status bar tint parameters in your app’s
Info.plistfile. You might do this to ensure that the status bar color matches the navigation bar color of your app during startup. To set the status bar tint, add the
UIStatusBarTintParameterskey to your Info.plist file. The value of this key is a dictionary with the appropriate values describing the navigation bar your app has at startup time. Inside the dictionary should be the
UINavigationBarkey, whose value is also a dictionary. That dictionary contains the initial navigation bar's style (with the
Stylekey) and whether it's translucent (with the
Translucentkey). If your navigation bar uses them, you can also specify its tint color (with the
TintColorkey), or the name of its custom background image (with the
In iOS 5.1, the
UISplitViewControllerclass adopts the sliding presentation style when presenting the left view (previously only seen in Mail). This style is used when presentation is initiated either by the existing bar button item provided by the delegate methods or by a swipe gesture within the right view. No additional API adoption is required to obtain this behavior, and all existing API, including that of the
UIPopoverControllerinstance provided by the delegate, will continue to work as before. If the gesture would be insupportable in your app, setting the
presentsWithGestureproperty of your split view controller to
NOdisables the gesture. However, disabling the gesture is discouraged because its use preserves a consistent user experience across all apps.
FIXED: In iOS 6, changes have been introduced so that you no longer need to set a delegate and implement a method for Single-Finger and Single-Tap gesture recognizers, in an effort to make them work well with the
In iOS 6 and later, the
UIWebViewclass paints its contents asynchronously.
FIXED: Developers trying out Auto Layout with
UIScrollViewobjects might notice jitters in the scroll indicators on devices with Retina displays.
Autorotation is changing in iOS 6. In iOS 6, the
UIViewControlleris deprecated. In its place, you should use the
More responsibility is moving to the app and the app delegate. Now, iOS containers (such as
UINavigationController) do not consult their children to determine whether they should autorotate. By default, an app and a view controller’s supported interface orientations are set to
UIInterfaceOrientationMaskAllfor the iPad idiom and
UIInterfaceOrientationMaskAllButUpsideDownfor the iPhone idiom.
A view controller’s supported interface orientations can change over time. Even an app’s supported interface orientations can change over time. The system asks both the topmost full screen view controller (typically the root view controller) for its supported interface orientations whenever the device rotates or whenever a view controller is presented with the full screen modal presentation style. Moreover the supported orientations are retrieved only if this view controller returns
shouldAutorotatemethod. The system intersects the view controller’s supported orientations with the app's supported orientations (as determined by the
Info.plistfile or the app delegate's
application:supportedInterfaceOrientationsForWindow:method) to determine whether to rotate.
The system determines if an orientation is supported by intersecting the value returned by the app’s
supportedInterfaceOrientationsForWindow:method with the value returned by the
supportedInterfaceOrientationsmethod of the topmost fullscreen controller.
setStatusBarOrientation:animated:method is not deprecated outright. However it now works only if the
supportedInterfaceOrientationsmethod of the topmost full screen view controller returns
0. This puts the responsibility of ensuring that the status bar orientation is consistent into the hands of the caller.
For compatibility, view controllers that still implement the
shouldAutorotateToInterfaceOrientation:method do not get the new autorotation behaviors. (In other words, they do not fall back to using the app, app delegate, or
Info.plistfile to determine the supported orientations.) Instead, the
shouldAutorotateToInterfaceOrientation:method used to synthesize the information that would be returned by the
FIXED: In certain situations, the Auto Layout system might not engage automatically for a view. To workaround this problem, override the
requiresConstraintBasedLayoutclass method in your view and return
YESfrom your implementation.
didRotateFromInterfaceOrientation:methods are no longer called on any view controller that makes a full screen presentation over itself—for example, by calling
You should make sure that your apps are not using these methods to manage the layout of any subviews. Instead, they should use the view controller’s
viewWillLayoutSubviewsmethod and adjust the layout using the view’s bounds rectangle.
In iOS 6, the
UIViewControllerare now deprecated. If you were using these methods to release data, use the
didReceiveMemoryWarningmethod instead. You can also use this method to release references to the view controller’s view if it is not being used. You would need to test that the view is not in a window before doing this.
FIXED: Calling any of the attributed string drawing methods without specifying a value for the
NSFontAttributeNameattribute is likely to throw an exception. The workaround is to set a value for the
NSFontAttributeNamekey before drawing or sizing an
Setting values for the
shadowColorproperties of a
attributedTextproperty contains a valid attributed string, is unsupported. Use the
NSShadowAttributeNameattribute of the attributed string to set the shadow instead.
Due to compatibility concerns, the
NSBaselineOffsetAttributeNameattribute is no longer supported in iOS 6.
NSTextAlignmentNaturalvalue is unsupported and will throw an exception when used with the
UILabelor supplied as the alignment parameter to the
UIViewhas been deprecated in this beta release. To achieve the same effect, use the
UIImageand display the image with a
UIImageeffectively resizes images by tiling. As a performance optimization, it uses stretching rather than tiling when the user would not be able to tell the difference, like when a single column or row is being stretched. But in certain circumstances, one might want to actually stretch some region of an image. In iOS 6, the
resizableImageWithCapInsets:resizingMode:method allows the caller to specify a tiling or stretching resizing mode.
UICollectionViewLayoutclass has changed:
The class now supports the customization of the animations created during rotation. The names of methods for customizing insert and delete animations have also changed so that the same hooks can be used for rotations as well as for insertions and deletions.
The class has changed some method names. Specifically, decoration views are no longer referred to by "reuse identifier" but rather by "element kind." Apps that are using decoration views will need to modify their code and rebuild to accommodate this.
FIXED: In iOS 6, a bug was fixed where
UIWebView.isLoadingwas set to
NObefore the main frame finished loading. Now,
UIWebView.isLoadingis set to NO when the main frame is done loading.
The bottom edge of a
UILabelview is now different from its baseline.
Previously, auto layout was interpreting the bottom of a
UILabelto be the same as its baseline. While convenient in many cases, it caused problems if you wanted to place the top edge of one label against the bottom edge of another. In such a scenario, the bottom label would overlap the top one, and descenders from the top label could crash into ascenders from the bottom label. Now, auto layout interprets
UILayoutAttributeBottomas the bottom of the text box (presuming the label is not bigger than its intrinsic content size), and
UILayoutAttributeBaselineas the baseline of the text. If you have already created code for laying out labels according to the bottom or center point, your text will move around a little and you will need to adjust your constraints.
Apps with table views in their nib or storyboard files, and that were built using previous versions of iOS 6 beta, will require a clean build with beta 3 and newer.
Here are some notes regarding auto layout support for
In general, auto layout considers the top, left, bottom, and right edges of a view to be the visible edges. That is, if you pin a view to the left edge of its superview, you're really pinning it to the minimum x-value of the superview’s bounds. Changing the bounds origin of the superview does not change the position of the view.
UIScrollViewclass scrolls its content by changing the origin of its bounds. To make this work with auto layout, the meaning of the top, left, bottom, and right edges within a scroll view now mean the edges of its content view.
The constraints on the subviews of the scroll view must result in a size to fill, which is then interpreted as the content size of the scroll view. (This should not be confused with the
intrinsicContentSizemethod used for auto layout.) To size the scroll view's
framewith auto layout, constraints must either be explicit regarding the width and height of the scroll view or the edges of the scroll view must be tied to views outside of its subtree.
Note that you can make a subview of the scroll view appear to float (not scroll) over the other scrolling content by creating constraints between the view and a view outside the scroll view's subtree, such as the scroll view's superview.
Here are some examples of how to configure the scroll view:
Position and size your scroll view with constraints external to the scroll view—that is, the
translatesAutoresizingMaskIntoConstraintsproperty is set to
Create a plain
UIViewcontent view for your scroll view that will be the size that you want your content to have. Make it a subview of the scroll view but let it continue to translate the autoresizing mask into constraints:
UIView *contentView = [[UIView alloc]
// DON'T change contentView's translatesAutoresizingMaskIntoConstraints,
// which defaults to YES;
Set the content size of the scroll view to match the size of the content view:
Create the views you want to put inside the content view and configure their constraints so as to position them within the content view.
Alternatively, you can create a view subtree to go in the scroll view, set up your constraints, and call the
systemLayoutSizeFittingSize:method (with the
UILayoutFittingCompressedSizeoption) to find the size you want to use for your content view's size and the
contentSizeproperty of the scroll view.
Pure auto layout approach:
In this case
translatesAutoresizingMaskIntoConstraintsmust be set to
NOon all views involved.
Position and size your scroll view with constraints external to the scroll view.
Use constraints to lay out the subviews within the scroll view, being sure that the constraints tie to all four edges of the scroll view and do not rely on the scroll view to get their size.
A simple example would be a large image view, which has an intrinsic content size derived from the size of the image. In the
viewDidLoadmethod of your view controller, you would include code like the following:
UIScrollView *scrollView = [[UIScrollView alloc] init];
UIImageView *imageView = [[UIImageView alloc] init];
[imageView setImage:[UIImage imageNamed:"MyReallyBigImage"]];
scrollView.translatesAutoresizingMaskIntoConstraints = NO;
imageView.translatesAutoresizingMaskIntoConstraints = NO;
NSDictionary *viewsDictionary = NSDictionaryOfVariableBindings(scrollView,imageView);
[self.view addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"H:|[scrollView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];
[self.view addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"V:|[scrollView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];
[scrollView addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"H:|[imageView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];
[scrollView addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"V:|[imageView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];
This would give you a scroll view that resized as the view controller's view resized (such as on device rotation), and the image view would be a scrolling subview. You don't have to set the content size of the scroll view.
Safari & WebKit
WebKit on iOS now supports the
Note that because the specification is still at the Working Draft state, these methods have the
webkitprefix, so they are
The default app cache quota has been increased from 5MB to 25MB.
The JPEG subsampling threshold was increased from 2 MP (megapixels) to 5 MP on all supported hardware except iPhone 3GS and iPod touch (4th gen).
Support has been added for
<input type="file">tags in web forms. Users can upload existing photos and videos from their photo library or take a picture or video using the camera. Previously this form control was always disabled.
With Safari 6.0 on OS X, developers can now use the Web Inspector (web development tool) with attached iOS devices and iOS Simulator. Developers can use the Web Inspector to debug Safari and the
UIWebViewclass in their own apps built and run from Xcode. This replaces the Debug Console banner in Safari.
In iOS 6 and later, web data (SQL Web Storage and LocalStorage) from a
UIWebViewobject can be stored in a directory that will be backed up. To enable backing up this data, set the
YESin your app’s user defaults. This should be done only if your app relies on web content data that cannot be reloaded. If your
UIWebViewobject opens links to arbitrary web content, this key should be set to
NO. Toggling the value of this key will not preserve existing web view data.
In iOS 6 and later, Safari no longer registers for the common
feed:RSS/ATOM scheme. Apps that can view those types of feeds are encouraged to register for that URL scheme.
WebKit no longer always creates hardware-accelerated layers for elements with the
-webkit-transform: preserve-3doption. Authors should stop using this option as a way to get hardware acceleration.
Experimental CSS3 Flexbox support will be disabled. Please switch from using
As of iOS 6, embedded YouTube URLs in the form of
https://www.youtube.com/watch?v=oHg5SJYRHA0will no longer work. These URLs are for viewing the video on the YouTube site, not for embedding in web pages. Instead, the format that should be used is described in https://developers.google.com/youtube/player_parameters.
In iOS 6, the
keyboardDisplayRequiresUserActionproperty was added to the
UIWebViewclass. The property defaults to
YES, which means that calling
focus()on a form element will not bring up the keyboard. By changing the property to
focus()on a form element will focus the element and automatically bring up the keyboard.
As of iOS 6, calling
focus()on a form element in a web app will focus the element.
들리는 소문에 의하면 8월에 모든 베타가 종료되고 정식 공개전 마무리 한다는 소문이 있지만
이왕 아이폰에 얹은거.. 다른 프로젝트 중이지만 일단 쭉 베타버전은 얹어 본다..
> beta3 공개를 알리는 메일내용~
Pre-release software, including information about pre-release software, is Apple Confidential Information and is subject to the terms of your iOS Developer Program License Agreement. Unauthorized distribution or disclosure of Apple Confidential Information is prohibited.
You are receiving this email because you are an iOS Developer Program member who is opted-in to receive marketing or technical information. If you would prefer not to receive future communications from Apple Developer you may unsubscribe.
> beta3 릴리즈 노트
iOS SDK Release Notes for iOS 5.0 beta 3
Important: This is a preliminary document for an API or technology in development. Although this document has been reviewed for technical accuracy, it is not final. Apple is supplying this information to help you plan for the adoption of the technologies and programming interfaces described herein. This information is subject to change, and software implemented according to this document should be tested with final operating system software and final documentation. Newer versions of this document may be provided with future seeds of the API or technology.
Notes and Known Issues
iOS SDK 5.0 provides support for developing iOS applications and includes the complete set of Xcode tools, compilers, and frameworks for creating applications for iOS and Mac OS X. These tools include the Xcode IDE and the Instruments analysis tool among many others.
With this software you can develop applications that run on iPhone, iPad, or iPod touch running iOS 5.0. You can also test your applications using the included iOS Simulator, which supports iOS 5.0. There are two Xcode iOS SDK 5.0 images, one for installing on a Macintosh computer running Mac OS X 10.6.7 (Snow Leopard) or later, the other for installing on a Macintosh computer running Mac OS X 10.7 (Lion).
This version of iOS is intended only for installation on devices registered with Apple's developer program. Attempting to install this version of iOS in an unauthorized manner could put your device in an unusable state.
For more information and additional support resources, visit:
Please report any bugs not mentioned in the “Notes and Known Issues” section using the Apple Bug Reporter on the Apple Developer website (http://developer.apple.com/bugreporter/). Additionally, you may discuss these issues and iOS SDK 5.0 in the Apple Developer Forums: http://devforums.apple.com. You can also access more information about iCloud Beta for Developers at: http://developer.apple.com/icloud
Notes and Known Issues
The following issues relate to using the 5.0 SDK to develop code.
When creating an iCloud account you can use any Apple ID provided it is a full email address and not a MobileMe account. If you have a MobileMe account, you can copy data from that account to an iCloud account to use during testing. You can find more information on iCloud at: http://developer.apple.com/icloud
When setting up an iCloud or MobileMe account using the setup assistant and leaving Find My iPhone on, it might actually turn Find my iPhone off after the setup. Please verify in Settings/Mail, Contacts, Calendar/YourAccount that Find my iPhone is toggled On after leaving the setup assistant.
There is a problem finding a device using Find My iPhone on the MobileMe website (www.me.com) when switching from iCloud back to MobileMe. To workaround this issue:
On the device go to Settings->Mail, Contacts, Calendar-><your_account>@me.com and Toggle Find My iPhone off and back on. Now the device should show up on MobileMe website.
It is recommended that you disable Bookmarks on multiple accounts. If they are enabled, the results might be undefined.
NEW: In this beta the option of “Choosing a security question” is not working during an iCloud account setup.
Starting in iOS 5, video content in applications and websites are AirPlay-enabled by default.
iOS 5 supports AirPlay of video via AV Foundation.
FIXED: The Apple TV screen saver may degrade mirroring performance over AirPlay. The screen saver can be disabled in Apple TV settings.
Apple TV Software beta enables users to mirror the contents of an iPad 2 to an Apple TV (2nd generation) using AirPlay. This beta software also enables Photo Stream on Apple TV so users can access photos stored in iCloud. Apple TV Software beta is being provided to test the latest AirPlay functionality with your iOS 5 apps and web sites. If you wish to install Apple TV Software beta on your device, you must first register your device UDID in the iOS Developer Program Portal.
Using voice chat in iOS 5 requires setting the kAudioSessionMode_VoiceChat mode on the Audio Session, or setting the AVAudioSessionModeVoiceChat mode on the AVAudioSession object.
FIXED: After creating a recurring event locally on the device, the device stops syncing after hitting an error on merge. Removing and re-adding the account acts as a workaround for this.
All MobileMe calendars were duplicated after turning calendar syncing off and back on.
If you launch or manually refresh Calendars on an iPad, your calendars might disappear and you will have to tap "Show All Calendars" to display them again.
NEW: Restoring from a Seed 1 backup or earlier will cause MobileMe/iCloud calendars not to sync. Subscribed calendars will show up in Calendars but none of your event calendars will appear in MobileCal. To workaround the problem please remove and re-add the account.
Match data for turn based matches is currently limited to 4 KB of data.
If you have an existing Game Center account which has not yet gone through the first-time Game Center flow in iOS 5, you will encounter a crash when signing into a game's login alert directly. The workaround for this is to launch Game Center to complete the first-time flow.
iBooks 1.2.2 may fail to display some text or images in books. Please update to iBooks 1.3 in the App Store.
As this is beta software, it is recommended that you do not use the iCloud services to store any critical data or information. If you enable iCloud Backup, automatic backup with iTunes when syncing will be disabled. We suggest you also manually back up your device with iTunes.
In the iOS 5 beta, support for data protection in iCloud Backup is unavailable. Apps that have protected files will not have any of their data or metadata backed up as a result.
After restoring, you may not be able to back up again because the device still thinks it's restoring. To workaround this issue try syncing apps or media that are missing form iTunes or try deleting your iCloud account and adding it back.
If you delete your backup, the feature will be disabled but settings may still indicate that it is enabled and you will have to toggle the BackUp to Cloud switch in Settings.
For compatibility reasons, this version of the iOS 5 beta requires that all files be backed up again, instead of only those files that have changed since your last backup. This may cause a warning that your account is over quota. In case the warning occurs, you can delete your oldest backup to free up space and then initiate a backup.
During the iOS 5 beta period, any documents stored on the servers might be purged periodically before GM. Therefore, it is highly recommended that you do not store any critical documents or information on the servers.
If your application is using the NSMetadataQuery class, you must set a predicate, even though the predicate itself is ignored.
The Foundation framework doesn't include the team ID when looking for an app's mobile documents container. The Team ID must be included at the beginning of the identifier string passed to the URLForUbiquityContainerIdentifier: method.
In this beta, the setSortDescriptors: method of NSMetadataQuery is not supported.
In this beta, if you want to use iCloud, you have to manually specify various container identifiers (your application’s Display set) within an Entitlements file for both of your Mac OS X and iOS projects.
There are issues using the Cloud Storage document API in conjunction with protected data which can lead to data corruption.
In this beta, document-based applications cannot always detect when files change, move, or are deleted out from underneath them.
NEW: In this beta, file presenters (objects that adopt the NSFilePresenter protocol) do not receive some of the messages that they're supposed to receive, especially:
You can workaround this by implementing the relinquishPresentedItemToWriter: method and checking to see if the writer actually wrote when your file presenter reacquires. You can also use FSEvents to observe file system changes
In this beta, messages about changes to files in a directory are not getting delivered to objects that adopt the NSFilePresenter protocol.
While reporting a bug related to the iCloud storage interfaces, please include the logs collected during your debugging session. To generate these logs, you must install a special debug profile on your device.
The debug profile can be obtained from http://connect.apple.com. This profile enables the generation of debug logs that are needed to diagnose any problems using iCloud storage. The instructions to collect the logs are:
Install the profile. (The easiest way to do this is to mail it to yourself and open the attachment on their device.)
Reproduce the bug.
Sync with iTunes to pull the logs off your device.
Attach the logs to your bug report. You can find the logs in ~/Library/Logs/CrashReporter/MobileDevice/DeviceName/DiagnosticLogs.
These logs can grow large very quickly, so you should remove the profile after you have reproduced the problem and pulled the logs for the bug report.
NEW: iMessage beta 3 will be unable to communicate with iMessage users on beta 1. It works between beta 3 and beta 2.
NEW: Modal alerts don’t appear for iMessages.
The version of iTunes that comes with beta 3 cannot sync devices that have the beta 2 software installed. To avoid this problem, do the following:
Sync any devices that have beta 2 installed to the version of iTunes that came with beta 2.
Upgrade iTunes to the version that comes with beta 3.
Connect the device and install the beta 3 software. (Understand that you might see a failure to sync error when you first connect the device.)
After installing the beta 3 software, restore from your the backup you made in step 1.
Videos purchased from the iTunes Store do not play on a 2nd generation AppleTV over AirPlay with iTunes 10.5.
Sending an MMS of large videos does not work.
If you apply red-eye adjustments in iOS, and import your image into the iPhoto seed build, the red-eye adjustments will not appear on that image in iPhoto. As a result, subsequent syncing of your image back to the iOS device from iPhoto will not show the red-eye adjustments.
FIXED: The Reminders application does not send notifications for reminders that are based upon the entry (and/or exit) of a location if there is no date associated with the reminder.
The “Back Up Now” button is enabled without the backup data class being enabled for the account.
FIXED: If you bring up the keyboard of the terms in Settings->General->Software Update, you cannot dismiss it. You have to force quit Settings to get out.
NEW: In this beta FaceTime icon is missing in Settings on the iPhones.
NEW: Location services are not functional in iOS 4.3 simulator running on Mac OS 10.7 with Xcode 4.2.
Push and local notifications for apps appear in the new Notification Center in iOS 5. Notification Center displays notifications that are considered "unread". In order to accommodate push and local notifications that have no "unread" status, developers can use their application badge count to trigger a clearing of notifications from Notification Center. When an application clears its badge count (by setting it to zero), iOS 5 will clear its notifications from Notification Center.
NEW: When tweeting your location from Safari and exiting before the location can be established, the location arrow will stay in the status bar. The arrow can be removed by killing Safari from the task switcher.
NEW: In iOS 5 beta 3, the first execution of a script after a reboot or erase install will likely fail. Subsequent attempts should succeed until the device is rebooted again.
The play and record buttons in the Automation instrument script editor may not work properly after targeting an application that was launched by a trace session and has ended. They may also not work if you target an application that was suspended. If you run into this problem and it persists, you may need to close and reopen the trace document to get back into a functional state.
When capturing actions into a script using the Automation instrument, interfaces with web views or table cells that contain a high number of off screen elements may take an extremely long time before returning with an expression.
The lock() and unlock() functions of UIATarget have been replaced with the lockForDuration(<seconds>) function.
Instruments overwrites the loaded automation script, even if another program is editing it.
Starting 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 <device id> -t <template> <application>
NEW: 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 return 0.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:
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.
There is a known issue with presenting a UIVideoEditorControllerobject where it doesn't show the selected video, which appears blank instead. In certain cases it may also crash.
Touch events are not getting forwarded to the view in the cameraOverlayView property of UIImagePickerController.
The imagePickerController:didFinishPickingMediaWithInfo: method of UIImagePickerController is not returning a URL to the video when recording is complete.
NEW: When creating a new appointment in calendar app on a device using 24 hr clock, you cannot select an hour value greater than 12. The date-time picker value sets current weekday to be the same as previous day (e.g: a An appointment on Tuesday will be set as Monday).
FIXED: 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 iOS 5 beta 2, a new inherited CSS property, -webkit-overflow-scrolling: value, is available. The value touch allows the web developer to opt in to native-style scrolling in an overflow:scroll element. The default value for this property is auto.
The WebKit framework has picked up a newer WebKit engine, which closely matches Safari 5.1. Some areas to be aware of with the new WebKit framework on iOS:
There is a new HTML5-compliant parser.
Text layout width may change slightly because word-rounding behavior now has floating-point-based precision.
There is improved validation of the <input type=number> form field, which includes removing leading zeros and number formatting.
Touch events are now supported on input fields.
window.onerror is now supported.
There is a new user agent that does not have locale information in the User Agent string.
In iOS 5 beta 2, wireless syncing is available for the Mac. It requires iTunes 10.5 beta 2 and OS X 10.6.8 or Lion. You will see an option to enable wireless syncing when you connect your device to iTunes with the USB cable. It is recommended you perform your initial sync with a cable after restoring your device.
Wireless syncing is triggered automatically when the device is connected to power and on the same network as the paired computer. Or, you can manually trigger a sync from iTunes or from Settings -> General -> iTunes Sync (same network as paired computer required). Be sure your device is plugged into a power source when performing wireless syncs.
If you find issues with apps, media and/or photos synced to your device, you can reset then resync. From Settings -> General -> Reset, choose Erase all Content and Settings. Then reconnect to iTunes and sync again.
FIXED: In this beta, iTunes may incorrectly report Photos as "Other" in the capacity bar. Photo syncing otherwise works as expected.
NEW:In some cases, your device may fail to sync contacts, calendars and account settings, or back up to iTunes. If this happens, reboot your device and re-sync.
NEW:In some cases, syncing photos may result in only thumbnails on your device. If this happens, unsync Photos then re-sync again.
In this beta, device restores using XCode are disabled. Please use iTunes only to back up and restore your device.
In some cases, Xcode 4.2 Organizer does not display a device that is in restore mode. As a workaround you can use iTunes to restore.
FIXED: On some desktop machines, Xcode's memory usage inflates incredibly fast while restoring a device or copying an IPSW. As a workaround use iTunes to restore.
FIXED: In this beta, crash logs (either unsymbolicated or symbolicated) do not appear in Xcode Organizer. To make them appear in the Xcode Organizer, you will have to rename the device.
In iOS 5 beta 2, the iOS Simulator is not compatible with previous releases of the iCloud Developer Seed for OS X. It is highly recommended that you update to the latest iCloud Developer Seed to ensure compatibility.
iOS 5.0 SDK supports both iOS 4.3 and iOS 5.0 simulators.