Monday, August 26, 2013

Find My iPhone bug Fixed without Dev Account

If you haven’t updated to the new version of Find my iPhone currently in the App Store, don’t—unless you’re a developer.
Version 2.0.3 of the app, which Apple released Thursday, purports to include only “bug fixes and stability improvements.” But when you update the app for locating your iOS devices, and log back in, you’ll get greeted with an error indicating that the app is limited to registered iOS developers running the iOS 7 beta. Whoops!
The updated version of the Find My iPhone app sports an icon more in line with the design of iOS 7 than iOS 6. It seems as if the version released in the App Store simply got pushed too early.
Apple declined to comment to Macworld, but did point to the now-updated version of the app.

iOS 7 beta 7 or Gold Master may launch next week : Few problems with update server

There has been a lot of speculation around iOS 7 beta 7 seeing a release date at some point this week, which is more about developers hoping rather than based on previous patterns. It seems that these developers are split on whether iOS 7 beta 7 or Gold Master will launch next, although our in-house developer has just notified us of a few problems with the update server within the last hour.

The screenshot you see below is from an iPhone 5 running iOS 7 beta 6 and this message has appeared only moments ago when checking to see if iOS 7 beta 7 is live. It is worth noting that this update might never arrive and we could be heading for Gold Master next.
Our in-house developer lives in the UK and said, “After checking to see if iOS 7 beta 7 is live or any other update I got this message while checking OTA. It basically states that an error occurred while checking for a software update, so you are unable to check for an update”. They continued, “I logged into the developer portal just fine and also tried to get an update on an iPhone 4S running iOS 7 beta 6, but the same problem and error message appeared”.

This might be some short downtime with the built-in software updater, or it could be that Apple is about to launch iOS 7 beta 7 with a release time around 10am PT as with past updates. We will have to wait and see, although we will contact our developer later today to see if the message is still there.
Would you like to see iOS 7 beta 7 release today, or would you rather go directly to Gold Master?
ios-7-beta-7-checking-receives-error

Friday, August 16, 2013

What's New in iOS 7 beta 6 ? Full Update

As you may know as up to this point Apple suddently released their Sixth beta of ios 7 late today for developers.  The iOS 7 beta 5 did not bring a whole lot of new features or improvements but you can check out what’s new in ios 7 beta 6. The main purpose of this post is not to judge or say anything bad about the ios 7 but to discuss about the next beta release. We expected that it will be iOS 7 beta 7.
According to well-known ios developer/hacker iH8Sn0w he expected that iOS 7 Beta 6 will be expired on Sunday, October 6, 2013 @ 12AM (GMT) on Twitter.. After the expiration something else got to be out right?
ih8sn0w ios 7 iOS 7 Beta 6 maybe out sometimes on October, 2013
That mean iOS 7 beta 7 will be out in sometimes on October or it could be the golden version of / final version of iOS 7 beta. About the final version, I do not think that it will be next because Apple still got a lot to fix and more features to roll out so most likely to be the beta 7 then. So that is what we expected but don’t blame us if it does not come out because this was just our expectation toward the next beta of ios 7. Stay tune for more updates. By the way, if the firmware does come out like we expected you will get the freedownload links right away.

Small Minor Fixes in iOS 7 Beta 6 Revealed Earlier [Hands-On video]

