感谢Thanks, Jean!
OTA升级软件大小是128兆
通过OTA安装iOS 5beta 5， 你必须擦除设备上的所有文件和设置，设置，通用，恢复，擦除所有设置和文件。OTA升级可以在当前的ios 5 beta 3及以上版本使用，选择设置，通用，软件升级
说明和已知问题
以下问题是在5.0 SDK发现。
账户
- 当创建一个iCloud账户，你可以用任何一个邮箱注册Apple ID，并非MobileMe账户，如果你已经有了MobileMe账户，你可以迁至MobileMe到iCloud，去 http://developer.apple.com/icloud 获得详细信息
- 通过iCloud或Mobileme设定账户时，打开Find My iPhone， 也许会无法启动设定完成后，请在设定，邮箱，再次验证是否启用
- 新：启动iCloud服务后，也许不会正常保存设置，当完成安装助手，去设定，iCloud去三次验证iCloud账户状态，如果你有多个iCloud或MobileMe账户设定在设备上，也要再次确认每个账户的设定，邮箱，联系人，日历
- 建议使用多个账户的用户关闭书签，如果启动，也许会导致未定义
- 默认iOS 5 会在应用程序和网页启动Airplay
- iOS 5 支持Airplay在AV项播出视频
- 苹果TV软件测试版允许用户使用Airplay播放iPad 2 媒体到第二代苹果TV，这个测试版也允许在苹果 TV使用照片流，所以用户可以访问iCloud存储的照片。 这个测试版提供测试最新的airplay功能。 如果想安装Apple TV 测试版在你的设备，你必须先注册你的设备UDID到iOS开发程序
- 生日日历暂时在iCloud不可用，但是将在未来开放
- 新：默认日历还会在iphone 日历，不论是否设定iCloud账户。解决方法，完成账户向导后在设置，邮箱，联系人，日历，重设默认日历
- 新：pushingiCloud日历数据暂时不可用。暂时只能手动到日历程序刷新
- 几个过滤在 beta 1已经添加. 包括以下filters:CIAdditionCompositing, CIAffineTransform, CICheckerboardGenerator,CIColorBlendMode, CIColorBurnBlendMode, CIColorControls, CIColorCube,CIColorDodgeBlendMode, CIColorInvert, CIColorMatrix, CIColorMonochrome,CIConstantColorGenerator, CICrop, CIDarkenBlendMode, CIDifferenceBlendMode,CIExclusionBlendMode, CIExposureAdjust, CIFalseColor, CIGammaAdjust,CIGaussianGradient, CIHardLightBlendMode, CIHighlightShadowAdjust, CIHueAdjust,CIHueBlendMode, CILightenBlendMode, CILinearGradient, CILuminosityBlendMode,CIMaximumCompositing, CIMinimumCompositing, CIMultiplyBlendMode,CIMultiplyCompositing, CIOverlayBlendMode, CIRadialGradient,CISaturationBlendMode, CIScreenBlendMode, CISepiaTone, CISoftLightBlendMode,CISourceAtopCompositing, CISourceInCompositing, CISourceOutCompositing,CISourceOverCompositing, CIStraightenFilter, CIStripesGenerator, CITemperatureAndTint, CIToneCurve, CIVibrance, CIVignette, and CIWhitePointAdjust
GameKit
- 修正数据限制到4KB
- 新：当登录游戏中心，密码也许会被清除，导致无法登陆，再次尝试会成功
- 新，在这个测试版，GameKit 邀请也许会不成功。解决方法，重启设备
- 部分文字或图片在iBook 1.2.2版本无法显示，请到app store升级到1.3版
iCloud Backup
- As this is beta software, it is recommended that you do not use the iCloud services to store any critical data or information. If you enable iCloud Backup, automatic backup with iTunes when syncing will be disabled. We also suggest that you manually back up your device with iTunes. Backups made with earlier versions of iOS 5 beta will soon become incompatible, and will no longer be available. It is strongly advised you upgrade to this version of the iOS 5 beta in order to continue backing up your devices. If you encounter errors restoring from a backup, or enabling a backup more than one hour after signing into iCloud, try deleting your iCloud account from Settings and adding it back. If errors persist, please try erasing your device and initiating the restore again.
- During the iOS 5 beta period, any documents stored on the servers might be purged periodically before GM. Therefore, it is highly recommended that you do not store any critical documents or information on the servers.
- NEW: Provisioning Profiles no longer need to be enabled for iCloud in the iOS Provisioning Portal. All newly generated provisioning profiles are now automatically enabled for iCloud. If you are using an Xcode managed Team Provisioning Profile, click refresh in the Xcode Organizer to obtain a new iCloud-enabled profile. To enable all other provisioning profiles for iCloud, simply regenerate your profiles in the iOS Provisioning Portal.
- If your application is using the NSMetadataQuery class, you must set a predicate, even though the predicate itself is ignored.
- In this beta, the setSortDescriptors: method of NSMetadataQuery is not supported.
- FIXED: To use iCloud prior to beta 5, you had to
manually specify various container identifiers (your application’s
Display set) within an Entitlements file for both of your Mac OS X and
iOS projects. Starting in beta 5, to enable iCloud storage within your
apps, simply click the “Enable Entitlements” checkbox in the Summary
pane of your project. Xcode will create a custom entitlements file for
your project that automatically includes your Team ID. You can add
additional iCloud Container values as required by your application.
(Note that you must regenerate your existing provisioning profiles,
either with Xcode or in the iOS Provisioning Portal, to use iCloud
storage.)
If you specify a custom identifier string for your iCloud Key-Value Store or iCloud Container entitlement values, you no longer need to prepend your Team ID to the beginning of the string. Xcode will prepend your Team ID to these entries automatically - The container identifier string you pass to the URLForUbiquityContainerIdentifier:method of NSFileManager MUST include the team ID at the beginning of the string. As a convenience, if you pass nil, Foundation uses the first document container ID specified in your app’s entitlements.
- There are issues using the Cloud Storage document API in conjunction with protected data which can lead to data corruption.
- FIXED: In this beta, document-based applications cannot always detect when files change, move, or are deleted out from underneath them.
- In this beta, file presenters (objects that adopt the NSFilePresenter protocol) do not receive some of the messages that they’re supposed to receive, especially:
- You can workaround this by implementing the relinquishPresentedItemToWriter: method and checking to see if the writer actually wrote when your file presenter reacquires. You can also use FSEvents to observe file system changes
- In this beta, messages about changes to files in a directory are not getting delivered to objects that adopt the NSFilePresenter protocol.
- While reporting a bug related to the iCloud storage interfaces, please include the logs collected during your debugging session. To generate these logs, you must install a special debug profile on your device. The debug profile can be obtained fromhttp://connect.apple.com. This profile enables the generation of debug logs that are needed to diagnose any problems using iCloud storage. The instructions to collect the logs are:
- Install the profile. (The easiest way to do this is to mail it to yourself and open the attachment on their device.)
- Reproduce the bug.
- Sync with iTunes to pull the logs off your device.
- Attach the logs to your bug report. You can find the logs in ~/Library/Logs/CrashReporter/MobileDevice/DeviceName/DiagnosticLogs.
- These logs can grow large very quickly, so you should remove the profile after you have reproduced the problem and pulled the logs for the bug report.
- NEW: File names are case-insensitive in OS X but case-sensitive in iOS. This can lead to problems when syncing files between the two. You should take steps on iOS to avoid creating files whose names differ only by case.
- iMessage beta1将会无法和Beta 2或以后版本交流
- 新: 当用侧边音量键或者耳机音量键调整音量大小，不会显示调整后的音量
- The version of iTunes that comes with beta 5 cannot sync devices that have the beta 4 software installed. To avoid this problem, do the following:
- Sync any devices that have beta 4 installed to the version of iTunes that came with beta 4.
- Upgrade iTunes to the version that comes with beta 5.
- Connect the device and install the beta 5 software. (Understand that you might see a failure to sync error when you first connect the device.)
- After installing the beta 5 software, restore from your the backup you made in step 1.
- Videos purchased from the iTunes Store do not play on a 2nd generation AppleTV over AirPlay with iTunes 10.5.
- FIXED: The startMonitoringSignificantLocationChanges method of CLLocationManager does not cause applications to be resumed or launched in the background for significant location change updates. However, if a backup from a previous software version (where an application was monitoring significant location changes) is restored to the device, significant location change monitoring will continue to cause that application to be resumed or launched in the background.
- FIXED: Forwarding a message with attachments included does not attach the file and the message compose screen does not change from “Loading….”
- NEW: When changing the host name of an email account in settings, blank messages may be seen in the unified inbox. As a workaround, delete and re-add the account instead of changing its host name.
- FIXED: Some songs are missing their album artwork after changing the device library via syncing.
- FIXED: In iOS 5.0 beta 4, several OpenGL ES extensions have been moved from the APPLE namespace to the EXT namespace, causing some API to be renamed. The altered extensions are EXT_color_buffer_half_float, EXT_occlusion_query_boolean, EXT_separate_shader_objects, EXT_shadow_samplers, EXT_texture_rg, EXT_debug_label, and EXT_debug_marker.
- If you are doing an OTA software update, you will need to re-sync your photos with iTunes.”
- FIXED: In this beta, iPhone 4 device cannot join personal hotspot even if it is on due to a non functional Wi-Fi tethering on these devices.
- FIXED: If you apply red-eye adjustments in iOS, and import your image into the iPhoto seed build, the red-eye adjustments will not appear on that image in iPhoto. As a result, subsequent syncing of your image back to the iOS device from iPhoto will not show the red-eye adjustments.
- NEW: When restoring photo libraries from an iTunes backup, some photos may not appear in the Photos application after restore. Please back up your photos before updating to iOS Beta 5.
- Location services are not functional in iOS 4.3 simulator running on Mac OS 10.7 with Xcode 4.2.
- Push and local notifications for apps appear in the new Notification Center in iOS 5. Notification Center displays notifications that are considered “unread.” In order to accommodate push and local notifications that have no “unread” status, developers can use their application badge count to trigger a clearing of notifications from Notification Center. When an application clears its badge count (by setting it to zero), iOS 5 will clear its notifications from Notification Center.
- FIXED: iOS 5.0 terminates VoIP applications that are resumed in the background for incoming network traffic with extreme frequency. Developers are encouraged to make sure all incoming data is read from VoIP sockets to avoid this condition.
- NEW: The UIPrerenderedIcon key (in the Info.plist file) is not honored in this build.
- NEW: In-App purchase will not work for developers testing their apps with the iTunes Sandbox.
- FIXED: When tweeting your location from Safari and exiting before the location can be established, the location arrow will stay in the status bar. The arrow can be removed by killing Safari from the task switcher.
- FIXED: Instruments overwrites the loaded automation script, even if another program is editing it.
- FIXED: The play and record buttons in the Automation instrument script editor may not work properly after targeting an application that was launched by a trace session and has ended. They may also not work if you target an application that was suspended. If you run into this problem and it persists, you may need to close and reopen the trace document to get back into a functional state.
- FIXED: When capturing actions into a script using the Automation instrument, interfaces with web views or table cells that contain a high number of off screen elements may take an extremely long time before returning with an expression.
- The lock() and unlock() functions of UIATarget have been replaced with the lockForDuration(
) function. - Starting in iOS 5 beta 2, you can now trigger the execution of an UI Automation script on an iOS device from the host terminal by using the instruments tool. The command is:
- instruments -w
-t - When using the cli instruments for UI Automation you can now target the default Automation Template and pass the script and results path into the tool as environment variable options. For example:
- instruments -w
-t /Developer/Platforms/iPhoneOS.platform/Developer/Library/Instruments/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate -e UIASCRIPT
No comments:
Post a Comment