Now that we have risen up to the iOS 7.1 it now gets reset back to the beta versions, hence the number 1 all over again. For those of you interested, this one carries the build number of 11D5099e with it.
Here’s what features are new:
- Dark keyboard toggling made viewable.
- Burst mode photos.
- Bold text works without restarting.
- Auto HDR mode.
- Pinch to close tweak. This one is for iPad users only.
- Notification Center has been revamped.
All up, that’s a lot of changes to be made to the feature side of things. Normally by this stage we are used to having nothing but performance enhancements and bugs that were there taken away before.
We knew that Apple was already working on this for a few months, just after the first iOS 7 was released. That was mainly thought to be because of all the bugs though, and not to be working on any new things to use.
Don’t forget that this is just the first of what always seems to be 4 incremental updates, which will then lead to the full release of the iOS 7.1. Knowing that, don’t get too excited just yet with what we are seeing.
If it’s hacking that you enjoy doing, the jailbreaking team has said not to worry about updating, ensuring that everything will be fine if you do. This is the general consensus about all the beta updates. It’s a bit suspicious when we think back to the other years when they were always considered major Do’s or Don’ts. It will mean either one of two things. The Evasi0n guys aren’t even bothering to work on a jailbreak yet because they know it’s worthless and are keeping hush about it, or they already have found the only exploit they need. The latter doesn’t make a great deal of sense, but it’s more fun to imagine that scenario as being the true one.
It’s hard to predict exactly when we will see the Beta 2 come out. Because we knew this one had worked already since September and very soon after the new software came out, it would be fair to assume that they had probably started with the Beta 2 already. However, there has been no talk around the web of this being true at all. We’ve also seen many new things that could easily have taken up all of Apple’s time, and from all reports so far from people who have used this latest build, it seems to be working nicely. If we had to guess, we’d say it will be between two weeks and one month before we see any further progress on the firmware side of things.
This one was seeded to developers overnight and the full change-log can be seen here:
iOS 7.1 Release Notes
iOS SDK 7.1 provides support for developing iOS apps, and it 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 for iPhone, iPad, or iPod touch running iOS 7. You can also test your apps using the included iOS Simulator, which supports iOS 7. iOS SDK 7.1 requires a Mac computer running OS X v10.8.4 (Mountain Lion) or later.
This version of iOS is intended for installation only on devices registered with the Apple Developer Program. Attempting to install this version of iOS in an unauthorized way could put your device in an unusable state.
For more information and added support resources, visithttp://developer.apple.com/programs/ios/.
Bug Reporting
To report any bugs not mentioned in the Notes and Known Issues section, use the Apple Bug Reporter on the Apple Developer website (http://developer.apple.com/bugreporter/). Additionally, you may discuss these issues and iOS SDK 7.1 in the Apple Developer Forums: http://devforums.apple.com. To get more information about iCloud for Developers, go to http://developer.apple.com/icloud.
Notes and Known Issues
The following issues relate to using iOS SDK 7.1 to develop code.
Bluetooth
Known Issue
32-bit apps running on a 64-bit device cannot attach to BTServer.
CFNetwork
Fixed in iOS 7.1 beta
Previously, if the server-side closed an HTTP request with TCP FIN without sending any bytes of HTTP header or HTTP body, NSURLConnection would synthesize an empty HTTP/1.1 200 OK response. This is now fixed, and the request will result in an error instead of a successful load with a synthesized response.
Notes
A new 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, NSURLConnection and NSURLSession would 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.
Core Text
Fixed in iOS 7.1 beta
Previously, text drawn with CTFrameDraw did not correctly place lines to account for the paragraphSpacing attribute of NSParagraphStyle. This has been addressed in iOS 7.1 beta.
Crash Logs
Known Issue
Crash logs will not appear in Diagnostics & Usage Data in Settings. The logs will still be available when synced off the device.
GLKit
Fixed in iOS 7.1 beta
If loaded with GLKTextureLoader, pngcrush images that have alpha were not unpremultiplied.
High Precision Timers
Fixed in iOS 7.1 beta
When sleeping or waiting for extremely precise time intervals, timers were delayed by up to 1 millisecond.
iTunes
Known Issue
Loading an iTunes Match library (or your purchased music history) may take much longer than expected, especially on larger libraries. If your library does not sync right away, please wait 30 minutes and try to access it again.
Multipeer Connectivity
Fixed in iOS 7.1 beta
The MCSessioninitWithPeer: method has now been implemented properly.
For more information on MCSession APIs, watch WWDC 2013: Nearby Networking with Multipeer Connectivity.
UIKit
Known Issues
If a UITextField or a UILabel that 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 -setFont: on UILabel, which should work as expected.
Workaround: Avoid making changes in UITextField or UILabel after 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.
The backIndicatorTransitionMask from a storyboard or a xib will not be interpreted correctly at runtime.
Workaround: Set the backIndicatorTransitionMask in code.