The iOS 7 beta 6 release arrived late today, a week a head of the rumored release date with a small fix for an iCloud issue but not much else to note.
The 13.5MB iOS 7 beta 6 download comes with a specific fix in mind, designed to address purchases downloading and playing unexpectedly on devices running iOS 7 beta 5 and earlier.
This is the second iOS 7 beta download to arrive outside of the previous Monday schedule, and the first to do so late in the day, so it’s possible Apple saw fixing this issue as a priority it didn’t want to hold over for a bigger update.
Earlier today a rumor suggested the iOS 7 beta 6 release would come next week, ahead of a Gold Master or final iOS 7 beta on September 5th to Apple partners and September 10th to developers, the same day of the rumored iPhone 5S launch date.
The iOS 7 beta 6 release arrives late Thursday night with small fixes.
The iOS 7 beta 6 release arrives late Thursday night with small fixes.
In addition to the iOS 7 beta 6 download files Apple offers in the Developer Center, there is an additional file users will need to download and install to reset their music library.
This ResetMusicAndVideosLibraries configuration profile resets the media library and will force users to all music and videos stored within the Music and Video apps. This will not remove videos from the camera roll, only content purchased in iTunes.
Registered iOS 7 developers can download the iOS 7 beta 6 ResetMusicAndVideosLibraries configuration profile by clicking opening the Developer Center in Safari on a device running iOS 7 beta 6. This will prompt users to install a verified profile, as shown in the image below. After installing it, Go to Settings -> Music -> Reset Media Library and then restart the device to complete the process.
The iOS 7 beta 6 download requires users to also download a configuration profile to complete the fix.
The iOS 7 beta 6 download requires users to also download a configuration profile to complete the fix.
Users running the iOS 7 beta already can download the iOS 7 beta 6 update through an over the air update, simplifying the update process. Apple also offers a collection of iOS 7 beta 6 download links in the Developer Center.
There are other iOS 7 beta 6 release changes in this update, including the removal of cellular fallback, which was in an earlier iOS 7 beta. This technology would automatically switch to a cellular connection if a WiFi Network was bad due to a cable modem or router issue.
A variety of other changes present in the iOS 7 beta 6 release notes share the details developers need to know to make iOS 7 compatible apps, but are likely of little interest to the general users that are simply beta testing IOS 7 ahead of the release.

Apple could issue an iOS 7 beta 7 release before an iOS 7 GM and ahead of the fall IOS 7 release to the public. Previous versions of iOS betas have gone up to beta 8, where 8 was the final beta. It is possible the iOS 7 release is set for September 18th for the general public.

iOS 7 beta 6 iPSW Mega Download Clarified without UDID or developer account

iOS 7 beta 6 download links [For non-developers]
iPad 4 Wi-Fi
iPad 4 Wi-Fi + GSM
iPad 4 Wi-Fi + CDMA
iPad Mini Wi-Fi
iPad Mini Wi-Fi + GSM
iPad Mini Wi-Fi + CDMA
iPad 3 Wi-Fi
iPad 3 Wi-Fi + GSM
iPad 3 Wi-Fi + CDMA
iPad 2 Wi-Fi
iPad 2 Wi-Fi + GSM
iPad 2 Wi-Fi + CDMA
[Note: Other download links to be updated soon.]  
Apple released sixth beta version of iOS 7.
Steps to install iOS 7 beta 6 without UDID or developer account
Step-1: Ensure that the iPhone/iPod/iPad is running on the latest version of firmware; iPhone users should download iOS 6.1.4 and iOS 6.1.3 for others
 Step-2: Download iOS 7 beta 6 IPSW
Step-3: Connect the iDevice to the computer using USB cable
Step-4: Launch iTunes on the computer
Step-5: Press SHIFT on the keyboard (OPTION for Mac) and click Updatesimultaneously on iTunes
Step-6: Choose the correct IPSW- iOS 6.1.3 or iOS 6.1.4
Step-7:  Let iTunes restore the device to the choosen firmware and set it up as a new device-not from the back up
Step-8: On the Home Screen, find Check for Updates
Step-9: Do not click, just highlight it and hold SHIFT or OPTION and click onUpdate again
Step-10: Select the iOS 7 beta 6 IPSW and iTunes will update the iDevice to the new firmware
Note: Non-developers may get an Activation Error message. There was a security flaw in iTunes, which means activation was being skipped. To fix the error, users can either downgrade to iOS 6.1.3 (or 6.1.4 for iPhone 5) or register with the Apple Developer Programme. 
Provided all aforementioned instructions are followed strictly, your iPhone/iPad/iPod Touch should now be running on the iOS 7 beta 6. 

Apple iOS 7 Beta 6 Early Release to Developers, Fixed iTunes Update Clarified

Although expected next week, Apple has just sent out iOS 7 beta 6 for developers. The update is available over-the-air immediately, with the system files—for the iPhone, iPad, iPad mini and iPod touch—likely to follow online at Apple's iOS developer website at any time now. The update fixes an "issue with iTunes in the Cloud, where some purchases may download or play unexpected items." 
Apple has just released the sixth beta version of iOS 7 to developers for testing purposes. The update is available as an over-the-air update to existing beta testers and it can also be downloaded via Apple's Developer Center.


It was rumored earlier today that Beta 6 might be released next week, roughly two weeks after the release of Beta 5; however, the odd timing of this release -- Apple traditionally releases new iOS betas to developers on Monday mornings -- along with its small size, only 13.5MB on an iPhone 5, suggests that it could be some kind of urgent bug fix.


