12:15 PM — Under a month ago, Apple released beta 2 to developers, and now the company has released iOS 7.1 beta 3 to developers. This can be downloaded from the Apple dev center, or if you have your device registered to your dev account, it can be processed via Over The Air (OTA) update.
The built number for beta 3 is 11d5127c. This can be downloaded onto all compatible iPhone, iPad and iPod devices.
As always, beta 3 includes a host of new bug fixes and perhaps even features. We will keep you updated as to what’s new in beta 3. Below, you will find the full change log that Apple released for beta 3. Keep the page bookmarked as we will continue to update the post as we find new things in beta 3. We are currently installing it ourselves and will report back shortly.
[learn_more caption=”iOS 7.1 Beta 3 Change Log”]
Notes and Known Issues
The following issues relate to using iOS SDK 7.1 beta 3 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 3
Creating a new iCloud account during setup assistant, should no longer give you an error when you enable iCloud Keychain.
Messages sometimes indicates iMessage send failure immediately after sending.
Workaround:Tap the error icon to re-send the message.
Fixed in iOS 7.1 beta 3
Audiobooks now play as expected.
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 <meta name=”viewport” content=”width=1024, minimal-ui”>.
- 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