อัพเดท iOS 7.1 ปล่อยออกมาให้ดาวน์โหลดแล้ว [สำหรับนักพัฒนา]

เพิ่งปล่อยอัพเดท iOS 7.0.4 ให้ผู้ใช้ทั่วไป ไปเมื่อไม่กี่วันก่อน ล่าสุดวันนี้ทางแอปเปิลได้ส่งไฟล์อัพเดท iOS 7.1 beta ให้สำหรับนักพัฒนาไปทดลองใช้กันก่อนแล้ว โดยในเวอร์ชั่นนี้ยังไม่มีการเพิ่มฟีเจอร์ใหญ่ๆ อะไรเข้ามา เพียงแต่เป็นการแก้บั๊กและปรับปรุงข้อผิดพลาดต่างๆ ตั้งแต่เปิดตัว iOS 7 มา (หวังว่าจะแก้ปัญหาภาษาไทยด้วยนะ) ใครที่เป็น Apple Developer อยู่ ก็สามารถไปดาวน์โหลดกันได้เลยนะครับ เชื่อว่า iOS 7.1 ตัวเต็มสำหรับผู้ใช้ทั่วไป น่าจะปล่อยออกมาให้อัพเดทในอีกไม่นานนี้

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 manner could put your device in an unusable state.

For more information and additional support resources, visit http://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.

ที่มา – 9to5mac

ส่งต่อเรื่องนี้ให้เพื่อน!
TANA:
Related Post