Iosbeta6


The new beta arrives as build 11A4449d, and comes a little more than week after the previous beta 5, which had a build number of 11A4449a.



iOS 7 is scheduled for release in the fall of this year, with updates to Apple’s iPhone and iPad lineups expected around the same time. If past history is any indication, iOS 7 should be made available to the public just a few days before the launch of the next-generation iPhone.



Update: Apple notes on the iOS Developer Center that the release fixes an "issue with iTunes in the Cloud, where some purchases may download or play unexpected items."


iosdevcenter
This software may be the last beta prior to the GM (gold master) version of iOS 7, due in advance of Apple's upcoming iPhone event on September 10, 2013. 
And just like that, iOS 7 beta 5 is no longer the freshest version of Apple's upcoming mobile OS. Today, the Cupertino firm unleashed beta 6 to the world, which is available as an OTA update to current beta testers. It's safe to assume that this release contains a bevy of bug fixes in the buildup to the final release, but we'll surely circle back if any juicy tidbits come to light. Naturally, if you have access to the latest beta, feel free to drop your impressions in the comments below.

Leaked and Tweaked iOS 7 Beta 6 Changelog Full update

As usual, within hours of the release of iOS 7 Beta 6, developers have leaked the changelog accompanying the software, a mile-long document that includes notes and detailed descriptions about the remaining bugs.

With one or two more betas to go before the software goes final, Apple continues to address issues in iOS 7, the latest such effort being evidenced by the release of Beta 6.

The new beta may not have been scheduled, as it addresses a rather critical bug involving iTunes in the Cloud. Developers receiving the beta have been given specific instructions regarding the installation of the software.

But iOS 7 Beta 6 also includes various other tweaks, all of which are documented in the now-leaked seed notes. For registered developers who don’t require leaks, the full iOS 7 Beta 6 release notes can be accessed on the iOS Dev Center.


With less than a month left until Apple finally takes the wraps off of its next-generation iPhone 5S and possibly the “iPhone 5C” as well — not that there’s much left to unwrap — the company has now issued iOS 7 beta 6, which will likely be its final iOS 7 beta. Apple released iOS 7 beta 6 a short while ago as an over the air (OTA) update and now the new files are available for compatible iPhone, iPad, iPad mini and iPod touch models on the iOS developer portal. The iOS 7 beta 6 change log was also just released and BGR has been sent a copy of the full document, which can be read below in its entirety.

Notes and Known Issues

The following issues relate to using iOS SDK 7.0 to develop code.

Address Book

Notes

  • The classes in the AddressBookUI framework now explicitly disallow subclassing. For apps linked against the iOS 7 SDK, attempting to initialize a subclass of one of these classes returns nil. For apps linked against older SDKs, the only behavior change is a warning logged to the console.
  • As of Seed 4, privacy support for the AddressBookUI framework is reenabled for apps linked against the iOS 7 SDK. Apps linked against older SDKs are not changed. If your app uses any of the Address Book view controllers, you should verify that it still behaves as expected.

AirDrop

Notes

  • AirDrop in iOS 7 Seed 2 or later is not compatible with AirDrop in iOS 7 Seed 1.
  • Contacts Only support requires that:
    • You are logged in to iCloud.
    • The sender and receiver have each other’s Apple ID email addresses in Contacts on their devices.

AV Foundation

Notes

AVCaptureSession now uses your app’s AVAudioSession by default.

Core Animation

Notes

When the UIViewGroupOpacity key is not present, the default value is now YES. The default was previously NO.
This means that subviews of a transparent view will first be composited onto that transparent view, then the precomposited subtree will be drawn as a whole onto the background. A NO setting results in less expensive, but also less accurate, compositing: each view in the transparent subtree is composited onto what’s underneath it, according to the parent’s opacity, in the normal painter’s algorithm order.

Exchange

Notes

In Seed 4 and later, the Exchange DeviceIdentifier has been changed back to the behavior of iOS 6 where it uses the serial number.

Fonts

Notes

New font line heights were introduced in Seed 4. If you had manually aligned your font in earlier seeds, it may move slightly up vertically in later seeds.

Foundation

