Apple on Friday pushed out iOS 7.1 beta 2, the latest pre-release version of its popular mobile operating system. The new iOS 7.1 software is available only to developers and it follows the release of Apple’s initial iOS 7.1 beta, which was first offered to developers on November 18th. The latest available public version of iOS is still iOS 7.0.4. iOS 7.1 beta 2 is available for download beginning immediately as an over the air (OTA) update and it will be released on Apple’s developer portal shortly. The software is compatible with the iPhone 4, iPhone 4S, iPhone 5, iPhone 5c, iPhone 5s, iPad 2, iPad (third and fourth generations), iPad Air, iPad mini and iPhone mini with Retina display.
UPDATE: BGR has been provided with the full, albeit brief iOS 7.1 beta 2 change log and release notes, which follow below.
Notes and Known Issues
The following issues relate to using iOS SDK 7.1 beta 2 to develop code.
32-bit apps running on a 64-bit device cannot attach to BTServer.
A compatibility behavior has been added to address an issue where some web servers would send the wrong Content-Length value for “Content-Encoding: gzip” content. Previously,
NSURLSessionwould send a “network connection was lost” / NSURLErrorNetworkConnectionLost (-1005) error in this situation.
The compatibility behavior applies only if the Content-Length value exactly matches the expanded gzip’d content. It won’t apply for “off by 1” or similar miscounting.
Fixed in iOS 7.1 beta 2
Crash logs now appear in Diagnostics & Usage Data in Settings.
If you create a new iCloud account during setup assistant, you may encounter an error when trying to enable iCloud Keychain.
Workaround: Select Setup Keychain Later in setup assistant, then enable iCloud Keychain in Settings.
Fixed in iOS 7.1 beta 2
Loading a large iTunes Match library should no longer take an especially long time to load.
Audiobooks fail to play.
A property, minimal-ui, has been added for the viewport meta tag key that allows minimizing the top and bottom bars on the iPhone as the page loads. While on a page using minimal-ui, tapping the top bar brings the bars back. Tapping back in the content dismisses them again.
For example, use .
- If a
UILabelthat is baseline aligned with constraints has attributes that change after the constraints have been added, the layout may be incorrect. The exception to this is
UILabel, which should work as expected.Workaround: Avoid making changes in
UILabelafter adding baseline-alignment constraints. If you must make changes, you should remove the constraints and then reapply them afterward. Note that this is a performance hit, so don’t do it unless it is necessary.
backIndicatorTransitionMaskfrom a storyboard or a xib will not be interpreted correctly at runtime.Workaround: Set the
More from BGR: How IFTTT automated (and archived) my digital life
This article was originally published on BGR.com