Notes

  • An NSMetadataQuery with ubiquitous scope can now use kMDItemContentTypeTree in predicates. For example:
    • NSPredicate *p = [NSComparisonPredicate
                     predicateWithLeftExpression:[NSExpression expressionForKeyPath:@"kMDItemContentTypeTree"]
                                 rightExpression:[NSExpression expressionForConstantValue:@"public.rtf"]
                                        modifier: NSAnyPredicateModifier
                                            type:NSLikePredicateOperatorType
                                         options:0];
  • When called on results returned by queries with ubiquitous scopes, -[NSMetadataItem valueForAttribute:NSMetadataItemDisplayNameKey] now produces the same value as -[NSURL getResourceValue: forKey: NSURLLocalizedNameKey], matching nonubiquitous queries.

iCloud

Notes

  • If you use iCloud Keychain with recovery, you may see a dialog indicating recovery has been disabled due to a server change. This is intentional. To reenable functionality, follow the instructions in the notification. If you see multiple alerts or observe issues with reenabling recovery, please file a bug report.
  • iCloud Keychain in iOS 7 Seed 3 or later is not backward compatible with iOS 7 Seed 2 or OS X Mavericks Seed 2.If you had iCloud Keychain and/or Keychain Restore enabled from iOS 7 Seed 2, both features are disabled upon updating to iOS 7 Seed 3 or later.After updating to iOS 7 Seed 3 or later, go to Settings > iCloud > Keychain and reenable iCloud Keychain on your devices.See OS X v10.9 Release Notes for more details.
  • Activation Lock, a new feature of Find My iPhone, is turned on automatically when Find My iPhone is enabled on any device running iOS 7. Activation Lock requires users to enter their Apple ID and password to turn off Find My iPhone, sign out of iCloud, erase the device, or reactivate the device after an erase. It’s important to do one of the following before transferring a device to a new user:
    • Sign out of iCloud.
    • Turn off Activation Lock in Settings > iCloud > Find My iPhone.

Known Issues

Password fields are not displayed in alert views for apps in landscape (for example, Game Center authentication or In-App Purchase). Text entry still works, though you can’t see what you are typing.

MapKit

Notes

If the calls to renderInContext on the layer backing an MKMapView are made off the main thread, they should be eliminated or moved to the main thread. Failure to do so can cause an app crash. Instead of usingrenderInContext, use the new MKMapSnapshotter APIs.

Media

Notes

iOS now remembers the last used media app across reboot and app crashes. Media apps that can receive remote control events should be prepared to be launched in the background and potentially receive a remote control event to begin playback. Additionally, it’s important that media apps monitor and handle the media server reset event, since the media app may receive a remote request to resume playback after a reset. Notifications to monitor these media server events are available in AVAudioSession and proper handling is described in General recommendations for handling kAudioSessionProperty_ServerDied.

Multipeer Connectivity

Notes

The MCSession APIs function as they were presented at WWDC. Major changes and enhancements include:
  • The following new method on MCSession has been implemented:
    • - (NSOutputStream *)startStreamWithName:(NSString *)streamName toPeer:(MCPeerID *)peerID error:(NSError **)error
    This delegate method has been implemented:
    • - (void)session:(MCSession *)session didReceiveStream:(NSInputStream *)stream withName:(NSString *)streamName fromPeer:(MCPeerID *)peerID
  • The following new method on MCSession has been implemented:
    • - (NSProgress *)sendResourceAtURL:(NSURL *)resourceURL withName:(NSString *)resourceName toPeer:(MCPeerID *)peerID withCompletionHandler:(void(^)(NSError *error))completionHandler
    The delegate method to start receiving a resource from remote peer has been implemented as:
    • - (void)session:(MCSession *)session didStartReceivingResourceWithName:(NSString *)resourceName fromPeer:(MCPeerID *)peerID withProgress:(NSProgress *)progress
    The delegate method to finish receiving a resource from remote peer and save the content in a temporary location is implemented as:
    • - (void)session:(MCSession *)session didFinishReceivingResourceWithName:(NSString *)resourceName fromPeer:(MCPeerID *)peerID atURL:(NSURL *)localURL withError:(NSError *)error

  • MCAdvertiserAssistant is a convenience class for implementing an Advertiser, which handles invitations and connections to an MCSession.
  • MCSession has a new initWithPeer: method.
  • sendResource has added “with” to the completionHandler.
  • The timeout has been removed from connectPeer:withNearbyConnectionData.
For more information on these APIs, watch the video for WWDC 2013 Session 708, “Nearby Networking with Multipeer Connectivity.”

Multitasking

Notes

  • AVAudioSession can no longer become active by apps in the background that wake due to Background Fetch, Background Transfers, and Remote Notification events.
  • The policy for the task completion API has changed back to match the iOS 6 behavior, but the time limit for task completion has decreased from 10 minutes in iOS 6.

Networking

Notes

  • The cellular fallback technology present in previous seeds has been removed as of Seed 5.
  • Two low-level networking APIs that used to return a MAC address now return the fixed value 02:00:00:00:00:00. The APIs in question are sysctl (NET_RT_IFLIST) and ioctl (SIOCGIFCONF). Developers using the value of the MAC address should migrate to identifiers such as -[UIDevice identifierForVendor]. This change affects all apps running on iOS 7.

Objective-C Runtime

Notes

Due to changes in how the isa field is implemented, *self may change during enumeration (for example, if the container is retained).
Workaround: When implementing countByEnumeratingWithState, do not set state->mutationsPtr = self.

Passbook

Notes

  • As of iOS 7 Seed 4, Passbook has added support for the major and minor fields to better match the rest of the iBeacon ecosystem. The new major and minor keys are independently variable optional alongsideproximityUUID (required) in each dictionary in the beacons array.
  • In previous versions of the iOS SDK, Passbook did not validate the back fields on passes completely. The validation rules have not changed, but validation is now including back fields. Please check the console log for additional logs.
  • As of iOS 7 Seed 3, PKPassLibraryDidCancelAddPasses is a new status code in the PKPassLibraryAddPassesStatus enum. It signifies that the user tapped Cancel in an add-passes alert.

Photos

Notes

Upon upgrading from an earlier seed, photo thumbnails in the Photos app will not appear for a short while.

Security

Notes

  • -[UIDevice uniqueIdentifier] is no longer accepted in submissions to the App Store. In iOS 7, apps that are already on the store or on users’ devices that call this removed API will no longer be returned the UDID. Instead, -[UIDevice uniqueIdentifier] will return a 40-character string starting with FFFFFFFF, followed by the hex value of -[UIDevice identifierForVendor]. It is important to consider how this will affect existing apps. Consider submitting updates that no longer access the UDID.
  • iOS now requests user consent for apps to use audio input on all iOS 7 devices. For devices sold in China, iOS will also request user consent for apps to use the camera hardware. The operating system will present the consent alert when you set the category of the instantiated AVAudioSession. The AVAudioSession categories that will present the alert are AVAudioSessionCategoryRecord andAVAudioSessionCategoryPlayAndRecord.If the user doesn’t allow access, the audio session data will be all zeros (silence). For devices where camera access is requested and denied by the user, the video capture session is a black screen.
  • The API gethostuuid() has been removed and will not be accepted for submission to the store, regardless of the targeted OS. For existing apps running on iOS 7, the function will return a uuid_t representation of the vendor identifier (-[UIDevice identifierForVendor]).

Siri

Notes

This seed includes development versions of new male and female Siri voices for U.S. English, French, and German.

Social

Notes

  • Through iOS 6, when using TWTweetComposeViewController and SLComposeViewController (the latter only for Twitter and Weibo, but not Facebook), if the caller supplies a completionHandler, the suppliedcompletionHandler is responsible for dismissing the view controller. As of iOS 7, if the app links against the iOS 7 SDK, the view controller will dismiss itself even if the caller supplies a completionHandler. To avoid this, the caller’s completionHandler should not dismiss the view controller.
  • When using the iOS 6.1 SDK on OS X v10.8 Mountain Lion, if you use the iOS 5.0 or iOS 5.1 Legacy SDK in iOS Simulator, you will not be able to use Twitter features: attempting to sign in to Twitter via the Settings pane will fail, and Twitter.framework will not work correctly. If you need to test Twitter features, you will need to choose either an iOS 6.1 or iOS 6.0 Simulator run destination, or you can test with iOS 5.x on a device.

Springboard

Notes

  • Active touches are no longer canceled when the user takes a screenshot.
  • Dynamic wallpaper is not available on iPhone 4.

Sprite Kit

Notes

+[AVPlayer playerWithPlayerItem:] returns an AVPlayer object, but the current item will return nil if the player was created on another thread.

Stores

Known Issues

App downloads can get stuck in the “Waiting” state.
Workaround: Reboot your device once or twice to resolve the issue and allow subsequent downloads to continue.

UIKit

Notes

  • Before Seed 4, the snapshot API (snapshotView and resizableSnapshotViewFromRect:withCapInsets:) would defer taking the snapshot if the view had never been committed or had been added to the view hierarchy in the current transaction. This behavior has changed.Snapshots now always represent the current, committed state of the view. Attempting to snapshot a view that has never been committed logs a message and now returns nil.
  • Snapshotting methods have been updated and now take an argument: afterUpdates. When set to YES, this instructs the snapshot to wait until all pending changes to the hierarchy have been committed. To maintain the pre-Seed 4 behavior, pass NO and the snapshot will capture what is currently on screen. See UIView.h for more details.
  • When there isn’t enough room in the navigation bar layout for the full text of the back button title, the navigation bar will substitute a generic short back title (in English, “Back”). If even that string is too long, the bar will show the back indicator chevron with no title.
  • +[UIPasteboard pasteboardWithName:create:] and +[UIPasteboard pasteboardWithUniqueName] now unique the given name to allow only those apps in the same application group to access the pasteboard. If the developer attempts to create a pasteboard with a name that already exists and they are not part of the same app suite, they will get their own unique and private pasteboard. Note that this does not affect the system provided pasteboards, general, and find.
  • Starting with Seed 2, apps default to using the new view controller-based status bar management system. To opt out of this, add a value of NO for the UIViewControllerBasedStatusBarAppearance key to your Info.plist.
  • When using Auto Layout to position a UIButton, if you set the content compression resistance or content hugging priority to minimum, the button will have ambiguous layout.Workaround: Don’t use a content compression resistance or content hugging priority of less than 2 for UIButton.
  • UIScreenEdgePanGestureRecognizer allows you to perform actions in response to swipes over the edge of the screen using the same heuristics that the system uses for its own gestures. Use this if you have a navigation semantic of your own that doesn’t use UINavigationController but should include this gesture (e.g., Safari).This gesture recognizer has a property that describes the edges on which it’s active. UIRectEdge is a new enum type that this property and -[UIViewController edgesForExtendedLayout] can share.UIRectEdge replaces UIExtendedEdge, which will be removed. The members of both have the same values. Use Xcode to replace all instances of “UIExtendedEdge” in your project with “UIRectEdge”.
  • UIButtonTypeInfoLightUIButtonTypeInfoDark, and UIButtonTypeDetailDisclosure buttons all look the same.
  • Blurred layers are not available on iPhone 4.
  • Parallax is not available on iPhone 4.
  • Letterpress text is not available on iPhone 4.

Known Issues

Password fields are not displayed in alert views for apps in landscape (for example, Game Center authentication or In-App Purchase). Text entry still works, though you can’t see what you are typing.

Weather

Notes

Weather conditions are not animated on iPhone 4.

WebKit

Notes

  • Previously, when the viewport parameters were modified, the old parameters were never discarded. This caused the viewport parameters to be additive.For example, if you started with width=device-width and then changed it to initial-scale=1.0, you ended up with a computed viewport of width=device-width, initial-scale=1.0.In iOS 7, this has been addressed. Now you end up with with a computed viewport of initial-scale=1.0.
  • Previously, when using <meta name=”viewport” content=”initial-scale=1.0, user-scalable=1″>, the scale could be incorrect after rotation.Now, if a user has not scaled the page explicitly, the page is restored to its initial scale. Also, the current scale is now correctly restricted within the min-scalemax-scale bounds.
  • Some images for Retina display devices appear at twice the size that they should instead of being scaled down 50%. This issue can also occur with any image to be scaled that is larger than its container and that uses either the background-size property or the -webkit-background-size property. This issue affects both native apps that display web content and web pages viewed in Safari for iPhone.The background CSS shorthand property now resets the value of the background-size property to auto when background size is not specified. This new behavior is per the CSS spec, and the old behavior is available only for apps linked to an SDK prior to iOS 7.0 when running on iOS 7 or later.Workaround: Specify the background-size property or the -webkit-background-size property after the background shorthand property in the CSS stylesheet for the web content being displayed.
  • Web apps and web clips created prior to Seed 4 will not stay in folders across reboot.Workaround: Delete the old web app or web clip and recreate it in this seed by loading the content in Safari, tapping the Action button, and then “Add to Home Screen.”

Wi-Fi

Notes

Seed 4 and later include changes to AWDL such that technologies that use it—such as AirDrop and the MultiPeerConnectivity APIs—will not work properly with older seeds.