iPhone SE 를 사용중에 터치 문제가 있어 최근 리퍼를 받아와서 잘 사용중이였다.


그런데 갑자기 어느날 아침 전화를 하려고 핸드폰을 사용하려는데... 아무런 소리가 들리지 않았다.


재부팅도 해보고 블루투스 에 이어폰이 연결된건지도 체크해봤지만... 전혀 아무소리도 들리지 않는 문제 발생...



[이슈]

- 핸드폰 수화기에서 통화 하려고 해도 아무런 소리도 들리지 않음...


[체크]

- 우선 블루투스 이어폰이 연결된건 아닌지 확인

- 볼륨버튼을 조작해 보기

- 통화 시도후 스피커폰으로 사용해보기




[원인]


- 볼륨 버튼 조작 시 아래 사진 처럼 헤드폰 이라고 메시지가 보여진다면.... 



원인은 바로 이어폰 단자 의 이물질등에 의한 문제!!


=> 당연하지만... 최신 핸드폰에서 빠진 이어폰 단자가 없는 7 이상의 아이폰은 해당 해결방법은 전혀 무관하니 a/s 센터를 찾아가시길 ...


[해결]

- 해결방법은 단순하다~! 청소하면 됨;;;




끝;;

'Tip' 카테고리의 다른 글

아이폰 갑자기 소리가 안날때!!  (0) 2017.08.02
티스토리 블로그 안뜰때  (0) 2016.12.19
아베스트 삭제 방법  (0) 2015.11.19
모바일웹 테스트  (0) 2015.08.11

개발자 버전인 iOS 9.1 beta 3 build 13B5130b 가 공개 되었습니다.

- 알려전 버그 수정 정도 의 업데이트



iOS 정식 9.0.2 업데이트
- 업데이트 는 설정 > 일반 > 소프트웨어 업데이트 에서 할수 있습니다.

iOS SDK Release Notes for iOS 9.1 Beta 3

Contents:

Introduction

iOS SDK 9.1 beta 3 provides support for developing iOS apps. It is packaged with a 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 9. You can also test your apps using the included Simulator, which supports iOS 9. iOS SDK 9.1 requires a Mac computer running OS X v10.10.3 (Yosemite) 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

For issues not mentioned in the Notes and Known Issues section, please file bugs through the Apple Developer website (https://developer.apple.com/bug-reporting/ios/). Additionally, you may discuss these issues and iOS SDK 9.1 in the Apple Developer Forums: https://forums.developer.apple.com/community/pre-release/ios-9-beta. To get more information about iCloud for Developers, go to http://developer.apple.com/icloud.

Autosubmission of Diagnostic and Usage Data

By default, the iOS 9.1 beta automatically sends anonymous diagnostic and usage data back to Apple. This includes information about crashes, freezes, kernel panics, and information about how you use Apple and third-party software, hardware, and services. This information is used to help Apple improve the quality and performance of its products and services. You can stop autosubmission of diagnostics and usage data by going to Settings > Privacy > Diagnostics and Usage > Don’t Send.

Notes and Known Issues

Apple ID

Known Issue

If you sign in with different Apple IDs for iCloud and iTunes during Setup Assistant, it may hang.

Workaround: Do not use different Apple IDs for iCloud and iTunes during Setup Assistant. After setup, sign in by going to Settings > App and iTunes Stores.

iCloud Keychain

Note

During the iOS 9.1 beta, iCloud Keychain accounts with two-factor authentication enabled will use beta servers. If you do not want your iCloud Keychain data stored on beta servers, do not use the beta software.

Fixed in Beta 3

  • If you disable two-factor authentication on your iCloud account, your iCloud Keychain may also get turned off.

    Workaround: Confirm that iCloud Keychain is still on in Settings after disabling two-factor authentication.

  • When activating iCloud Keychain in Settings on iPad, you may be unable to complete the activation.

Known Issue

Sometimes while setting up iCloud Keychain, you receive a "Could Not Set Up iCloud Keychain" error.

Workaround: Reboot the device.

Metal

Note

For tvOS Metal development, it is required that you use the tvOS-specific feature set enum MTLFeatureSet_TVOS_GPUFamily1_v1.

PhotoKit

Known Issue

If your app gets the gesture recognizer from the PHLivePhotoView object (via playbackGestureRecognizer) to install it on a different view, subsequently setting a new value forlivePhoto on the PHLivePhotoView object causes it to reinstall the gesture recognizer on itself.

Workaround: Your app can get the gesture recognizer and reinstall it on the appropriate view every time after setting a value for livePhoto.

Podcasts

Fixed in Beta 3

The sleep timer does not work in this beta.

Restore

Fixed in Beta 3

If you’ve set a region that doesn’t match your language, restores from iCloud Backup might not progress.

Workaround: During restore, change your region to match your language. You can change it back after the restore is over.

Known Issue

Sometimes while restoring from iCloud backup, you will not see your list of backups, if you have two-factor authentication enabled on your iCloud account.

Settings

Known Issue

Settings may become unresponsive after signing into an iMessage or FaceTime account.

Workaround: Quit Settings from the App Switcher.

Siri

Known Issue

When asking Siri to play music, Siri will return an error but will still play back the music requested.

UIKit

Note

On 3D Touch capable devices, touch pressure changes cause touchesMoved:withEvent: to be called for all apps running on iOS 9.0. When running iOS 9.1, the method is called only for apps linked with the iOS 9.0 (or later) SDK.

Apps should be prepared to receive touch move events with no change in the x/y coordinates.



'iOS' 카테고리의 다른 글

iOS 9.1 베타 3 , iOS 9.0.2 업데이트  (0) 2015.10.01
iOS 9.1 베타 2 릴리즈 노트  (0) 2015.09.24
iOS 9.1 베타 릴리즈 노트  (0) 2015.09.10
[watchOS] 2GM seed 릴리즈 노트  (0) 2015.09.10


iOS 9.1 베타2 가 릴리즈 되었습니다.


- 몇몇 알려진 버그들이 수정되었네요 ( 비번찾기 링크 오류 등..)


별거아닌거 같지만 가장 큰변화는 연락처 목록에서 사진 감추기 옵션 이 생겼네요 6, 6+ 만 인듯 싶지만













iOS SDK Release Notes for iOS 9.1 Beta

Contents:

Introduction

iOS SDK 9.1 beta provides support for developing iOS apps. It is packaged with a 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 9. You can also test your apps using the included Simulator, which supports iOS 9. iOS SDK 9.1 requires a Mac computer running OS X v10.10.3 (Yosemite) 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

For issues not mentioned in the Notes and Known Issues section, please file bugs through the Apple Developer website (https://developer.apple.com/bug-reporting/ios/). Additionally, you may discuss these issues and iOS SDK 9.1 in the Apple Developer Forums: https://forums.developer.apple.com/community/pre-release/ios-9-beta. To get more information about iCloud for Developers, go tohttp://developer.apple.com/icloud.

Autosubmission of Diagnostic and Usage Data

By default, the iOS 9.1 beta automatically sends anonymous diagnostic and usage data back to Apple. This includes information about crashes, freezes, kernel panics, and information about how you use Apple and third-party software, hardware, and services. This information is used to help Apple improve the quality and performance of its products and services. You can stop autosubmission of diagnostics and usage data by going to Settings > Privacy > Diagnostics and Usage > Don’t Send.

Notes and Known Issues

AppleID

Known Issue

iForgot links may not work.

Workaround: Go to iforgot.apple.com in Safari.

iCloud Keychain

Note

During the iOS 9.1 Beta, iCloud Keychain for iCloud accounts with two-factor authentication enabled will use beta servers. If you do not want your iCloud Keychain data stored on beta servers, do not use the beta software.

Known Issues

  • Sometimes while setting up iCloud Keychain, you recieve a "Could Not Set Up iCloud Keychain" error.

    Workaround: Reboot the device.

  • If you disable Two-Factor Authentication on your iCloud account, your iCloud Keychain may also get turned off.

    Workaround: Confirm that your Keychain is still on in Settings after disabling Two-Factor Authentication.

  • When activating Keychain in Settings on iPad, you may be unable to complete the activation.

  • If you have an account with Two-Factor Authentication and set up iCloud Keychain, it may not succeed if you take a few minutes to get through Setup Assistant.

    Workaround: Go back to the beginning of Setup Assistant and sign into iCloud again.

  • If you had been using a Random Security Code for your Keychain before upgrading to iOS 9.1 Beta, tapping “Back” when prompted to enter your security code in Setup Assistant may result in a sign-in failure.

    Workaround: Go back to the beginning of Setup Assistant and sign into iCloud again.

  • If you change your device passcode while in Airplane Mode, you iCloud Keychain may cease to sync with other devices.

Keyboards

Known Issue

3rd party keyboards don’t appear in sharing sheets and action sheets.

Workaround: Use the Apple keyboard.

PhotoKit

Known Issue

If you add a PHLivePhotoView to an app UI in Interface Builder, it might end up as a regular UIView object at runtime.

Workaround: Declare a dummy PHLivePhotoView subclass in your code:

@interface DummyLivePhotoViewSubclass : PHLivePhotoView
@end
@implementation DummyLivePhotoViewSubclass
@end

Podcasts

Known Issue

If you try to play the last item in a list, Podcasts may crash.

Restore

Known Issue

If you’ve set a region that doesn’t match your language, restores from iCloud Backup might not progress.

Workaround: During restore, change your region to match your language. You can change it back after the restore is over.

UIKit

Note

On 3D Touch capable devices, touch pressure changes cause touchesMoved: to be called. This is true for all apps running on iOS 9.0. When running iOS 9.1, it is true only for apps linked with the iOS 9.0 (or greater) SDK.

Apps should be prepared to receive touch move events with no change in the x/y coordinates.



'iOS' 카테고리의 다른 글

iOS 9.1 베타 3 , iOS 9.0.2 업데이트  (0) 2015.10.01
iOS 9.1 베타 2 릴리즈 노트  (0) 2015.09.24
iOS 9.1 베타 릴리즈 노트  (0) 2015.09.10
[watchOS] 2GM seed 릴리즈 노트  (0) 2015.09.10

iOS SDK Release Notes for iOS 9.1 Beta

Contents:

Introduction

iOS SDK 9.1 beta provides support for developing iOS apps. It is packaged with a 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 9. You can also test your apps using the included Simulator, which supports iOS 9. iOS SDK 9.1 requires a Mac computer running OS X v10.10.3 (Yosemite) 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

For issues not mentioned in the Notes and Known Issues section, please file bugs through the Apple Developer website (https://developer.apple.com/bug-reporting/ios/). Additionally, you may discuss these issues and iOS SDK 9.1 in the Apple Developer Forums: https://forums.developer.apple.com/community/pre-release/ios-9-beta. To get more information about iCloud for Developers, go to http://developer.apple.com/icloud.

Autosubmission of Diagnostic and Usage Data

By default, the iOS 9.1 beta automatically sends anonymous diagnostic and usage data back to Apple. This includes information about crashes, freezes, kernel panics, and information about how you use Apple and third-party software, hardware, and services. This information is used to help Apple improve the quality and performance of its products and services. You can stop autosubmission of diagnostics and usage data by going to Settings > Privacy > Diagnostics and Usage > Don’t Send.

Notes and Known Issues

AppleID

Known Issue

iForgot links may not work.

Workaround: Go to iforgot.apple.com in Safari.

iCloud Keychain

Note

During the iOS 9.1 Beta, iCloud Keychain for iCloud accounts with two-factor authentication enabled will use beta servers. If you do not want your iCloud Keychain data stored on beta servers, do not use the beta software.

Known Issues

  • Sometimes while setting up iCloud Keychain, you recieve a "Could Not Set Up iCloud Keychain" error.

    Workaround: Reboot the device.

  • If you disable Two-Factor Authentication on your iCloud account, your iCloud Keychain may also get turned off.

    Workaround: Confirm that your Keychain is still on in Settings after disabling Two-Factor Authentication.

  • When activating Keychain in Settings on iPad, you may be unable to complete the activation.

  • If you have an account with Two-Factor Authentication and set up iCloud Keychain, it may not succeed if you take a few minutes to get through Setup Assistant.

    Workaround: Go back to the beginning of Setup Assistant and sign into iCloud again.

  • If you had been using a Random Security Code for your Keychain before upgrading to iOS 9.1 Beta, tapping “Back” when prompted to enter your security code in Setup Assistant may result in a sign-in failure.

    Workaround: Go back to the beginning of Setup Assistant and sign into iCloud again.

  • If you change your device passcode while in Airplane Mode, you iCloud Keychain may cease to sync with other devices.

Keyboards

Known Issue

3rd party keyboards don’t appear in sharing sheets and action sheets.

Workaround: Use the Apple keyboard.

PhotoKit

Known Issue

If you add a PHLivePhotoView to an app UI in Interface Builder, it might end up as a regular UIView object at runtime.

Workaround: Declare a dummy PHLivePhotoView subclass in your code:

@interface DummyLivePhotoViewSubclass : PHLivePhotoView
@end
@implementation DummyLivePhotoViewSubclass
@end

Podcasts

Known Issue

If you try to play the last item in a list, Podcasts may crash.

Restore

Known Issue

If you’ve set a region that doesn’t match your language, restores from iCloud Backup might not progress.

Workaround: During restore, change your region to match your language. You can change it back after the restore is over.

UIKit

Note

On 3D Touch capable devices, touch pressure changes cause touchesMoved: to be called. This is true for all apps running on iOS 9.0. When running iOS 9.1, it is true only for apps linked with the iOS 9.0 (or greater) SDK.

Apps should be prepared to receive touch move events with no change in the x/y coordinates.


'iOS' 카테고리의 다른 글

iOS 9.1 베타 2 릴리즈 노트  (0) 2015.09.24
iOS 9.1 베타 릴리즈 노트  (0) 2015.09.10
[watchOS] 2GM seed 릴리즈 노트  (0) 2015.09.10
애플워치2 베타5 업데이트 방법  (0) 2015.08.12




애플 워치도 기존 아이폰과 동일하게 베타 os 로 설정이 가능하다~


다른점은 아이폰을 통해진행되는 내용이기 때문에~ 


1. 우선 아이폰이 우선 9.0 베타 버전이 설치 되어 있어야 한다~!


대신 애플워치는 UDID 등록 할 필요는 없다는거~





2. 애플워치 베타 OS 업그레이드를 위해서는 프로파일 설치가 필요하다.


watchOS_2_beta.mobileconfig


아이폰 9.0 에서 위 파일 을 클릭하여 프로파일을 등록 해준다~


안될경우~ 다운로드 받아서 메일 첨부 파일로 전달 하여 진행하면 된다.


설치 한경우 아래와 같은 화면을 볼수 있다 ( 아이폰 에서 보는 애플워치 프로파일 등록 화면)




3. 등록후 아이폰에 있는 애플워치 앱 설정 > 소프트웨어 업데이트에서 업데이트를 확인 할수 있다


바로 업데이트 진행~!

업데이트 진행시 다운로드 초반 과 다운로드 후 설치 시 애플워치 잠금 해제가 필요하다



4. 업데이트 진행


시작시에 2시간 남음 이라고 되어있어서... 설마 했는데 스샷만 찍어놓고 자세히 안봤는데 정말로 2시간 정도 걸린듯;;


아래 안내 멘트에도 나오지만,


업데이트 설치시~! Apple Watch 가 

- Wi-Fi 에 연결된 iPhone 의 범위 내에 있고

-충천기에 연결되어 있고

- 최소 50% 이상 충전 되어야 합니다.







'iOS' 카테고리의 다른 글

[watchOS] 2GM seed 릴리즈 노트  (0) 2015.09.10
애플워치2 베타5 업데이트 방법  (0) 2015.08.12
iOS 9 Beta 5 Release Notes  (0) 2015.08.07
애플 watchOS 2 릴리즈 노트 베타4  (0) 2015.08.03

iOS SDK Release Notes for iOS 9 Beta 5

Contents:

Introduction

iOS SDK 9.0 provides support for developing iOS apps. It is packaged with a 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 9. You can also test your apps using the included Simulator, which supports iOS 9. iOS SDK 9.0 requires a Mac computer running OS X v10.10.3 (Yosemite) 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

For issues not mentioned in the Notes and Known Issues section, please file bugs through the Apple Developer website (https://developer.apple.com/bug-reporting/ios/). Additionally, you may discuss these issues and iOS SDK 9.0 in the Apple Developer Forums: https://forums.developer.apple.com/community/pre-release/ios-9-beta. To get more information about iCloud for Developers, go to http://developer.apple.com/icloud.

Autosubmission of Diagnostic and Usage Data

By default, the iOS 9 beta automatically sends anonymous diagnostic and usage data back to Apple. This includes information about crashes, freezes, kernel panics, and information about how you use Apple and third-party software, hardware, and services. This information is used to help Apple improve the quality and performance of its products and services. You can stop autosubmission of diagnostics and usage data by going to Settings > Privacy > Diagnostics and Usage > Don’t Send.

Notes and Known Issues

The following issues relate to using iOS SDK 9.0 to develop code.

Accessories

Fixed in Beta 5

Lightning video dongles don’t work with this beta.

App Store

Note

iOS 9 enforces the UILaunchImages requirement; apps can no longer declare the same launch image to support different interface orientations.

Known Issue

Users might be prompted twice for credentials on the first In-App Purchase.

Apple ID

Note

Some users will be offered the option to upgrade their Apple ID to use two-factor authentication. For more information about two-factor authentication see developer.apple.com/support/two-factor-authentication. Two-factor authentication is not supported on iOS 9 betas prior to beta 3.

Fixed in Beta 5

  • You may not be able to create a new Apple ID in Settings or Setup Assistant.

    Workaround: Create a new iCloud account on iCloud.com.

  • You cannot manage your two-factor authentication trusted devices at appleid.apple.com.

    Workaround: You can find and manage trusted devices in Settings > iCloud > yourName > Devices.

  • Removing a device from your account removes it as a trusted device for two-factor authentication, but will not sign out of any services or permanently remove it from the device list.

    Workaround: To fully remove a device, click Remove From Account then sign out of iCloud in device Settings of the device you want to remove.

Known Issues

  • iForgot links may work intermittently.

    Workaround: Please try again.

  • If you upgrade your Apple ID to use two-factor authentication, iTunes purchases on Mac and Windows and store purchases on Apple TV will require you to append a six-digit verification code to the end of your password on every purchase. The six-digit code will display automatically on your iOS 9 or OS X El Capitan devices, or can be sent to your trusted phone number via a text message or phone call.

  • If your Apple ID uses two-factor authentication, you may not be able to sign in to services that use Apple ID on iOS 9 and OS X El Capitan beta installations earlier than beta 3.

  • If you disable two-factor authentication and set a new password at iForgot.apple.com, the password requirements are not indicated so your password may not be accepted.

    Workaround: Make sure your password meets these requirements:

    • Have at least one lowercase letter

    • Have at least one uppercase letter

    • Have at least one number

    • Your password must not contain more than two consecutive identical characters

    • Not be the same as the account name

    • Be at least 8 characters

    • Not be a common password

AVFoundation

Notes

  • The canUseNetworkResourcesForLiveStreamingWhilePaused property has been added to AVPlayerItem. The default value is NO for apps linked on or after iOS 9.0 or OS X 10.11, but YES for apps that were linked earlier.

    To minimize power usage, set this property to NO if you do not need playback state to stay up to date while paused.

  • AVQueuePlayer now supports a mixture of file-based media and HTTP Live Streaming media in its queue. Prior to this, you had to ensure that all items in the queue were of the same type.

  • For apps linked against iOS 9 or later, the media interruption behavior for AV(Queue)Player has changed.

    Before iOS 9, apps could interrupt other media-playing clients by associating or adding AVPlayerItem to AVPlayer or by modifying the time or date of the current AVPlayerItem (using the seekToTime: or seekToDate: methods). In iOS 9, these operations interrupt only when AVPlayer object’s playback rate is changed to a non-zero value through the rate property or play method.

  • Picture in Picture playback might stop and the Picture in Picture button might disappear when using AVPlayerViewController for video playback and replacing the underlying AVPlayer object’s current item usingreplaceCurrentItemWithPlayerItem:.

  • The AVPictureInPictureController interface and the cancelPictureInPicture method are deprecated.

Calendar

Fixed in Beta 5

Calendar may hang if you tap Ignore on a suggested event.

CarPlay

Fixed in Beta 5

The Home button may not always work.

Known Issue

The navigation bar in Maps can sometimes get into a state where it is inaccessible.

CBCentralManager

Note

The retrievePeripherals: and retrieveConnectedPeripherals methods were deprecated in iOS 7.0 and removed in iOS 9.0. Apps that use these methods will crash on launch or upon pairing an accessory.

Enterprise

Note

iOS 9 adds support for TLS v1.2 in 8021.X authentication. Authentication servers that support TLS v1.2 may require an update for compatibility. If you are using FreeRADIUS, update to version 2.2.7 or 3.0.8. If you are using Aruba ClearPass update to version 6.5.2. If you are using other Aruba products, update to ArubaOS 6.4.2.9.

Foundation

Notes

  • There is new Foundation API that can be used to detect if the device is in Low Power Mode. See the updated Energy Efficiency Guide for iOS Apps for details.

  • Horizontal location constraints should consistently reference either left/right or leading/trailing attributes. For apps linked against the iOS 9 SDK, NSLayoutConstraint will throw an exception if you attempt to create a constraint between a leading/trailing attribute and a left/right attribute.

HealthKit

Known Issue

In rare circumstances, it is possible for the health database to be deleted during an upgrade to a beta build.

Workaround: To make sure the health database is not lost, make an encrypted iTunes backup prior to installing this beta.

Although keeping the device unlocked for the duration of the upgrade process reduces the risk of the database being destroyed, it’s recommended that you create a backup so that you can recover the database if you encounter this issue.

Home Sharing

Fixed in Beta 5

  • If you have an empty music library, you will be unable to enable or disable Home Sharing in Music.

  • The Home Sharing option doesn't always appear in My Music.

iCloud Drive

Note

The fetchAllChanges property on CKFetchRecordChangesOperation has been deprecated, and will be removed in iOS 9.

Keyboards

Note

Russian, Turkish, and Korean QuickType keyboards require iOS 9 beta 2 or later.

Fixed in Beta 5

If you use a complex passcode on an iPad, some panes in Settings will now show the keyboard.

Keychain

Note

iCloud Keychain will not sync passwords & credit cards with previous betas of iOS 9 and OS X El Capitan.

Fixed in Beta 5

  • You may not be able to accept a Suggested Password when creating a new account.

  • You may be unable to join an existing iCloud Keychain circle using iCloud Security Code and SMS Verification Code.

  • After changing your iCloud password, you may see an “iCloud Keychain Reset” prompt.

  • If you have two-step verification enabled on your AppleID and then change your iCloud Keychain or iCloud Security Code on a non-trusted device, you see a “Verification Failed” error.

  • If your iCloud account uses two-factor authentication, you will get a sign-in alert on all logged-in iOS 9 or OS X El Capitan devices whenever there is a change in the phone number in Settings > iCloud > Keychain > Advanced.

Mail

Known Issue

A Yahoo mail account may periodically display “Cannot get mail.”

Maps

Known Issue

If you use Siri to get driving, walking, or transit directions, you may see a failure with a dialog that says “Current Location not Available.”

Workaround: Toggle Wi-Fi and then try again. Alternatively, get directions in Maps directly without using Siri.

Messages

Fixed in Beta 5

  • When recording audio messages, the audio glyphs are not shown. This occurs in both quick reply and in the Messages app.

  • When you send an audio message, it may be difficult to begin playback.

Music

Note

When users plug in headphones or connect to Bluetooth or CarPlay in their car, their favorite music app appears on the lock screen or the car display.

For your app to be eligible for this, it must publish to Now Playing upon launch and consistently maintain a Now Playing state. A common practice upon launch is to continue playing the track from when the app was last exited.

Known Issues

  • The share sheet may not appear when sharing tracks from Apple Music.

  • The New tab may not load if you are not signed into Apple Music.

Networking

Note

When negotiating a TLS/SSL connection with Diffie-Hellman key exchange, iOS 9 requires a 1024-bit group or larger. These connections include:

  • Secure Web (HTTPS)

  • Enterprise Wi-Fi (802.1X)

  • Secure e-mail (IMAP, POP, SMTP)

  • Printing servers (IPPS)

Photo Booth

Fixed in Beta 5

Photos taken with Photo Booth are not saved.

ReplayKit

Known Issue

Playing a video while ReplayKit recording is ON will stop ongoing recording session and video will fail to play.

Safari

Fixed in Beta 5

Fixed a bug where calling reloadContentBlockerWithIdentifier:completionHandler: returned an error when running on a physical device.

Notes

  • When Done is tapped in a SFSafariViewController, it is automatically dismissed. You no longer need to dismiss it in the delegate method safariViewControllerDidFinish:.

  • “Find on Page” is now available both from the share sheet as well as in the Completions List.

  • Request Desktop Site has moved; it’s now in the Share sheet instead of Favorites.

  • Web Browser–to–Native App Handoff does not work with your app if the apple-app-site-association file isn’t correctly formatted and signed. For more information, see Handoff Programming Guide and Shared Web Credentials Reference.

Secure Transport

Note

  • DHE_RSA ciphersuites are now disabled by default in Secure Transport for TLS clients. This may cause failure to connect to TLS servers that only support DHE_RSA cipher suites. Applications that explicitly enable ciphersuites usingSSLSetEnabledCiphers() are not affected and will still use DHE_RSA ciphersuites if explicetely enabled.

Siri

Fixed in Beta 5

  • Siri cannot change Settings options.

  • Siri Eyes Free may not work.

  • You are unable to create, view, or edit notes using Siri.

Spotlight

Fixed in Beta 5

After upgrading to this beta, some contacts are not searchable in Spotlight.

UIKit

Notes

  • If initialized with a nil nibName value, UIViewController.nibName has always looked for a nib with a similar name as the view controller’s class, and defaulted to that value if loadView is not overridden.

    Prior to iOS 9, subclasses of UIViewController that were written in Swift would require that their corresponding nib file name include the module prefix.

    To improve flexibility in the event of refactoring, you can omit the module name from the nib file name in code that runs in iOS 9 beta 4 and later. UIViewController.nibName still prefers a name that contains the module prefix, but falls back to an unqualified name if a nib with the fully-qualified name is not found.

  • In iOS 9, when layoutIfNeeded is sent to a view and all of the following conditions are satisfied (which is not common), we apply fitting-size constraints (width/height = 0 at UILayoutPriorityFittingSizeLevel) instead of required size constraints (width/height required to match current size):

    1. The receiver is not yet in the subtree of a view that hosts a layout engine, such as window, view controller view (unless you have set translatesAutoresizingMaskIntoConstraints to NO on that view—or created constraints that have one item in its subtree and one item outside it), table view cell content view, and so on.

    2. The final ancestor (that is, top-level view) of the receiver has translatesAutoresizingMaskIntoConstraints set to NO.

    3. The top-level view has a subview that is not a UIViewController-owned layout guide that also has translatesAutoresizingMaskIntoConstraints set to NO.

    Under condition 1, we create a temporary layout engine from the top-level view and add all the constraints from the subtree to it. The problem is that we need to add some constraints that make the size of the top-level view unambiguous in the layout engine. The old behavior (prior to iOS 9) was that we would add constraints to restrict the size of the top-level view to its current bounds for any situation under condition 1. This really doesn’t make sense when you add conditions 2 and 3 and can result in unsatisfiable-constraints logging and broken layout.

    So in iOS 9, for this special case only, we use fitting-size constraints instead.

    This means that if you are sending layoutIfNeeded to a view under these conditions in iOS 9, you must be sure that either you have sufficient constraints to establish a size for the top-level view (which usually, though not always, is the receiver) or you must add temporary size constraints to the top-level view of layout size you desire before sending layoutIfNeeded, and remove them afterward.

  • For apps linked on iOS 9 or later, UITextView will now always correctly constrict its NSTextContainer to the fit inside the view when scrolling is disabled. Overflowing lines that lie outside of an NSTextContainer, even partially, are not rendered.

    In previous iOS releases, the NSTextContainer sometimes was not constricted in size. This meant that logically overflowing lines were erroneously rendered. If you are seeing previously rendered lines at the end of your text view no longer rendered after linking your app against iOS 9, this behavior change is the likely cause. You can remedy this by making your UITextView larger, or perhaps by adjusting the bottom value of the text view's textContainerInset property.

  • There is a redesigned UI for printing that includes a print preview (presented from UIPrintInteractionController or UIActivityViewController). For apps that provide printing items or use only built-in UIPrintFormatter objects (such asUISimpleTextPrintFormatterUIMarkupTextPrintFormatterUIWebViewPrintFormatter, or the UIViewPrintFormatter of any system-provided view), nothing additional is needed for the print preview to display.

    Apps that subclass UIPrintPageRenderer or UIPrintFormatter to draw content for printing must be built with the iOS 9 SDK for the preview to display. The behavior of UIPrintPageRenderer has been updated to call drawPageAtIndex:inRect:multiple times with potentially different page sizes and margins. Various methods on UIPrintPageRenderer may be called from a non-main thread, but never from multiple threads concurrently.

  • UIPickerView and UIDatePicker are now resizable and adaptive—previously, these views would enforce a default size even if you attempted to resize them. These views also now default to a width of 320 points on all devices, instead of to the device width on iPhone.

    Interfaces that rely on the old enforcement of the default size will likely look wrong when compiled for iOS 9. Any problems encountered can be resolved by fully constraining or sizing picker views to the desired size instead of relying on implicit behavior.

Known Issues

  • Instances of UIViewController classes that are defined in the UIKit library and are created with a nil nibBundle attempt to find their nib inside the UIKit framework instead of the app's main bundle.

    Workaround: Pass [NSBundle mainBundle] for the nibBundle argument instead of nil.

  • Apps linked to versions of iOS earlier than iOS 8 may display incorrectly. Symptoms include cropping and displaying only in a small section of the screen.

Volume Purchase Program

Fixed in Beta 5

Apps that are distributed through VPP and are licensed to a device won't launch.

Watch App

Known Issue

Pairing iOS 9 beta 3 or 4 with watchOS 2 beta 1 or 2 requires you to sign out of your AppleID in Messages prior to pairing and to skip iCloud sign-in during pairing. Pairing with watchOS 2 beta 3 and watchOS 1 is not impacted.

Webkit

Note

The if-domain and unless-domain value strings only match the exact domain. To match the domain and any subdomains, begin the string with the asterisk character (*).



'iOS' 카테고리의 다른 글

애플워치2 베타5 업데이트 방법  (0) 2015.08.12
iOS 9 Beta 5 Release Notes  (0) 2015.08.07
애플 watchOS 2 릴리즈 노트 베타4  (0) 2015.08.03
iOS 9 Beta 3 Release Notes  (0) 2015.07.10

이 업데이트에서는 Apple Music을 새로 선보입니다. Apple Music은 혁신적인 음악 서비스를 제공하고 글로벌 라디오를 24시간 들을 수 있으며 좋아하는 아티스트를 팔로우할 수 있는 Connect 기능을 포함합니다. 이 모든 서비스는 새롭게 디자인된 음악 App에서 즐길 수 있습니다. 그 외에 iOS 8.4는 iBooks의 향상과 오류 수정을 포함합니다.
Apple Music
Apple Music 구독 멤버가 되면 Apple Music 카탈로그에 있는 수백만 곡의 노래를 즐길 수 있고 오프라인 재생목록으로 보관하여 나중에 오프라인에서도 들을 수 있습니다.
추천 음악: Apple Music 멤버는 음악 전문가가 엄선한 재생목록 및 추천 앨범을 볼 수 있습니다.
새로운 음악: Apple Music 멤버에게는 최신 및 최고의 음악을 에디터가 직접 선별하여 제공합니다.
라디오: Beats 1에서 음악과 인터뷰, 독점적인 라디오 쇼를 청취할 수 있습니다. 또한 에디터가 만든 라디오 스테이션을 재생할 수도 있고 좋아하는 아티스트 또는 노래로 직접 스테이션을 만들 수도 있습니다.
Connect: 팔로우하는 아티스트의 생각, 사진, 음악 및 비디오를 공유하고 대화에도 참여할 수 있습니다.
나의 음악: iTunes 구입 항목, Apple Music의 노래, 재생목록을 모두 한 곳에서 재생하고 즐깁니다.
최근 추가된 항목, 미니 플레이어, 다음에 재생할 목록 등 더 많은 기능을 추가한 전면 새로 디자인된 음악 플레이어입니다.
iTunes Store: 좋아하는 음악을 구입할 수 있는 최적의 장소입니다. 한 번에 한 곡씩 또는 앨범 전체를 구입할 수 있습니다.
이용 가능한 서비스 및 기능은 국가에 따라 다를 수 있습니다.
iBooks 향상 및 오류 수정
iBooks 내에서 오디오북을 검색, 청취 및 다운로드할 수 있습니다.
지금 재생 중 기능이 오디오북을 위해 특별히 새로 디자인되었습니다.
iPad는 물론 iPhone에서도 이제 iBooks용으로 만들어진 도서를 사용할 수 있습니다.
시리즈 도서를 보관함에서 바로 검색하고 미리 주문할 수 있습니다.
iBooks Author로 만들어진 도서에서 Widget, 용어집 및 탐색 기능의 손쉬운 사용이 향상되었습니다.
기본 설정된 중국어 서체가 새로워졌습니다.
보관함에서 자동 야간 테마 끄기 설정이 새로워졌습니다.
구입 항목 가리기의 오작동 원인을 수정했습니다.
iCloud에서 책이 다운로드되지 않던 문제를 해결했습니다.
기타 향상 및 오류 수정
특정한 유니코드 문자를 받으면 기기가 재시동되던 문제 해결
GPS 액세서리가 위치 데이터를 제공할 수 없던 문제 수정
삭제된 Apple Watch App이 다시 설치되던 문제 해결
이 업데이트의 보안 콘텐츠와 관련된 자세한 정보는 다음 웹 사이트를 참조하십시오.
http://support.apple.com/kb/HT1222?viewlocale=ko_KR

'iOS' 카테고리의 다른 글

iOS 9 Beta 3 Release Notes  (0) 2015.07.10
iOS 8.4 업데이트  (0) 2015.07.01
iOS 9 릴리즈 노트 구글 번역본  (0) 2015.06.09
아이폰 iOS 8.3 업데이트 내용 (한글)  (0) 2015.04.09

아이폰 OS SDK의 출시는 아이폰 OS 9 베타 노트

내용 :

소개

아이폰 OS SDK 9.0은 아이폰 OS 앱 개발에 대한 지원을 제공합니다. 그것은 이러한 도구는 엑스 코드 IDE 및 많은 다른 사람의 사이에서 악기 분석 도구를 포함 아이폰 OS 및 OS X 용 응용 프로그램을 만들기위한 엑스 코드 도구, 컴파일러 및 프레임 워크의 완전한 세트와 함께 제공된다.

이 소프트웨어를 사용하면 (아이폰 OS는 또한 9.0 OS X의 v10.10.3를 실행하는 맥 컴퓨터가 필요합니다 아이폰 OS 9. 아이폰 OS SDK를 지원 포함 된 시뮬레이터를 사용하여 응용 프로그램을 테스트 할 수 있습니다 9. 실행을 터치 요세미티를 iPhone, iPad 또는 iPod 용 응용 프로그램을 개발할 수 있습니다 ) 이상.

아이폰 OS의 버전은 애플 개발자 프로그램에 등록 된 장치 설치를위한 것입니다. 사용할 수없는 상태로 장치를 넣을 수있는 권한이없는 방식으로 아이폰 OS의 버전을 설치하려고.

자세한 정보 및 추가 지원 리소스에 대한 방문 http://developer.apple.com/programs/ios/을 .

버그보고

문제는 언급하지 않는 사항 및 문제점에게 알려진 부분을, 애플 개발자 웹 사이트를 통해 버그를 제출하시기 바랍니다 ( https://developer.apple.com/bug-reporting/ios/ ). 또한, 당신은이 문제를 논의 할 수 있으며, 애플 개발자 포럼에서 아이폰 OS SDK 9.0 : http://devforums.apple.com . 개발자를위한 아이 클라우드에 대한 자세한 정보를 얻으려면,로 이동 http://developer.apple.com/icloud .

참고 사항 및 알려진 문제

다음과 같은 문제가 코드를 개발하는 아이폰 OS 9.0 SDK를 사용하여 관련이 있습니다.

AirPlay를

알려진 문제

애플 TV와 AirPlay를 연결 문제.

해결 방법 :

  • 애플 TV와 발신자 장치가 동일한 네트워크에 있지 않은 경우 동일한 네트워크에 다시 시도하는 동안, 한 번 AirPlay를 연결합니다.

  • 애플 TV와 발신자 장치 모두를 재부팅 한 후 다시 시도하십시오.

앱 스토어

알려진 문제

사용자가 두 번 첫 번째 인 - 앱 구매에 자격 증명을 입력하라는 메시지가 표시 될 수 있습니다.

애플 ID

알려진 문제

  • iForgot 링크가 간헐적으로 작동 할 수 있습니다.

    해결 방법 : 다시 시도하십시오.

  • 당신이 appleid.apple.com에 기본 이메일 주소를 변경하는 경우, 당신은 (나의 iPhone 찾기에서 로그 아웃 포함) 장치를 인증 할 수 없습니다.

    해결 방법 : 먼저, 다시 appleid.apple.com에서 이전 이메일에 이메일을 변경합니다. 그런 다음 로그 아웃 및 장치에에 백업합니다.

애플 유료

알려진 문제

당신이 요청하는 경우 애플 유료 시트를 제공 할 수 PKAddressFieldName을 하여 원하는 배송 주소의 필드.

해결 방법 : 사용 PKAddressFieldAll는 당신이 배송 주소 필요하거나 필요하지 않은 경우 PKAddressFieldName을 .

AVFoundation

노트

  • AVQueuePlayer는 이제 큐에 파일 기반 미디어 및 HTTP 라이브 스트리밍 미디어의 혼합물을 지원합니다. 이에 앞서, 당신은 큐의 모든 항목이 같은 유형이라고 확인했다.

  • 아이폰 OS 9 이상에 링크 앱에 대한 미디어 중단 동작 AV는 (큐) 플레이어가 변경되었습니다.

    아이폰 OS 9하기 전에, 애플리케이션은 관련 또는 추가하여 다른 미디어 재생 클라이언트를 중단 할 수 AVPlayerItem을 에 AVPlayer 또는 시간 또는 현재의 날짜 수정하여 AVPlayerItem를 (사용seekToTime을 : 나 : seekToDate 방법). 아이폰 OS 9시에서, 이러한 작업은 중단 AVPlayer의 오브젝트의 재생 속도를 통해 0이 아닌 값으로 변경되는 레이트 속성 또는 재생 방법.

  • 사진 재생시 사진이 중지 될 수 있습니다 및 사용시 이미지 버튼의 그림은 사라질 수 AVPlayerViewController을 비디오 재생과 기본 교체 AVPlayer를 사용하여 객체의 현재 항목replaceCurrentItemWithPlayerItem을 : .

  • AVPictureInPictureController의 방법 cancelPictureInPicture는 사용되지 않습니다.

블루투스

알려진 문제

수신 휴대 전화 오디오 특정 블루투스 헤드셋 행되지 않을 수도 있습니다.

해결책 : 멀리 블루투스 헤드셋에서 오디오를 라우팅 (예를 들어, 전화 스피커) 및 백.

CarPlay

알려진 문제

당신은 여전히​​ CarPlay 사용 헤드 유닛에 부착 된 장치를 사용하여 차량을 끄면 장치가 완전히 응답하지 및 하드 재부팅해야합니다.

CBCentralManager

알려진 문제

사용 앱 CBCentralManager (특히 retrievePeripherals : 및 retrieveConnectedPeripherals을 ). 발사 또는 액세서리를 페어링에 충돌합니다은 CBCentralManager은 아이폰 OS 7.0을 사용합니다 및 아이폰 OS 9.0에서 제거되었습니다.

연락처

알려진 문제

가족과 함께 나누기

알려진 문제

  • 로드에서 iCloud를 설정의 패밀리 섹션 비밀번호를 방지 변경.

    해결 방법 : 아이 클라우드에서 로그 아웃 한 다음 암호 변경 이후에 백업합니다.

  • 가족 인라인을 추가하면 실패합니다.

    해결 방법 : 사용은 가족 구성원을 추가 초대합니다.

  • 도청 때 응답하지 않는 알림을 구입하기 위해 문의하십시오.

HealthKit

알려진 문제

건강 데이터베이스가 베타로 업그레이드하는 동안 삭제하는 드문 경우에, 그것은이 가능합니다.

해결 방법 : 이 베타를 설치하기 암호화 된 아이튠즈 백업이 이전하기 위해선, 건강 데이터베이스가 손실되지 않습니다 있는지 확인하십시오.

업그레이드 프로세스의 기간 동안 잠금 해제 장치를 유지하는 데이터베이스의 위험이 파괴되는 것을 줄일 수 있지만, 그것은이 문제가 발생하는 경우 데이터베이스를 복구 할 수 있도록 백업을 만드는 것이 좋습니다.

HomeKit

알려진 문제

  • HomeKit에 여러 개의 통신 경로를 지원 액세서리 중복 나타날 수 있습니다.

  • 액세서리에서 제거되지 않을 수 있습니다 HMAccessoryBrowser의 집에 추가 된 후 객체입니다.

  • HMLocationEvent는 현재 만 지원 CLCircularRegion을 .

  • 아이폰 OS 9는 현재 아이폰 OS 8에서 집으로 초대를 허용하지 않습니다.

  • 위치 기반 이벤트 트리거는 시뮬레이터에서 작동하지 않습니다.

아이 클라우드 백업

알려진 문제

  • 아이폰 OS 9에서 생성 된 백업에서 복원 아이폰 OS 8 또는 이전 버전에서 생성 된 백업에서 복원하는 것보다 느립니다.

    해결 방법 : 백업 및 복원 iTunes를 사용합니다.

  • 당신은이 성공적으로 백업 한 경우 장치를 제안 잘못된 "아이 클라우드 백업"경고가 백업되지 않은 볼 수 있습니다.

    해결 방법 : , 장치가 마지막 백업 시점을 결정 설정> iCloud에> 백업을하고, "마지막 백업"타임 스탬프를 볼 수 있습니다.

  • 아이 클라우드 백업은 잘못> 설정> iCloud를> 백업에 0 바이트의 백업 크기를보고 스토리지> 스토리지> 장치를 관리합니다.

  • 만약 당신이 두 요소 인증은 인증 코드를 전송 박히 수있는 아이 클라우드 백업에서 복원하는 동안 당신의 iTunes 계정에 로그인, 활성화.

    해결 방법 : 아이 클라우드 백업에서 복원하는 동안 사용자의 iTunes 계정에 로그인하지 마십시오.

  • 드문 경우에, 아이 클라우드 백업이 진행을,하지만 실패합니다.

    해결 방법 : 백업 및 복원 iTunes를 사용합니다.

아이 클라우드 드라이브

알려진 문제

검색 결과에 아이 클라우드 드라이브 문서를 도청하는 것은 아무것도하지 않습니다.

키보드

알려진 문제

  • 타사 키보드는 검색 결과에서 작동하지 않습니다.

  • 타사 키보드는 애플 리케이션에서 활성 키보드의 목록에서 제거받을 수 있습니다.

    해결 방법 : 키보드 설정에서 다시 키보드를 추가합니다.

키 체인

알려진 문제

  • 아이 클라우드 체인 있도록 버디 사용시 SMS가 동일한 디바이스에 수신되는 경우, SMS 인증 코드는 자동으로 입력 할 수 없습니다.

    해결 방법 : 마침 설정 지원 및 설정을 사용하여 iCloud 키 체인을 가능하게한다.

  • SecKeyGeneratePair은 때때로 보안 영토 (에 저장되어있는 키 생성에 실패 할 수 있습니다 kSecAttrTokenIDSecureEnclave을 ).

  • 당신의 아이 클라우드 암호를 변경 한 후, 당신은 아이 클라우드 키 체인 재설정 프롬프트를 볼 수 있습니다.

    해결 방법 : 아이 클라우드 키 체인을 사용하도록 다시.

  • 열쇠 고리로 작성된 항목 kSecAccessControlUserPresence 액세스 제어 목록을 10 분 동안 글로벌 터치 ID 크리 덴셜을 사용한다. 아이폰이 터치 ID로 잠금이 해제되는 경우,이 항목은 터치 ID가 정보의 잠금을 해제하고 새로운 인증을 요청하지 않습니다 다시. 아이폰이 암호를 사용하여 잠금을 해제하는 경우, 항목은 터치 ID를 필요로한다.

  • SecRequestSharedWebCredential는 사용자 이름 선택기를 표시하지 않습니다.

  • 로컬 인증 setCredential는 키 체인 작업을 위해 응용 프로그램 암호를 설정하는 데 실패합니다.

  • 두 단계 인증은 신뢰할 수없는 장치에서 아이 클라우드 키 체인 또는 아이 클라우드 보안 코드를 변경 한 다음 AppleID에서 사용하고있는 경우,이 오류를 "인증 실패"를 참조하십시오.

    해결 방법 : , iCloud를 로그 아웃 계정에 다시 로그인하여 iCloud 키 체인을 사용

지도

알려진 문제

아이폰은 애플의 시계에 페어링되어 아이폰 화면이 잠겨있는 경우 탐색 단계, 지침 및 표시가 제대로 업데이트되지 않습니다.

해결 방법 : 아이폰의 잠금을 해제합니다.

우편

알려진 문제

  • 메시지를 인쇄 할 때 메일이 충돌합니다.

  • 야후 메일 계정은 정기적으로 "메일을 가져올 수 없습니다."가 표시 될 수 있습니다

    해결 방법 : 당신은 경고를 해제 할 수 예상대로 야후 메일이 계속 작동합니다.

MDM

알려진 문제

AvailableOSUpdates MDM 명령은 알 수없는 명령과 자율 장치에 실패합니다. 명령은 감독 DEP-등록 된 장치에 성공합니다.

멀티 태스킹

알려진 문제

  • 앱 스위처 연속성이 베타 작동하지 않습니다. 당신이 연속성을 테스트해야하는 경우, 당신은 잠금 화면에서 테스트 할 수 있습니다.

  • 멀티 태스킹 시나리오에 표시하는 경우, 보조 응용 프로그램은 고정 해제, 고정 할 수없는, 또는 VoiceOver를 사용할 수있는 경우 크기를 조정할.

    해결 방법 : 설정에서 비활성화 VoiceOver는> 일반> 손쉬운 사용이 멀티 태스킹 제스처 기능을 다시 시작합니다.

  • 아이 패드 에어 시뮬레이터 멀티 태스킹 기능 (오버레이 및 픽처 인 픽처 만)을 제한하고있다. 이 베타 버전, 아이 패드 에어와 아이 패드 에어 2 시뮬레이터 차이가 없다.

음악

주의

사용자가 헤드폰을 연결하거나 자신의 차에 블루투스 또는 CarPlay에 연결하면, 자신이 좋아하는 음악 앱은 잠금 화면이나 자동차 디스플레이에 표시됩니다.

앱이 자격이 있으려면, 지금은 시작에 재생에 게시하고 일관되게 지금 재생 상태를 유지해야합니다. 출시에 따라 일반적인 방법은 응용 프로그램이 마지막으로 종료되었을 때의 트랙을 계속 재생하는 것입니다.

노트

알려진 문제

아이폰 OS 9 베타 1에서 노트를 업그레이드 한 후, 메모는 Windows에서 iTunes를 사용하여 동기화되지 않습니다.

사진

알려진 문제

아이 클라우드 백업에서 복원 한 후, 아이 클라우드 사진 라이브러리에 저장되지 않은 사진 썸네일을 표시하지 못한다.

해결 방법 : 영향을 사진을 선택하고 편집 되돌리기 다음을 선택합니다.

응용 프로그램 확장

알려진 문제

작업을 디버깅하거나 확장을 공유하는 확장이 누락 될 수 있습니다 UIActivityViewController의 객체입니다.

해결 방법 : 더 많은 목록으로 이동하여 다시 확장을 보여주기 위해 돌아갑니다.

팟 캐스트

알려진 문제

  • 검색 페이지는 항상로드하거나 결과를 제공하지 않습니다.

  • 구독 버튼은 사용자의 터치에 반응하는 속도가 느립니다.

  • 멀티 태스킹을 사용할 때, 팟 캐스트 앱 충돌은 50 % 감소하고 66 %로 증가 할 때.

원정 여행

노트

  • "페이지에서 찾기"공유 시트에서뿐만 아니라 달성 목록에 모두 사용할 수 있습니다.

  • 요청 데스크톱 사이트는 이동했습니다. 그것은 공유 시트 대신 즐겨 찾기에 지금입니다.

  • 애플 앱 - 사이트 연결 파일이 올바른 형식과 서명되지 않은 경우 웹 브라우저에 네이티브 앱 핸드 오프는 사용자의 응용 프로그램과 함께 작동하지 않습니다. 참조하십시오 핸드 오프 프로그래밍 가이드및 공유 웹 자격 증명 참조 자세한 내용을.

알려진 문제

  • 새로운 API는 응용 프로그램 번들 내에서 파일을로드 작동하지 않습니다 현재 로컬 파일을로드합니다.

  • 잘못된 JSONs와 내용 차단제는로드되지 않습니다.

수색

알려진 문제

  • 검색 결과에 메일 메시지,지도 즐겨 찾기, 주, 또는 메시지를 도청하는 일부 장치에 응용 프로그램을 열지 않습니다.

  • 썸네일로 코어 스포트 라이트 항목을 인덱싱하면 검색 결과의 썸네일이나 설명을 표시하지 않습니다.

  • 모든 NSUserActivity 객체는 색인 및 검색에 (검색 표시 장치뿐 아니라)을 표시하자.

시리

알려진 문제

  • 시리의 아이 패드에 제안, 전화를 시도, 메시지, 또는 페이스 타임에서 여러 주소와 연락처는 충돌 스프링이 발생합니다.

설정

알려진 문제

  • 셀룰러 데이터 페이지는 SIM 카드를 교환 한 후 비어있을 수 있습니다.

  • > 아이 클라우드> AppleID 설정을 탭하면 처음 몇 번 응답하지 않을 수 있습니다.

    해결 방법 : 다시 시도하십시오. 그것은 결국 작동합니다.

  • 타사 응용 프로그램 설정은 때때로 시뮬레이터에 표시되지 않습니다.

설정 지원

알려진 문제

아이 클라우드 이용 약관 창에 동의하지 버튼을 선택하면 진행 할 수 없습니다.

은 UIKit

노트

  • (에서 제시 인쇄 미리보기가 포함 인쇄를 위해 새롭게 디자인 된 UI가 UIPrintInteractionController 또는 UIActivityViewController은 ). 인쇄 항목을 제공하거나 만 내장에 사용되는 응용 프로그램에 대한 UIPrintFormatter의 객체 ( UISimpleTextPrintFormatter , UIMarkupTextPrintFormatter , UIWebViewPrintFormatter , 또는 UIViewPrintFormatter 인쇄 미리보기를 표시하는 어떤 시스템이 제공하는보기), 추가 아무것도 필요하지 않습니다.

    서브 클래스 애플리케이션 UIPrintPageRenderer 또는 UIPrintFormatter는 인쇄 내용이 미리보기가 표시 할 아이폰 OS 9 SDK와 함께 구축해야합니다립니다. 의 동작 UIPrintPageRenderer는전화를 업데이트되었습니다 inRect : drawPageAtIndex을 잠재적으로 다른 페이지 크기와 여백과 여러 번. 에 다양한 방법 UIPrintPageRenderer는 하지만 결코 여러 스레드에서 동시에, 비 메인 쓰레드에서 호출 할 수있다.

  • UIPickerView 및 UIDatePicker은 지금 크기 조정 및 적응이다 - 이전에, 그들은 기본 크기를 적용 할 것입니다 당신이 그들을 크기를 조정하려고해도. 이러한 뷰는 지금 대신 아이폰의 장치 폭, 모든 장치에서 320 점의 폭을 기본값으로.

    완전히 구속 또는 크기 선택기보기를 원하는 크기로 대신 암시 적 행동에 의존하여 아이폰 OS 9를 위해 발생하는 모든 문제가 해결 될 수 컴파일 할 때 기본 크기의 이전 시행에 의존하는 인터페이스 가능성이 잘못 볼 것이다.

알려진 문제

UIModalPresentationPopover의 스타일은 업데이트하지 않습니다 barButtonItem의 창 크기를 조정할 때 앵커의 위치를.

VPN

알려진 문제

  • 당신이 개발자 디스크 이미지 패키지가 설치되어있는 경우, AlwaysOn에 VPN 터널이 설정되지 않습니다.

  • 셀룰러와 와이파이 터널가있는 경우, 가끔 휴대 터널 대신 와이파이 터널의 기본 경로가 될 것이다.

  • 때때로하지가 제기 즉시 철거되는 터널로 연결 이벤트가 처리되지 않는 상 / 하, 최대 인터페이스.


'iOS' 카테고리의 다른 글

iOS 8.4 업데이트  (0) 2015.07.01
iOS 9 릴리즈 노트 구글 번역본  (0) 2015.06.09
아이폰 iOS 8.3 업데이트 내용 (한글)  (0) 2015.04.09
iOS 8.3 Beta 2 release notes  (0) 2015.02.24

이 릴리즈는 향상된 성능, 오류 수정 및 새로 디자인된 이모티콘 키보드를 포함합니다. 변경된 사항은 다음과 같습니다.

향상된 성능:

  • App 실행
  • App 반응성
  • 메시지
  • Wi-Fi
  • 제어 센터
  • Safari 탭
  • 타사 키보드
  • 키보드 단축키
  • 중국어(간체) 키보드

Wi-Fi 및 Bluetooth 수정사항

  • 로그인 자격 증명을 계속 요청받던 문제 수정
  • 일부 장비에서 간헐적으로 Wi-Fi 네트워크 연결이 해제되던 문제 해결
  • 핸즈프리 전화 통화가 연결 해제되던 문제 수정
  • 일부 Bluetooth 스피커에서 오디오가 재생되지 않던 문제 수정

방향 및 회전 수정사항

  • 때때로 가로 화면 방향으로 회전한 후 세로 화면 방향으로 다시 회전할 수 없던 문제 해결
  • 장비를 세로 화면 방향 및 가로 화면 방향으로 회전할 때 발생하는 성능 및 안정성 문제 개선
  • 주머니에서 iPhone 6 Plus를 꺼내면 장비의 화면 방향이 거꾸로 되던 문제 수정
  • 멀티태스킹으로 App을 전환한 후 가끔 App이 올바른 화면 방향으로 회전되지 않던 문제 해결

메시지 수정사항

  • 그룹 메시지가 때때로 분리되던 문제 해결
  • 개별 메시지를 전달하거나 삭제하는 기능이 때때로 사라지던 문제 수정
  • 메시지에서 사진을 찍을 때 때때로 미리보기가 나타나지 않는 문제 해결
  • 메시지 App에서 직접 정크 메시지로 보고할 수 있는 기능 추가
  • 사용자의 연락처에 없는 사람이 보낸 iMessages를 필터링할 수 있는 기능 추가

가족 공유 수정사항

  • 가족 구성원의 장비에서 특정 App이 실행되지 않거나 업데이트되지 않는 오류 수정
  • 가족 구성원이 특정 무료 App을 다운로드할 수 없던 오류 수정
  • 구입 요청 알림에 대한 신뢰성 향상

CarPlay 수정사항

  • 지도가 검은색 화면이 되던 문제 수정
  • UI가 올바르지 않게 회전되던 문제 수정
  • CarPlay 화면에 나타나지 말아야 할 키보드가 나타나던 문제 수정

기업용 수정사항

  • 기업용 App 설치 및 업데이트 신뢰성 향상
  • IBM Notes에서 생성된 캘린더 이벤트의 시간대 수정
  • 재시동 후 Web Clip 아이콘이 일반 아이콘이 되던 문제 수정
  • 웹 프록시 암호 저장에 대한 신뢰성 향상
  • 외부 답장에 대해 Exchange 부재 중 메시지를 이제 개별적으로 편집 가능
  • 일시적인 연결 문제에 대해 Exchange 계정 복구 향상
  • VPN 및 웹 프록시 솔루션 호환성 향상
  • 공용 Wi-Fi 네트워크에 연결할 때와 같이 Safari 웹 시트에 로그인할 때 물리적 키보드 사용 허용
  • 긴 메모가 있는 Exchange 회의가 잘리던 문제 수정

손쉬운 사용 수정사항

  • Safari에서 뒤로 버튼을 사용할 때 VoiceOver 제스처가 응답하지 않던 문제 수정
  • 임시 저장 Mail 메시지에서 VoiceOver 초점의 신뢰성이 떨어지던 문제 수정
  • 점자 화면 입력을 사용하여 웹 페이지 양식에 텍스트를 입력할 수 없던 문제 수정
  • 점자 디스플레이에서 빠른 탐색을 토글할 때 빠른 탐색이 꺼져있다고 나오던 문제 수정
  • VoiceOver가 활성화되어 있을 때 App 아이콘이 홈 화면에서 움직이지 않던 문제 수정
  • 일시 정지 후 화면 말하기가 다시 시작되지 않던 화면 말하기 문제 수정

기타 개선사항 및 오류 수정사항

  • 300개 이상의 새로운 이모티콘이 있는 새로 디자인된 이모티콘 키보드
  • iCloud 사진 보관함이 OS X 10.10.3의 새로운 사진 App과 동작하도록 최적화되었으며 정식 출시됨
  • 지도에서 턴 바이 턴 내비게이션의 거리 이름을 말하는 발음 향상
  • Baum VarioUltra 20 및 VarioUltra 40 점자 디스플레이 지원 포함
  • 투명도 줄이기가 켜져 있을 때 Spotlight 결과 표시 향상
  • iPhone 6 Plus 가로 화면 방향 키보드의 이탤릭체 및 밑줄체 포맷 옵션 추가
  • Apple Pay에 사용하는 배송 및 청구 주소 제거 기능 추가
  • Siri가 지원되는 언어 및 국가 추가: 영어(인도, 뉴질랜드), 덴마크어(덴마크), 네덜란드어(네덜란드), 포르투갈어(브라질), 러시아어(러시아), 스웨덴어(스웨덴), 태국어(태국), 터키어(터키)
  • 받아쓰기 언어 추가: 아랍어(사우디 아라비아, 아랍 에미리트 연합국) 및 히브리어(이스라엘)
  • 전화, Mail, Bluetooth 연결, 사진, Safari 탭, 설정, 날씨 및 음악의 Genius 재생목록의 안정성 향상
  • 특정 장비에서 밀어서 잠금 해제가 동작하지 않던 문제 해결
  • 가끔 잠금 화면에서 쓸어넘겨 전화 통화를 받을 수 없던 문제 해결
  • Safari PDF에서 링크가 열리지 않던 문제 해결
  • Safari 설정에서 방문 기록 및 웹 사이트 데이터 지우기를 선택해도 모든 데이터가 지워지지 않던 문제 수정
  • 'FYI'가 자동 수정되던 문제 수정
  • 빠른 답장에 예상 단어가 나타나지 않던 문제 해결
  • 지도가 하이브리드 모드에서 야간 모드로 바뀌지 않던 문제 수정
  • FaceTime URL을 사용하여 브라우저 또는 타사 App에서 FaceTime 통화를 시작할 수 없던 문제 해결
  • 때때로 사진이 Windows의 디지털 카메라 이미지 폴더에 제대로 보내지지 않던 문제 수정
  • iTunes에서 때때로 iPad 백업이 완료되지 않던 문제 수정
  • Wi-Fi에서 셀룰러 네트워크로 전환할 때 Podcast 다운로드가 멈추던 문제 수정
  • 잠금 화면에서 타이머의 남은 시간이 00:00으로 잘못 표시되던 문제 수정
  • 때때로 통화 음량이 조절되지 않던 문제 수정
  • 상태 막대가 때때로 나타나지 말아야 할 때 나타나던 문제 수정

이 업데이트의 보안 콘텐츠에 관한 자세한 정보를 보려면 다음 웹 사이트를 방문하십시오.

http://support.apple.com/kb/HT1222?viewlocale=ko_KR

'iOS' 카테고리의 다른 글

iOS 9 릴리즈 노트 구글 번역본  (0) 2015.06.09
아이폰 iOS 8.3 업데이트 내용 (한글)  (0) 2015.04.09
iOS 8.3 Beta 2 release notes  (0) 2015.02.24
iOS 8.2 beta 5 release notes  (0) 2015.02.10

iOS SDK Release Notes for iOS 8.3 Beta 2

Contents:

Introduction

iOS SDK 8.3 provides support for developing iOS apps. The SDK is packaged with a complete set of tools, compilers, and frameworks for creating apps for iOS and OS X. The 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 8. It now includes WatchKit, a framework for developing Apple Watch apps. You can test your apps using the included iOS Simulator.

iOS SDK 8.3 is included in Xcode 6.3, which requires a Mac computer running OS X v10.10 (Yosemite) 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

For issues not mentioned in the Notes and Known Issues section, please file bugs through the Apple Developer website (https://developer.apple.com/bug-reporting/ios/). Additionally, you may discuss these issues and iOS SDK 8.3 in the Apple Developer Forums: http://devforums.apple.com. To get more information about iCloud for Developers, go tohttp://developer.apple.com/icloud.

Notes and Known Issues

The following issues relate to using iOS SDK 8.3 to develop code.

App Extensions

Notes

  • App extensions need an arm64 slice to run on 64-bit devices. If you try to run the armv7 slice on a 64-bit device it won’t work.

  • Apps need to have an arm64 slice if the bundle contains a framework that both the app and the app extension link against.

CarPlay

Fixed in Beta 2

The dialog that appears when connecting an iPhone to a CarPlay-compatible car is not functional.

WatchKit

Known Issue

Creating an animated image using the UIImage method animatedImageWithImages:duration: and then playing the animation using startAnimating ignores the duration and plays back as fast as possible.

Workaround: Use startAnimatingWithImagesInRange:duration:repeatCount: instead.

LTE Voice

Known Issue

LTE Voice does not work properly with Verizon.

Workaround: If you are using Verizon, please set LTE to Data Only for this seed.


'iOS' 카테고리의 다른 글

아이폰 iOS 8.3 업데이트 내용 (한글)  (0) 2015.04.09
iOS 8.3 Beta 2 release notes  (0) 2015.02.24
iOS 8.2 beta 5 release notes  (0) 2015.02.10
iOS SDK Release Notes for iOS 8.2 Beta 3  (0) 2014.12.19

iOS SDK Release Notes for iOS 8.2 Beta 3

Contents:

Introduction

iOS SDK 8.2 provides support for developing iOS apps. The SDK is packaged with a complete set of tools, compilers, and frameworks for creating apps for iOS and OS X. The 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 8. It now includes WatchKit, a framework for developing Apple Watch apps. You can test your apps using the included iOS Simulator.

iOS SDK 8.2 requires a Mac computer running OS X v10.9.3 (Mavericks) 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

For issues not mentioned in the Notes and Known Issues section, please file bugs through the Apple Developer website (https://developer.apple.com/bug-reporting/ios/). Additionally, you may discuss these issues and iOS SDK 8.2 in the Apple Developer Forums: http://devforums.apple.com. To get more information about iCloud for Developers, go tohttp://developer.apple.com/icloud.

Notes and Known Issues

The following issues relate to using iOS SDK 8.2 to develop code.

CloudKit

Note

A single CKAsset instance can no longer be set as a value on multiple CKRecords.

Document Providers

Notes

  • Your app needs the iCloud entitlement to be able to be used as a document provider.

  • The com.apple.developer.icloud-container-identifiers entitlement is required.

Known Issues

  • After rotating the document picker to landscape, the status bar is hidden.

  • Upon bringing up the document picker in landscape, the containing view may be shifted beneath the navigation bar.

App Extensions

Notes

  • App extensions need an arm64 slice to run on 64-bit devices. If you try to run the armv7 slice on a 64-bit device it won’t work.

  • Apps need to have an arm64 slice if the bundle contains a framework that both the app and the app extension link against.

File System

Note

The file system layout of app containers has changed on disk. Rather than relying on hard-coded directory structure, use the NSSearchPathForDirectoriesInDomains function or theURLForDirectory:inDomain:appropriateForURL:create:error: method of the NSFileManager class. See Accessing Files and Directories in File System Programming Guide.

Fonts

Note

The Thai system font has increased in size to improve readability. This will cause clipping in many places in your UI if you don’t take appropriate action:

  1. Use UILabel as much as possible. If you use Interface Builder, make sure that Clip Subviews is not checked. UIKit will grow the clipping region as necessary to not clip text.

  2. Use Dynamic Type. This will ensure that you do not have overlapping glyphs in multiline labels or text fields.

If you can’t do 1 and 2 because you implement your own views, you must implement measures not to clip. You can use CoreText to figure out the appropriate clipping region for a line of text by calling:

CTLineGetBoundsWithOptions(lineRef, kCTLineBoundsIncludeLanguageExtents);

To avoid overlapping glyphs in multiline text elements, adjust the line height. An additional 30% is recommended.

This measure will also help your app perform better in other languages, including Arabic, Hindi, and Vietnamese.

iCloud

Note

Mail handoff and AirDrop may stop working after changing your iCloud password at appleid.apple.com.

Workaround: Sign out and back into iCloud on the device.

iCloud Drive

Note

URLForUbiquityContainerIdentifier: might return nil when running your application in Xcode. If so, open System Preferences, navigate to iCloud > iCloud Drive, and enable Xcode.

Messages

Fixed in Beta 3

Your device may get into a state where tapping into Messages conversations can take a long time.

Notification Center

Note

The schedule and intended use of widgetPerformUpdateWithCompletionHandler: is intended as a convenient home for all data/model update logic. If implemented, the system will call at opportune times for the widget to update its state, both when Notification Center is visible, as well as in the background. An implementation is required to enable background updates. It’s expected that the widget will perform the work to update asynchronously and off the main thread as much as possible. Widgets should call the argument block when the work is complete, passing the appropriate NCUpdateResult. Widgets should NOT block returning from viewWillAppear: on the results of this operation. Instead, widgets should load cached state in viewWillAppear: in order to match the state of the view from the last viewWillDisappear:, then transition smoothly to the new data when it arrives.

NSURLSession

Note

The NSURLSessionTask class provides a new “priority” property with three associated constants: NSURLSessionTaskPriorityDefaultNSURLSessionTaskPriorityLow, andNSURLSessionTaskPriorityHighNSURLSessionTask priorities can be used to specify how multiple requests and responses to the same host should be prioritized. Note that the priority is a hint and not a strict guarantee of NSURLSessionTask performance.

For complete usage details of NSURLSessionTask priorities, refer to the NSURLSession.h header file, which is provided by the Foundation framework.

Phone

Note

To activate Wi-Fi Calling functionality for T-Mobile (U.S. only), follow these steps:

  • Go to Settings > Phone > Wi-Fi Calling.

  • Toggle the Wi-Fi Calling switch to ON.

  • If the carrier does not have the user’s registered emergency address, you will be asked to add it before the feature is activated.

Photos

Notes

  • Maintain a backup of your photo library before enabling and while using iCloud Photo Library beta by:

    • Importing to your Mac using iPhoto

    • Importing to your Mac using Image Capture

  • iCloud Photo Library beta will not download photos and videos that were synced to your device from iTunes. Any photos and videos synced to your device from iTunes will be removed when you enable iCloud Photo Library beta.

  • iPhoto for iOS will not launch on iOS 8 beta. Launching Photos.app will migrate your iPhoto edits to the iOS 8 Photo Library. Make sure your iPhoto for iOS data is included in your device backup.

  • The ability to automatically optimize device space is enabled for all accounts larger than 5GB.

  • When using iCloud Family Sharing, both iCloud Photo Sharing and My Photo Stream are enabled.

Provisioning Profiles

Known Issue

If you have upgraded to the 8.2 beta from previous iOS 8 betas you may see your apps crashing due to provisioning profile issues.

Workaround:

  1. Connect the device via USB to your Mac.

  2. Launch Xcode.

  3. Choose Window > Devices.

  4. Right click on the device in left column, choose "Show Provisioning Profiles".

  5. Click on the provisioning profile in question.

  6. Press the "-" button.

  7. Continue to removing all affected profiles.

  8. Re-install the app.

UIKit

Notes

  • UILabel has a default value of YES for clipsToBounds. This differs from the normal UIView default of NO.

  • The leftLayoutGuide and rightLayoutGuide APIs have been removed. Please use the layoutMargins property instead.

WatchKit

Notes

  • The WKInterfaceMap API has changed. Specifically, setMapRect: and setCoordinateRegion: have been replaced by setVisibleMapRect: and setRegion: respectively.

  • The WKInterfaceController method initWithContext: has been deprecated. Please use awakeWithContext: instead. The designated initializer for WKInterfaceController is now init.

  • The WKInterfaceDevice API has changed. Specifically, addCachedImage:name: and addCachedImageWithData:name: now return BOOL to indicate the success or failure of adding an image to the cache. Note that these methods return NO if the cache size has reached its limit. Delete images from the cache by calling removeCachedImageWithName: orremoveAllCachedImages.

  • A page-based WatchKit app can dynamically resequence the pages at the root level using reloadRootControllersWithNames:contexts:.

  • Rows in a WKInterfaceTable now have a default appearance. This appearance can be overridden by specifying the values for background color, margin, corner radius, and height for the row in Interface Builder.

Fixed in Beta 3

  • In iOS Simulator, the Emoji button should now be visible, regardless of the selected input mode.

  • The WKInterfaceController method openParentApplication:reply: now launches the containing app in the background when the iPhone (or iOS Simulator) is unlocked or locked.

  • The WKInterfaceController method presentTextInputControllerWithSuggestions:completion: is now fully supported in iOS Simulator.

Known Issue

  • Inserting, deleting, or updating rows of a WKInterfaceTable may cause the table to temporarily size incorrectly. Scrolling your interface controller should restore the table to the proper size.

Wi-Fi Calling (T-Mobile US only)

Note

The carrier name in the status bar will show “T-Mobile Wi-Fi” when the device is able to make and receive Wi-Fi calls.


'iOS' 카테고리의 다른 글

iOS 8.2 beta 5 release notes  (0) 2015.02.10
iOS SDK Release Notes for iOS 8.2 Beta 3  (0) 2014.12.19
Xcode6 및 베타5 릴리즈노트 다운로드  (0) 2014.08.05
iOS8 베타5 SDK 릴리즈 노트  (0) 2014.08.05

여기저기 네이버검색을 해보면 키워드 광고부터 각종 블로그 카페에 널려있는 모바일 청첩장 소개 내용들 이 넘처 난다.


어떤게 가장 이쁘고 어떤게 가장 싸거나, 무료 일까


이런 여러가지 고민을 하다 보면 다시금 머리가 지끈 거려 온다...


이고민 저고민으로도 모자라 모바일 청첩장 까지 고민 고민~ 


달팽 이라는 모바일 청첩장은 메인 부터 이런 마음을 알기라도 하듯이 감성 드립으로 시작한다~


이벤트 로 경품도 주고있고~ 청첩장은 무료로 ~ 거기다 스킨은 훌륭하다~! 모바일,태블릿, 데스크탑 에서도 알아서 조정되는 레아이웃


네비게이션 연결되는 기능, 이모티콘 까지 여러 기능들을 다 챙기고 있는 데 무료라니;;


뭐먹고 사실까...


달팽 : http://dalpeng.com










달팽 : http://dalpeng.com



이전에 소개했던 달팽 이라는 모바일 청첩장 업체에서 경품 이벤트를 진행한다....

 

하필이면 아이폰 6 플러스... 이미 예판 신청하고 기다리고 있구만....

 

하지만 이벤트 기간이 3개월 이니 난 pass ~!

 

2등 상품이 아이패드 에어2 !! 이건 좀 욕심이 나니 열심히 로그인해서 응모를!


반응형 모바일 청첩장 달팽 바로 가기 : http://dalpeng.com

 

 

달팽 이벤트 바로가기

 

달팽 이벤트 바로가기

 

달팽 이벤트 바로가기

 

달팽 이벤트 바로가기

 

달팽 이벤트 바로가기

 

 

내가 시도할만한 응모권 모으기 방법은 로그인과 홍보글 날리고 받기 정도인건가

 

중요한건 오픈 초기라 그런지 이벤트 응모 건수가 별로 없다 !! 즉 경쟁자가 별로 없으니 당첨 확률도 높은 상황~!!!

 

Good luck~!!

 

제 블로그 글을 보고 응모 하신뒤 당첨되셨다면 ㅋㅋ 커피라도 한잔 쏘세요 -_-;; 굽신 굽신


달팽 이벤트 바로 가기 : http://dalpeng.com/event

 

 

 

2014/09/22 - [정보공유] - 무료 모바일 청첩장 만들기 달팽으로 - 반응형 청첩장

 

 

 

iOS 8 for Developers

iOS 8 includes over 4,000 new APIs that let you add amazing new features and capabilities to your apps. Deeper integration with iOS means you can extend the reach of your app content and functionality. And with bold new technologies for game development, you can create even more incredible, responsive, and immersive gaming experiences.

Download the beta and get started today

App Extensions

iOS 8 lets you extend select areas of the system by supplying an app extension — code that enables custom functionality within the context of a user task. iOS supports app extensions for the following extension points.

App Extensions

Share

By providing more sharing options, iOS 8 enables your app to share photos, videos, websites, and other content with social websites and other entities.

Photo Editing

Embed your filters and editing tools directly into the Photos app, so users can easily apply your effects to images and videos without having to import them into your app.

Custom Actions

Create your own custom action buttons in the Action sheet to let users watermark documents, add something to a wish list, translate text to a different language, and more.

Today

Your apps can now display widgets in the Today view of Notification Center, providing quick updates or enabling brief tasks — for example, posting updates on package deliveries, the latest surf reports, or breaking news stories.

Storage Provider

You can now provide a document storage location that can be accessed by other apps. Apps that use a document picker view controller can open files managed by the storage provider or move files into the storage provider.

Document Picker

The document picker view controller grants your users access to files outside your app’s sandbox. Documents are easily shared between apps, enabling users to edit a single document in multiple places.

Custom Keyboard

With iOS 8, you can provide custom keyboards with different input methods and layouts for users to install and use systemwide.

New Capabilities

iOS 8 introduces a huge set of APIs and services, so you can create new categories of apps and features. Here are some of the most exciting new capabilities we’re unlocking.

Touch ID

Touch ID

Your app can now use Touch ID to authenticate a user before accessing some or all content in your app. Fingerprint data is protected and never accessed by iOS or other apps.

PhotoKit

PhotoKit

PhotoKit provides new APIs for working with photo and video assets, including iCloud Photos assets, that are managed by the Photos app, so your app can edit photos directly in the Camera roll without having to import them first. Key features include a thread-safe architecture for fetching and caching thumbnails and full-sized assets, requesting changes to assets, observing changes made by other apps, and resumable editing of asset content.

Camera

Manual Camera Controls

The AVFoundation framework makes it easier than ever for users to take great photos. Your app can take direct control over the camera focus, white balance, and exposure settings. Your app can also use bracketed exposure captures to automatically capture images with different exposure settings.

HealthKit

HealthKit

HeathKit allows apps providing health and fitness services to access shared health-related information in one place. A user’s health information is stored in a centralized and secure location and the user decides which data should be shared with your app.

Your app can access any shared health-related information and can provide information about the user without you needing to implement support for specific fitness-tracking devices. Information can come from devices connected to an iOS device or manual entry by the user.
Learn more

HomeKit

HomeKit

This is a new framework for communicating with and controlling connected devices in a user’s home. Your apps can enable users to discover devices in their home and configure them, or you can create actions to control those devices. Users can group actions together and trigger them using Siri.
Learn more

CloudKit

CloudKit

Leverage the full power of iCloud and build apps with the new CloudKit framework. Now you can easily and securely store and efficiently retrieve your app data like structured data in a database or assets right from iCloud. CloudKit also enables your users to anonymously sign in to your apps with their iCloud Apple IDs without sharing their personal information.

With CloudKit, you can focus on your client-side app development and let iCloud eliminate the need to write server-side application logic. CloudKit provides authentication, private and public databases, and structured and asset storage services — all for free with very high limits.
Learn more

Handoff

Handoff

Using a simple API in Foundation, your app can participate in Handoff to let users start an activity on one device and seamlessly resume the activity on another device.

Games

Technology improvements in iOS 8 make it easier than ever to implement your game’s graphics and audio features. Take advantage of high-level frameworks for ease-of-development, or use new low-level enhancements to harness the power of the GPU.

SceneKit

SceneKit

SceneKit is a high-level 3D graphics framework that helps you create 3D animated scenes and effects in your apps. It incorporates a physics engine, a particle generator, and easy ways to script the actions of 3D objects so you can describe your scene in terms of its content — geometry, materials, lights, and cameras — then animate it by describing changes to those objects. SceneKit’s 3D physics engine enlivens your app or game by simulating gravity, forces, rigid body collisions, and joints. It’s also completely integrated with SpriteKit, so you can include SpriteKit assets in 3D games.

SpriteKit

SpriteKit

The SpriteKit framework adds new features to make it easier to create high-performance, battery-efficient 2D games. With support for custom OpenGL ES shaders and lighting, integration with SceneKit, and advanced new physics effects and animations, you can add force fields, detect collisions, and generate new lighting effects in your games. Xcode 6 also incorporates new shader and scene editors that save you time as you create your game. Create a scene’s contents, specifying which nodes appear in the scene and characteristics of those nodes, including physics effects. The scene is then serialized to a file that your game can easily load.

Metal

Metal

With extremely low-overhead access to the A7 GPU, Metal enables incredibly high performance for sophisticated graphics rendering and computational tasks. Metal eliminates many performance bottlenecks that are found in traditional graphics APIs. It’s specifically designed to exploit modern architectural considerations, such as multiprocessing and shared memory, to make it easy to parallelize the creation of GPU commands. Metal offers a streamlined API, a unified graphics and compute shading language, and Xcode-based tools.

Swift

Swift is an innovative new programming language for Cocoa and Cocoa Touch with concise yet expressive syntax. Writing Swift code within an Xcode 6 playground shows instant results, while finished apps are compiled into high-performance native machine code. The Swift language is fast, modern, safe, and interactive.
Learn more about Swift

'iOS' 카테고리의 다른 글

iOS8 달라진 점 - What's New in iOS8  (0) 2014.06.03
iOS8 for Developers  (0) 2014.06.03
iOS 7.1 beta 5 Release Notes  (0) 2014.02.05
iOS SDK 릴리즈 노트 iOS7  (0) 2013.06.11

iOS SDK Release Notes for iOS 7.0

Contents:

Introduction

iOS SDK 7.0 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.0 requires a Mac computer running OS X v10.8.3 (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.0 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.0 to develop code.

AirDrop

Notes

“Contacts Only” support requires that:

  • You are logged into iCloud.

  • The sender and receiver have each other’s Apple ID email addresses in Contacts on their devices.

Known Issues

  • “Contact Only” currently requires that you have an active Internet connection.

  • Occasionally, AirDrop will exhibit unreliability in discovery and/or data transfer to peers over Wi-Fi.

  • The App Store should support the ability to find an app capable of opening a received document based on the document’s Uniform Type Identifier (UTI). Currently, just a blank screen is displayed.

AV Foundation

Notes

AVCaptureSession now uses your app’s AVAudioSession by default.

Known Issues

AVCaptureSession is unable to produce samples to its AVCaptureAudioDataOutput when the app is running in the background.

Calendar

Known Issues

Edits made to iCloud Calendar events off-device will not push to the device.

Workaround: Update the calendar manually or trigger a fetch by modifying an event on-device.

Car Display

Known Issues

Support for Car Display will be provided once compatible systems are available.

Core Animation

Notes

When the UIViewGroupOpacity key is not present, the default value is now YES. The default was previously NO.

This means that subviews of a transparent view will first be composited onto that transparent view, then the precomposited subtree will be drawn as a whole onto the background. A NO setting results in less expensive, but also less accurate, compositing: each view in the transparent subtree is composited onto what’s underneath it, according to the parent’s opacity, in the normal painter’s algorithm order.

Core Data

Known Issues

Moving data from a local sandbox to iCloud using migratePersistentStore causes a crash. Instead, manually migrate the data store by iterating over the objects in the local data store file.

Game Center

Known Issues

  • When adding new Apple IDs to Game Center, they must be added through the Game Center app and not Settings.

  • If you launch a Game Center app while not logged into Game Center, the Game Center login sheet may be unreadable.

Game Kit

Known Issues

  • The API for sending reminders is present but unimplemented in this seed.

  • The API for loading leaderboard sets might need to be called a second time for it to succeed.

iCloud

Notes

Activation Lock, a new feature of Find My iPhone, is turned on automatically when Find My iPhone is enabled on any device running iOS 7. Activation Lock requires users to enter their Apple ID and password to turn off Find My iPhone, sign out of iCloud, erase the device, or reactivate the device after an erase. It’s important to sign out of iCloud, or choose Settings > General > Erase All Content and Settings, before transferring a device to a new user to allow them to use the device.

Known Issues

  • Signing out of an iCloud account with Find My iPhone turned on requires you to enter your Apple ID password. However, in some cases, the keyboard does not appear.

    Workaround: Double-tapping the home button will bring up the keyboard.

  • On rare occasions, users might experience difficulties setting up iCloud Keychain on some of their devices.

    Workaround: A temporary Reset iCloud Keychain button is available in iCloud Settings > Account > Account Security.

  • After users change their iCloud Security Code to Simple or Complex, they will not be able to recover their keychain items from the secure backup.

    Workaround: Change the country code field under Account Security so that the user can receive the SMS Verification Code to complete the recovery process.

  • Sometimes when creating a new Apple ID and choosing to use iCloud in Setup Assistant, iCloud will not be turned on.

    Workround: Go to Settings/iCloud and sign in with your Apple ID.

  • iCloud Keychain users who set up an additional device will receive an approval request to the other devices with iCloud Keychain turned on. The approval request will not be displayed if their screens are off and the devices are idle.

    Workaround: Wake up any peer device to accept the approval request.

  • Users signing out of iCloud by deleting their iCloud account, erasing all contents and settings, or erasing the device via Find My iPhone and signing back in will not be presented with the correct iCloud Keychain setup screens.

    Workaround: Use the seed-only iCloud Keychain Reset button.

  • Users who have a single device with iCloud Keychain on will not be presented with the correct iCloud Keychain setup screens after restoring from a backup.

    Workaround: Use the seed-only iCloud Keychain Reset button.

  • When setting up iCloud Keychain, many iCloud Security Code candidates will be rejected for being too weak.

    Workaround: Choose a 4-digit iCloud Security Code that does not have an obvious pattern.

  • Restoring your device from the same device’s iCloud backup will lose all passwords for Wi-Fi, profiles, accounts, and apps.

  • When just Calendars or just Reminders is toggled off then back on again in iCloud settings, data may not resync to the device.

    Workaround: Turn off both Calendars and Reminders, and then turn them both back on.

  • Nonpurchased ePubs and PDFs will not be restored when iCloud-restoring an iOS 7 device with a pre-iOS 7 backup. Purchased content will be restored without issue.

    Workaround: Use iTunes sync.

  • In iOS 7, Find My iPhone and Bookmarks toggles are no longer supported on secondary iCloud accounts. When you update your device with either of these options enabled on a secondary iCloud account, they will be turned off with no user notification.

    Workaround: Set up the primary iCloud account via Settings/iCloud and then enable Find My iPhone or Bookmarks.

  • Users cannot use Simple or Complex iCloud Security Codes to recover their keychain items from their secure backup on iPhone 4.

    Workaround: Use Random iCloud Security Codes to backup keychain items.

Location Services

Known Issues

  • Location Services will be off by default after updating from prior releases. This prohibits Find My iPhone from working.

    Workaround: Turn on Location Services in Settings > Privacy > Location Services.

  • In this seed, GPS-based location is nonfunctional on iPhone 4. This includes AGPS call flows used for 911 emergency services location requests. Wi-Fi and cellular-based location remain functional.

MapKit

Notes

If the calls to renderInContext on the layer backing an MKMapView are made off the main thread, they should be eliminated or moved to the main thread. Failure to do so can cause an app crash. Instead of using renderInContext, use the new MKMapSnapshotter APIs.

Known Issues

  • Using +[MKMapCamera cameraLookingAtCenterCoordinate:fromEyeCoordinate:eyeAltitude:] may result in the wrong map heading being chosen.

  • Using +[MKMapSnapshot pointForCoordinate:] returns the wrong result for nonsquare snapshots.

Multitasking

Known Issues

  • Silent pushes will always wake the device.

  • Currently, there is no API that lets you inspect the settings controlling your app’s background behavior.

Music Player

Known Issues

MPMediaPickerController has been disabled for this seed. It will immediately return as if the user canceled the selection.

Networking

Notes

  • Cellular fallback is a technology that will attempt to connect over the cellular interface when a connection over the Wi-Fi interface does not succeed. There are a number of cases where connection failures may occur over Wi-Fi, such as a cable modem in need of a reboot or a firewall that blocks access to certain resources.

    If your app restricts network operations over the cellular network, verify that your code is using the proper API to implement that policy.

    For example, if your app watches SCNetworkReachability for the kSCNetworkReachabilityFlagsIsWWAN to monitor when Wi-Fi is available, it may not behave correctly under cellular fallback.

    If an app uses this method and then attempts to connect, thinking it will get a connection over Wi-Fi, the app may inadvertently end up with a connection over the cellular network. The lack of thekSCNetworkReachabilityFlagsIsWWAN is not a guarantee that your connection will not go over cellular. If your code needs to enforce that a connection not go over cellular, it needs to specify that when making a networking request.

    Instead, for CFNetwork code using CFSocketStreamCFHTTPStream, or similar APIs, set the kCFStreamPropertyNoCellular property to true on the CF object before connecting.

    For NSURLRequests, call [request setAllowsCellularAccess: false].

    In addition to making sure your code will never be connected over cellular because of cellular fallback, this call ensures that your code will never be connected over cellular because of the VPN or convoluted routing problems (connecting to IPv6 over cellular because only IPv4 is available over Wi-Fi, etc.).

    To verify that your app is behaving properly, you should test against a broken Wi-Fi network. The easiest way to set up a broken Wi-Fi network is to set up an Apple AirPort Base Station or other Wi-Fi access point to hand out a DHCP address and leave the access point disconnected from the Internet. Another simple way of testing is to unplug the cable or DSL line from your cable or DLS modem.

  • Two low-level networking APIs that used to return a MAC address now return the fixed value 02:00:00:00:00:00. The APIs in question are sysctl (NET_RT_IFLIST) and ioctl (SIOCGIFCONF). Developers using the value of the MAC address should migrate to identifiers such as -[UIDevice identifierForVendor]. This change affects all apps running on iOS 7.

Newsstand

Known Issues

Newsstand background downloads that use HTTP basic or digest authentication will prompt the user with authorization alerts (NSURLConnectionDelegate callbacks forconnectionShouldUseCredentialStorage and willSendRequestForAuthenticationChallenge are not called correctly).

Nike + iPod

Known Issues

The Nike + iPod app is not included in this seed.

Objective-C Runtime

Notes

Due to changes in how the isa field is implemented, *self may change during enumeration (for example, if the container is retained).

Workaround: When implementing countByEnumeratingWithState, do not set state->mutationsPtr = self.

Phone

Known Issues

If you select Voicemail and then another option, such as Contacts, and then return to Voicemail, the Phone app hangs. You will need to kill the Phone app and relaunch it.

Reminders

Known Issues

Reminders may become unusable after the user creates a new list.

Safari

Known Issues

  • Safari website credentials do not always autofill between mobile and desktop versions.

    Workaround: Use the desktop version if the site offers it.

  • Users cannot delete their passwords via Safari Settings > Autofill.

  • The SafariServices addToReadingList API doesn't work on devices. However, it works fine on iOS Simulator.

  • If a user deletes a saved credit card number (from Autofill), it will still autofill.

    Workaround: After deleting a credit card from Autofill, force-quit Safari or reboot the device.

Security

Notes

  • -[UIDevice uniqueIdentifier] is no longer accepted in submissions to the App Store. In iOS 7, apps that are already on the store or on users’ devices that call this removed API will no longer be returned the UDID. Instead, -[UIDevice uniqueIdentifier] will return a 40-character string starting with FFFFFFFF, followed by the hex value of -[UIDevice identifierForVendor]. It is important to consider how this will affect existing apps. Consider submitting updates that no longer access the UDID.

  • iOS now requests user consent for apps to use the microphone hardware on all iOS 6 devices. For devices sold in China, iOS will also request user consent for apps to use the camera hardware. The operating system will present the consent alert when you set the category of the instantiated AVAudioSesison. The AVAudioSessionCategories that will present the alert areAVAudioSessionCategoryRecord and AVAudioSessionCategoryPlayAndRecord.

    If the user doesn’t allow access, the audio session data will be all zeros (silence). For devices where camera access is requested and denied by the user, the video capture session is a black screen.

  • The API gethostuuid() has been removed and will not be accepted for submission to the store regardless of the targeted OS. For existing apps running on iOS 7, the function will return a uuid_trepresentation of the vendor identifier (-[UIDevice identifierForVendor]).

Known Issues

Changing the Require Passcode time setting after a restore from backup will require a reboot for the change to take effect.

Settings

Known Issues

  • In General > Background App Refresh, the per-app settings are not honored.

  • In Notification Center, when selecting an alert style for an app, the examples for None, Banners, and Alerts are not displayed.

Siri

Known Issues

The new Siri voices are not in this seed.

Social

Notes

Up through iOS 6, when using TWTweetComposeViewController and SLComposeViewController (the latter only for Twitter and Weibo, but not Facebook), if the caller supplies a completionHandler, the supplied completionHandler is responsible for dismissing the view controller. As of iOS 7, if the app links against the iOS 7 SDK, the view controller will dismiss itself even if the caller supplies acompletionHandler. To avoid this, the caller’s completionHandler should not dismiss the view controller.

Known Issues

When using the iOS 6.1 SDK on OS X v10.8 Mountain Lion, if you use the iOS 5.0 or iOS 5.1 Legacy SDK in iOS Simulator, you will not be able to use Twitter features: attempting to sign in to Twitter via the Settings pane will fail, and Twitter.framework will not work correctly. If you need to test Twitter features, you will need to choose either an iOS 6.1 or iOS 6.0 Simulator run destination, or you can test with iOS 5.x on a device.

Springboard

Notes

  • Active touches are no longer canceled when the user takes a screenshot.

  • Dynamic wallpaper is not available on iPhone 4.

Known Issues

When restoring from an iCloud backup on a device with hundreds of apps, Springboard may crash repeatedly.

Sync

Known Issues

The Wi-Fi sync option in iTunes is checked, but Wi-Fi devices do not appear in iTunes.

Workaround: On OS X, install the iOS 7.0 SDK after installing iTunes. Wi-Fi sync is not supported on Windows.

UIKit

Notes

  • +[UIPasteboard pasteboardWithName:create:] and +[UIPasteboard pasteboardWithUniqueName] now unique the given name to allow only those apps in the same application group to access the pasteboard. If the developer attempts to create a pasteboard with a name that already exists and they are not part of the same app suite, they will get their own unique and private pasteboard. Note that this does not affect the system provided pasteboards, general, and find.

  • Blurred layers are not available on iPhone 4.

  • Parallax is not available on iPhone 4.

  • Letterpress text is not available on iPhone 4.

Known Issues

  • When a device without a passcode is connected to an untrusted computer, iTunes will tell the user to approve on the phone, yet the phone never asks the user to approve. The phone is trusted anyway, so there is no functional impact, but the UI is missing.

  • UIPickerView with custom views doesn't show the views in the selection indicator.

  • UIRefreshControl and the associated table view are hidden under the nav bar when setTranslucent: is NO.

  • Auto Layout constraints do not take bar height into account, which leads to issues during rotation or when the height of the status bar changes.

  • UIButtonTypeInfoLightUIButtonTypeInfoDark, and UIButtonTypeDetailDisclosure buttons all look the same.

  • The UIImagePickerController does not show a live preview when using custom overlays.

  • Print Center is not functional. Seeing print job progress, job name, or job preview icon is not available in this seed. To ensure that the job name is correct for print jobs, use the Printer Simulator app in Xcode and check the log.

  • When using Auto Layout to position a UIButton, if you set the content compression resistance or content hugging priority to minimum, the button will have ambiguous layout.

    Workaround: Don’t use a content compression resistance or content hugging priority of less than 2 for UIButton.

  • UISwitchonTintColors is always green irrespective of what it’s set to.

  • The title of the UIRefreshControl appears below the navigation bar.

USB Tethering

Known Issues

Personal Hotspot (Internet Tethering) will not work if this seed of the iOS SDK 7.0 is installed.

Voice Memos

Known Issues

The VoiceMemos app is not available in this seed.

VoiceOver

Known Issues

  • Maps does not work with VoiceOver.

  • Siri and VoiceOver do not always work together properly.

  • Reminders does not work with VoiceOver.

Weather

Notes

Weather conditions are not animated on iPhone 4.

WebKit

Notes

  • Previously, when the viewport parameters were modified, the old parameters were never discarded. This caused the viewport parameters to be additive.

    For example, if you started with width=device-width and then changed it to initial-scale=1.0, you ended up with a computed viewport of .

    In iOS 7, this has been addressed. Now you end up with with a computed viewport of initial-scale=1.0.

  • Previously, when using <meta name="viewport" content="initial-scale=1.0, user-scalable=1">, the scale could be incorrect after rotation.

    Now, if a user has not scaled the page explicitly, the page is restored to its initial scale. Also, the current scale is now correctly restricted within the min-scale, max-scale bounds.

Known Issues

  • Some images for Retina display devices appear at twice the size that they should instead of being scaled down 50%. This issue can also occur with any image to be scaled that is larger than its container and that uses either the background-size property or the -webkit-background-size property. This issue affects both native apps that display web content and web pages viewed in Safari for iPhone.

    The background CSS shorthand property now resets the value of the background-size property to auto when background size is not specified. This new behavior is per the CSS spec, and the old behavior is available only for apps linked to an SDK prior to iOS 7.0 when running on iOS 7 or later.

    Workaround: Specify the background-size property or the -webkit-background-size property after the background shorthand property in the CSS stylesheet for the web content being displayed.

  • When scrolling a page with animations, the animations stop and do not resume when the scrolling has stopped.


'iOS' 카테고리의 다른 글

iOS 7.1 beta 5 Release Notes  (0) 2014.02.05
iOS SDK 릴리즈 노트 iOS7  (0) 2013.06.11
iOS Developer Library - What's New in iOS7  (0) 2013.06.11
iOS 7 Design Resources PDF 입니다.  (0) 2013.06.11

iOS 7.0

iOS 7 is a major update with compelling features for developers to incorporate into their apps. The UI has been completely redesigned. In addition, iOS 7 introduces a new animation system for creating 2D and 2.5D games. Multitasking enhancements, peer-to-peer connectivity, and many other important features make iOS 7 the most significant release since the first iPhone SDK.

This article summarizes the key developer-related features introduced in iOS 7. This version of the operating system runs on current iOS-based devices. In addition to describing the key new features, this article lists the documents that describe those features in more detail.

For late-breaking news and information about known issues, see iOS 7 Release Notes. For the complete list of new APIs added in iOS 7, see iOS 7.0 API Diffs.

User Interface Changes

iOS 7 includes many new features intended to help you create great user interfaces.

A New Design

The iOS 7 UI has been completely redesigned. Throughout the system, a sharpened focus on functionality and on the user's content informs every aspect of design. Translucency, refined visual touches—and fluid, realistic motion—impart clarity, depth, and vitality to the user experience. Whether you're creating a new app or updating an existing one, keep these qualities in mind as you work on the design.

Apps compiled against the iOS 7 SDK automatically receive the new appearance for any standard system views when the app is run on iOS 7. If you use Auto Layout to set the size and position of your views, those views are repositioned as needed. But there may still be additional work to do to make sure your interface still has the appearance you want. Similarly, if you customize your app’s views, you may need to make changes to support the new appearance fully.

For guidance on how to design apps that take full advantage of the new look in iOS 7, see iOS 7 Design Resources.

UIKit Dynamics

Apps can now specify dynamic behaviors for UIView objects and for other objects that conform to the UIDynamicItem protocol. (Objects that conform to this protocol are called dynamic items.) Dynamic behaviors offer a way to improve the user experience of your app by incorporating real-world behavior and characteristics, such as gravity, into your app’s animations. UIKit supports the following types of dynamic behaviors:

  • UIAttachmentBehavior object specifies a connection between two dynamic items or between an item and a point. When one item (or point) moves, the attached item also moves. The connection is not completely static, though. An attachment behavior has damping and oscillation properties that determine how the behavior changes over time.

  • UICollisionBehavior object lets dynamic items participate in collisions with each other and with the behavior’s specified boundaries. The behavior also lets those items respond appropriately to collisions.

  • UIGravityBehavior object specifies a gravity vector for its dynamic items. Dynamic items accelerate in the vector’s direction until they collide with other appropriately configured items or with a boundary.

  • UIPushBehavior object specifies a continuous or instantaneous force vector for its dynamic items.

  • UISnapBehavior object specifies a snap point for a dynamic item. The item snaps to the point with a configured effect. For example, it can snap to the point as if it were attached to a spring.

Dynamic behaviors become active when you add them to an animator object, which is an instance of the UIDynamicAnimator class. The animator provides the context in which dynamic behaviors execute. A given dynamic item can have multiple behaviors, but all of those behaviors must be animated by the same animator object.

For information about the behaviors you can apply, see UIKit Framework Reference.

Text Kit

Text Kit is a full-featured, high-level framework for apps that need to handle text that has all the characteristics of fine typography. Text Kit can lay out styled text into paragraphs, columns, and pages; it easily flows text around arbitrary regions such as graphics; and it manages multiple fonts. Text Kit is integrated with all UIKit text-based controls to enable applications to create, edit, display, and store text more easily—and with less code than was previously possible in iOS.

Text Kit comprises new classes plus extensions to existing classes, including the following:

For more information about Text Kit, see Text Programming Guide for iOS.

Multitasking Enhancements

iOS 7 supports the following new background execution modes for apps:

  • Apps that regularly require new content can register with the system and be woken up or launched periodically to download that content in the background. To register, include the UIBackgroundModes key with the fetch value in your app’s Info.plist file and set the minimum time you want between fetch operations using the setMinimumBackgroundFetchInterval: method. You must also implement the application:performFetchWithCompletionHandler: method in your app delegate to perform any downloads.

  • Apps that use push notifications to notify the user that new content is available can now use those notifications to initiate background download operations. To support this mode, include the UIBackgroundModes key with the remote-notification value in your app’s Info.plist file. Your app delegate must also implement the application:didReceiveRemoteNotification:fetchCompletionHandler: method.

Apps supporting either the fetch or remote-notification background modes may be launched or moved from the suspended to background state at appropriate times. In the case of the fetch background mode, the system uses available information to determine the best time to launch or wake apps. For example, it does so when networking condition are good or when the device is already awake. Apps supporting the remote-notification background mode may be woken up when a new push notification arrives but before that notification is delivered to the user. The app can use the interval to download new content and have that content ready to present to the user when the notification is subsequently delivered.

To handle the downloading of content in the background, apps should use the new NSURLSession class. This class improves on the existing NSURLConnection class by providing a simple, task-based interface for initiating and processing NSURLRequest objects. A single NSURLSession object can initiate multiple download and upload tasks, and through its delegate can handle any authentication requests coming from the server.

For more information about the new background modes, see “App States and Multitasking” in iOS App Programming Guide.

Games

iOS 7 includes enhanced support for games.

Sprite Kit Framework

The Sprite Kit framework (SpriteKit.framework) provides a hardware-accelerated animation system optimized for creating 2D and 2.5D games. Sprite Kit provides the infrastructure that most games need, including a graphics rendering and animation system, sound playback support, and a physics simulation engine. Using Sprite Kit frees you from creating these things yourself and lets you focus on the design of your content and the high-level interactions for that content.

Content in a Sprite Kit app is organized into scenes. A scene can include textured objects, video, path-based shapes, Core Image filters, and other special effects. Sprite Kit takes those objects and determines the most efficient way to render them onscreen. When it comes time to animate the content in your scenes, you can use Sprite Kit to specify explicit actions you want to perform or use the physics simulation engine to define physical behaviors (such as gravity, attraction, or repulsion) for your objects.

In addition to the Sprite Kit framework, there are Xcode tools for creating particle emitter effects and texture atlases. You can use the Xcode tools to manage app assets and update Sprite Kit scenes quickly.

For more information about how to use Sprite Kit, see Sprite Kit Programming Guide. To see an example of how to use Sprite Kit to build a working app, seecode:Explained Adventure.

Game Controller Framework

The Game Controller framework (GameController.framework) lets you discover and configure Made-for-iPhone/iPod/iPad (MFi) game controller hardware in your app. Game controllers can be devices connected physically to an iOS device or connected wirelessly over Bluetooth. The Game Controller framework notifies your app when controllers become available and lets you specify which controller inputs are relevant to your app.

For more information about supporting game controllers, Game Controller Programming Guide.

Game Center Improvements

Game Center includes the following improvements:

  • Exchanges give players an opportunity to initiate actions with other players, even when it is not their turn. You can use this feature to implement simultaneous turns, player chats, and trading between players when it is not their turn.

  • The limit on per-app leaderboards has been raised from 25 to 100. You can also organize your leaderboards using a GKLeaderboardSet object, which increases the limit to 500.

  • You can add conditions to challenges that define when the challenge has been met. For example, a challenge to beat a time in a driving game might stipulate that other players must use the same vehicle.

  • The framework has improved its authentication support and added other features to prevent cheating.

For more information about how to use the new Game Center features, see Game Center Programming Guide. For information about the classes of the Game Kit framework, see Game Kit Framework Reference.

Maps

The Map Kit framework (MapKit.framework) includes numerous improvements and features for apps that use map-based information. Apps that use maps to display location-based information can now take full advantage of the 3D map support found in the Maps app, including controlling the viewing perspective programmatically. Map Kit includes other changes that enhance maps in your app.

  • Overlays can be placed at different levels in the map content, so that they appear above or below other relevant data.

  • You can apply an MKMapCamera object to a map to add position, tilt, and heading information to their appearance. Camera information imparts a 3D viewing experience onto your map like the one provided by Maps.

  • The MKDirections class lets you ask for direction-related route information from Apple. You can use that route information to create overlays for display on your own maps.

  • The MKGeodesicPolyline class lets you create a line-based overlay that follows the curvature of the earth.

  • Apps can use the MKMapSnapshotter class to capture map-based images.

  • The visual representation of overlays is now based on the MKOverlayRenderer class, which replaces overlay views and offers a simpler rendering approach.

  • Apps can now supplement or replace a map’s existing tiles using the MKTileOverlay and MKTileOverlayRenderer classes.

For more information about the classes of the Map Kit framework, see Map Kit Framework Reference.

AirDrop

AirDrop lets users share photos, documents, URLs, and other kinds of data with nearby devices. AirDrop support is now built-in to the existingUIActivityViewController class. This class displays different options for sharing the content that you specify. If you are not yet using this class, you should consider adding it to your interface.

For more information about using an activity view controller to share data, see UIActivityViewController Class Reference

Inter-App Audio

The Audio Unit framework (AudioUnit.framework) adds support for Inter-App Audio, which enables the ability to send MIDI commands and stream audio between apps on the same device. For example, you might use this feature to record music from an app acting as an instrument or use it to send audio to another app for processing. To vend your app’s audio data, publish a AURemoteIO instance as an audio component that is visible to other processes. to use audio features from another app, use the audio component discovery interfaces in iOS 7.

For information about the new interfaces, see the framework header files. For general information about the interfaces of this framework, see Audio Toolbox Framework Reference.

Peer-to-Peer Connectivity

The Multipeer Connectivity framework (MultipeerConnectivity.framework) supports the discovery of nearby devices and the direct communication with those devices without requiring Internet connectivity. This framework makes it possible to create multipeer sessions easily and to support reliable in-order data transmission and real-time data transmission. With this framework, your app can communicate with nearby devices and seamlessly exchange data.

The framework provides programmatic and UI-based options for discovering and managing network services. Apps can integrate the MCPeerPickerViewControllerclass into their UI to display a list of peer devices for the user to choose from. Alternatively, you can use the MCNearbyServiceBrowser class to look for and manage peer devices programmatically.

For more information about the interfaces of this framework, see Multipeer Connectivity Framework Reference.

New Frameworks

iOS 7 includes the following new frameworks:

  • The Game Controller framework provides an interface for communicating with game-related hardware; see “Game Controller Framework”.

  • The Sprite Kit framework provides support for sprite-based animations and graphics rendering; see “Sprite Kit Framework.”

  • The Multipeer Connectivity framework provides peer-to-peer networking for apps; see “Peer-to-Peer Connectivity.”

  • The JavaScript Core framework (JavaScriptCore.framework) provides Objective-C wrapper classes for many standard JavaScript objects. Use this framework to evaluate JavaScript code and parse JSON data. For information about the classes of this framework, see the header files.

  • The Media Accessibility framework (MediaAccessibility.framework) manages the presentation of closed-caption content in your media files. This framework works in conjunction with new settings that let the user enable the display of closed captions.

  • The Safari Services framework (SafariServices.framework) provides support for programmatically adding URLs to the user’s Safari reading list. For information about the class provided by this framework, see the framework header files.

Additional Framework Enhancements

In addition to the items discussed in the preceding sections, the following frameworks have significant enhancements. For a complete list of new interfaces, see iOS 7.0 API Diffs.

UIKit Framework

The UIKit framework (UIKit.framework) includes the following enhancements:

  • All UI elements have been updated to present the new look associated with iOS 7.

  • UIKit Dynamics lets you mimic real-world effects such as gravity in your animations; see “UIKit Dynamics.”

  • Text Kit provides sophisticated text editing and display capabilities; see “Text Kit.”

  • The UIView class defines the following additions:

    • The tintColor property applies a tint color that affects both the view and its subviews. For information on how to apply tint colors, see iOS 7 UI Transition Guide.

    • You can create keyframe-based animations using views. You can also make changes to your views and specifically prevent any animations from being performed.

  • The UIViewController class defines the following additions:

    • View controller transitions can be customized, driven interactively, or replaced altogether with ones you designate.

    • View controllers can now specify their preferred status bar style and visibility. The system uses the provided information to manage the status bar style as new view controllers appear. You can also control how this behavior is applied using the UIViewControllerBasedStatusBarAppearance key in your app’sInfo.plist file.

  • The UIMotionEffect class defines the basic behavior for motion effects, which are objects that define how a view responds to device-based motion.

  • Collection views support UIKit Dynamics. Using this support, you can apply behavior objects to layout attributes to animate the corresponding items in the collection.

  • The imageNamed: method of UIImage supports retrieving images stored in image asset catalogs, which are a way to manage and optimize assets that have multiple sizes and resolutions. You create image asset catalogs in Xcode.

  • There is a new snapshot method on UIView and UIScreen creates a view that you can use to present your app’s content.

  • The UIKeyCommand class wraps keyboard events received from an external hardware keyboard. These events are delivered to the app’s responder chain for processing.

  • UIFontDescriptor object describes a font using a dictionary of attributes. Use font descriptors to interoperate with other platforms.

  • The UIFont and UIFontDescriptor classes support dynamic text sizing, which improves legibility for text in apps. With this feature, the user controls the desired font size that all apps in the system should use.

  • The UIActivity class now supports new activity types, including activities for sending items via AirDrop, adding items to a Safari reading list, and posting content to Flickr, Tencent Weibo, and Vimeo.

  • The UIApplicationDelegate protocol adds methods for handling background fetch behaviors.

  • UIKit adds support for running in a guided-access mode, which allows an app to lock itself to prevent modification by the user. This app is intended for institutions such as schools where users bring their own devices but need to run apps provided by the institution.

  • State restoration now allows the saving and restoration of any object. Objects adopting the UIStateRestoring protocol can write out state information when the app moves to the background and have that state restored during subsequent launches.

  • Table views now support estimating the height of rows and other elements, which improves scrolling performance.

For information about the classes of this framework, see UIKit Framework Reference.

Store Kit Framework

The Store Kit framework (StoreKit.framework) has migrated to a new receipt system that developers can use to verify in-app purchases on the device itself. You can also use it to verify the app purchase receipt on the server.

For more information about how to use this new receipt system, see Receipt Validation Programming Guide.

Security Framework

The Security framework (Security.framework) adds support for syncing passwords between user's devices via iCloud. Apps can mark their keychain items for iCloud via a new keychain attribute (kSecAttrSyncronizable).

For more information about this attribute, see the framework header files. For general information about the keychain, see the Keychain Services Programming Guide.

Pass Kit Framework

The Pass Kit framework (PassKit.framework) includes new APIs for adding multiple passes at once, along with these additions to the pass file format:

  • New keys specify the expiration date for a pass.

  • You can specify that a pass is relevant only when it is in the vicinity of specific Bluetooth beacons.

  • New attributes control how a pass is displayed. You can group passes together, display links with custom text on the back of a pass, and control how time values are displayed on the pass.

  • You can now associate extra data with a pass. This data is available to your app but not displayed to the user.

  • You can designate which data detectors to apply to the fields of your passes.

For information about how to use Pass Kit in your app, see Passbook Programming Guide. For information about the pass file format, see Passbook Package Format Reference.

OpenGL ES

OpenGL ES includes the following new extensions:

  • The EXT_sRGB extension adds support for sRGB framebuffer operations.

  • The GL_APPLE_pvrtc_sRGB extension adds support for sRGB texture data compressed in the PVRTC texture format.

  • The GL_APPLE_draw_instanced and GL_APPLE_instanced_arrays extensions can improve rendering performance when your app draws multiple instances of the same object. You use a single call to draw instances of the same object. You add variation to each instance by specifying how fast each vertex attribute advances or by referencing an ID for each instance in your shader.

As always, check for the existence of an extension before using it in your app.

Also, textures can now be accessed in vertex shaders; query the value of the MAX_VERTEX_TEXTURE_IMAGE_UNITS attribute to determine the exact number of textures you can access.

MessageUI Framework

In the MessageUI framework, the MFMessageComposeViewController class adds support for attaching files to messages. For information about the new interfaces, see the framework header files.

For information about the classes of this framework, see Message UI Framework Reference.

Media Player Framework

In the Media Player framework, the MPVolumeView class provides support for determining whether wireless routes such as AirPlay and Bluetooth are available for the user to select. You can also determine whether one of these wireless routes is currently active. For information about the new interfaces, see the framework header files. For information about the classes of Media Player framework, see Media Player Framework Reference.

Map Kit Framework

The Map Kit framework (MapKit.framework) includes changes that are described in “Maps.”

For information about the classes of this framework, see Map Kit Framework Reference.

Image I/O Framework

The Image I/O framework (ImageIO.framework) now has interfaces for getting and setting image metadata.

For information about the new interfaces, see the framework header files. For information about the classes of this framework, see Image I/O Reference Collection.

iAd Framework

The iAd framework (iAd.framework) includes two extensions to other frameworks that make it easier to incorporate ads into your app’s content:

  • The framework introduces new methods on the MPMoviePlayerController class that let you run ads before a movie.

  • The framework extends the UIViewController class to make it easier to create ad-supported content. You can now configure your view controllers to display ads before displaying the actual content they manage.

For information about the new interfaces, see the framework header files. For information about the classes of this framework, see Ad Support Framework Reference.

Game Kit Framework

The Game Kit framework (GameKit.framework) includes numerous changes, which are described in “Game Center Improvements.”

For information about the classes of this framework, see Game Kit Framework Reference.

Foundation Framework

The Foundation framework (Foundation.framework) includes the following enhancements:

  • The NSURLSession class is a new class for managing the acquisition of network-based resources in the background. This class serves as a replacement for theNSURLConnection class and its delegate; it also replaces the NSURLDownload class and its delegate.

  • The NSURLComponents class is a new class for parsing the components of a URL. This class supports the URI standard (rfc3986/STD66) for parsing URLs.

  • The NSNetService and NSNetServiceBrowser classes support peer-to-peer discovery over Bluetooth and Wi-Fi.

  • The NSURLCredential and NSURLCredentialStorage classes let you create credentials with a synchronizable policy and provide the option of removing credentials with a synchronizable policy from iCloud.

  • The NSURLCacheNSURLCredentialStorageNSHTTPCookieStorage classes now support for the asynchronous processing of storage requests.

  • The NSCalendar class supports new calendar types.

For information about the new interfaces, see the framework header files and Foundation release notes. For general information about the classes of this framework, see Foundation Framework Reference.

Core Telephony Framework

The Core Telephony framework (CoreTelephony.framework) lets you get information about the type of radio technology in use by the device, the current signal strength, and the cell ID serving the device. Apps developed in conjunction with a carrier can also authenticate their apps against a particular subscriber for that carrier.

For information about the new interfaces, see the framework header files. For general information about the classes of the Core Telephony framework, see Core Telephony Framework Reference

Core Motion Framework

The Core Motion framework (CoreMotion.framework) adds support for step counting and motion tracking. With step counting, the framework detects movements that correspond to user motion and uses that information to report the number of steps to your app. Because the system detects the motion, the system can continue to gather step data even when your app is not running. Alongside this feature, the framework can also distinguish different types of motion, including different motions reflective of travel by walking, by running, or by automobile. Navigation apps might use that data to change the type of directions they give to users.

For information about the new interfaces, see the framework header files. For general information about the classes of this framework, see Core Motion Framework Reference.

Core Location Framework

The Core Location framework (CoreLocation.framework) supports ranging using Bluetooth devices. Ranging lets you determine the relative range of nearby Bluetooth devices and respond appropriately. For example, a museum might place Bluetooth beacons in its galleries and provide visitors with an app that displays information as the user enters and exits those galleries. The framework also supports deferring the delivery of location updates until a specific time has elapsed or the user has moved a minimum distance.

For general information about the classes of this framework, see Core Location Framework Reference.

Core Foundation Framework

The Core Foundation framework (CoreFoundation.framework) now supports scheduling stream objects on dispatch queues. For information about the new interfaces, see the framework header files.

For general information about the interfaces of this framework, see Core Foundation Framework Reference.

Core Bluetooth Framework

The Core Bluetooth framework (CoreBluetooth.framework) includes the following enhancements:

  • The framework supports saving state information for central and peripheral objects and restoring that state at app launch time. You can use this feature to support long-term actions involving Bluetooth devices.

  • The central and peripheral classes now use an NSUUID object to store unique identifiers.

  • You can now retrieve peripheral objects from a central manager synchronously.

For information about the new interfaces, see the framework header files. For general information about the classes of this framework, see Core Bluetooth Framework Reference.

AV Foundation Framework

The AV Foundation framework (AVFoundation.framework) includes the following enhancements:

  • The AVAudioSession class supports the following new behaviors:

    • Support for selecting the preferred audio input, including audio from built-in microphones

    • Support for multichannel input and output

  • The AVVideoCompositing and related classes let you support custom video compositors.

  • The AVSpeechSynthesizer and related classes provide speech synthesis capabilities.

  • The capture classes add support and interfaces for the following features:

    • Discovery of a camera’s supported formats

    • Support for 60 fps recording

    • Video zoom (true and digital) in recordings and video preview, including custom ramping

    • Real-time discovery of machine-readable barcode metadata

    • Autofocus range restriction

    • Access to the clocks used during capture

  • There are new metadata key spaces for supported ISO formats such as MPEG-4 and 3GPP and improved support for filtering metadata items when copying those items from source assets to output files using the AVAssetExportSession class.

  • The AVAssetWriter class provides assistance in formulating output settings and there are new level constants for H.264 encoding.

  • The AVPlayerLayer class adds the videoRect property, which you can use to get the size and position of the video image.

  • The AVPlayerItem class supports the following changes:

    • Asset properties can be loaded automatically when AVPlayerItem objects are prepared for playback.

    • When you link your app against iOS SDK 7, the behavior when getting the values of player item properties—such as the duration, or tracks, orpresentationSize properties—is different than pervious versions of iOS. The properties of this class now return a default value and no longer block your app if the AVPlayerItem object is is not yet ready to play. As soon as the player item’s status changes to AVPlayerItemStatusReadyToPlay, the getters reflect the actual values of the underlying media resource. If you use key-value observing to monitor changes to the properties, your observers are notified as soon as changes are available.

  • The AVPlayerItemLegibleOutput class can process timed text from media files.

  • The AVAssetResourceLoadingDelegate protocol now supports loading of arbitrary ranges of bytes from a media resource.

For information about the new interfaces, see the framework header files. For general information about the classes of this framework, see AV Foundation Framework Reference.

Accelerate Framework

The Accelerate framework (Accelerate.framework) includes the following enhancements:

  • Improved support for manipulating Core Graphics data types

  • Support for working with grayscale images of 1, 2, or 4 bits per pixel

  • New routines for converting images between different formats and transforming image contents

  • Support for biquad (IIR) operations

For information about the new interfaces, see the framework header files. For general information about the functions and types of this framework, see Accelerate Framework Reference.

Objective-C

The Objective-C programming language has been enhanced to support modules, resulting in faster builds and shorter project indexing times. Module support is enabled in all new projects created using Xcode 5. If you have existing projects, you must enable this support explicitly by modifying your project’s Enable Modules setting.

Deprecated APIs

From time to time, Apple adds deprecation macros to APIs to indicate that those APIs should no longer be used in active development. When a deprecation occurs, it is not an immediate end-of-life to the specified API. Instead, it is the beginning of a grace period for transitioning off that API and onto newer and more modern replacements. Deprecated APIs typically remain present and usable in the system for a reasonable amount of time past the release in which they were deprecated. However, active development on them ceases and the APIs receive only minor changes—to accommodate security patches or to fix other critical bugs. Deprecated APIs may be removed entirely from a future version of the operating system.

As a developer, it is important that you avoid using deprecated APIs in your code as soon as possible. At a minimum, new code you write should never use deprecated APIs. And if you have existing code that uses deprecated APIs, update that code as soon as possible. Fortunately, the compiler generates warnings whenever it spots the use of a deprecated API in your code and you can use those warnings to track down and remove all references to those APIs.

This release includes deprecations in the following technology areas:

  • The Map Kit framework includes deprecations for the MKOverlayView class and its various subclasses. The existing overlay views have been replaced with an updated set of overlay renderer objects that descend from the MKOverlayRenderer class. For more information about the classes of this framework, see Map Kit Framework Reference.

  • The AudioSession API in the Audio Toolbox framework is deprecated. Applications should use the AVAudioSession class in the AV Foundation framework instead.

  • The CLRegion class in the Core Location framework is replaced by the CLCircularRegion class. The CLRegion class continues to exist as an abstract base class that supports both geographic and beacon regions.

  • The UUID property of the CBCentral class is deprecated. To specify the unique ID of your central objects, use the identifier property instead.

  • The Game Kit framework contains assorted deprecations intended to clean up the existing API and provide better support for new features.

  • The UIKit framework contains the following deprecations:

    • The wantsFullScreenLayout property of UIViewController is deprecated. In iOS 7 and later, view controllers always support full screen layout.

    • The UIPopoverController class no longer supports the notion of an arrow direction; it supports a presentation direction.

    • UIColor objects that provided background textures for earlier versions of iOS are gone.

    • Many drawing additions to the NSString class are deprecated in favor of newer variants.

  • The gethostuuid function in the libsyscall library is deprecated.

  • In iOS 7 and later, if you ask for the MAC address of an iOS device, the system returns the value 02:00:00:00:00:00. If you need to identify the device, use theidentifierForVendor property of UIDevice instead. (Apps that need an identifier for their own advertising purposes should consider using theadvertisingIdentifier property of ASIdentifierManager instead.)

For a complete list of specific API deprecations, see iOS 7.0 API Diffs.


'iOS' 카테고리의 다른 글

iOS SDK 릴리즈 노트 iOS7  (0) 2013.06.11
iOS Developer Library - What's New in iOS7  (0) 2013.06.11
iOS 7 Design Resources PDF 입니다.  (0) 2013.06.11
iOS 7 beta for Developers  (0) 2013.06.11


iOS7 UIKit User Interface Catalog

UIKitUICatalog.pdf



iOS 7 UI Transition Guide

TransitionGuide.pdf



iOS Human Interface Guidelines

MobileHIG.vol1.egg

MobileHIG.vol2.egg




ps. 외부 링크 거실땐 반드시 댓글로 명시해주세요


'iOS' 카테고리의 다른 글

iOS Developer Library - What's New in iOS7  (0) 2013.06.11
iOS 7 Design Resources PDF 입니다.  (0) 2013.06.11
iOS 7 beta for Developers  (0) 2013.06.11
[apple]iOS 6.1 Xcode 4.6 업데이트  (0) 2013.01.29

요즘 많이 사용하는 스마트폰 이나~ 패드~ 노트북에 이르기까지 많은 무선기기들이 많이 사용되고 있다.

 

근데 예상외로 연결이 안되는데 그 원인을 알수가 없다는 경우가 많다.

 

아주 단순한 원인임에도 불구하고~

 

 

 

1. 안테나 손상.

 

뭐 제목에서도 보다시피 기기의 안테나 손상의 경우를 들수있다.

 

기기내에서 주변 와이파이가 감지가 안되는경우.

 

충격이나 외부 자극에 의한 안테나 손상 문제일 가능성이 높다.

 

 

 

2. 공유기 무선랜 호환 모드 설정

 

예상외로 공유기 설정을 만지작 하다 설정하기도 하는데 잘 모른경우가 많아 공유기 초기화로 해결하는경우가 많은듯 하다.

 

EFM 네트워크 iptime 계열의 관리자 설정 에 무선 설정/보안  메뉴를 열어보면

 

모드 라는 옵션이 있는데...

 

도움말을 보면

 

---------------------------------------------------------------------------------------------

모드는 무선랜 카드와의 호환성을 설정합니다. (제품별로 지원할 수 있는 모드가 다를 수 있습니다.)

---------------------------------------------------------------------------------------------
11a/n 5GHz : 5GHz 대역의 11a/n 기반의 무선 호스트가 접속할 수 있습니다.
B,G,N : 802.11n/11b/11g 기반의 무선 호스트가 접속할 수 있습니다.
G,N : 802.11g/11n 기반의 무선 호스트가 접속할 수 있습니다.
N Only : 802.11n 기반의 무선 호스트만 접속할 수 있습니다.
G Only : 802.11g(54Mbps)기반의 무선 호스트만 접속할 수 있습니다.
G and B : 802.11g(54Mbps)와 802.11B(11Mbps)기반의 무선 호스트가 접속할 수 있습니다.
B Only : 802.11b(11Mbps) 기반의 무선 호스트만 접속할 수 있습니다.

---------------------------------------------------------------------------------------------

 

최근 나온 기기들의 경우 는 대부분 N 인경우가 대부분이지만

 

아이폰 3Gs 의 랜카드는 802.11g 표준 으로서 G 모드도  설정을 해줘야 접속이 가능하다.

 

혼자만 쓰는거면야 자신의 스마트폰에 맞게 설정하면 되지만 여러명이 같이쓰는 곳이라면 B G N 모두를 설정하는게 덜 귀찮을 듯 ~

 

 

 

3. 기타 접속불가

 

뭐 비밀번호틀린거라면 알아서 해결을 보시고;;

 

랜카드고장... 공유기 불량 등의 기기오류는 역시 a/s -_-b

 

주변에 많은 밀집된 주파수 사용으로 인한 통신 간섭 등에 의해 접속이 불안정하다거나 하다면....

 

전문가를 초빙하시던가 그게 힘드시다면 5GHz 주파수대를 사용하는 공유기가 판매되고있으니 (조금 고가 이긴 하지만) 간단하게 돈으로 서 해결이 가능하다... 속도나 거리의 장점이 있긴하다(역시 돈이 최고인가 ㅋ)

 

 

 

 

ps. kt쿡허브 쓰레기 인듯;; 인터넷전화때메 어쩔수없이 강매 당했지만....(모델이 쿡허브 전화밖에 없다니 어이없는 ㅋ) 쓰고있는데 아주 최악의 허브인듯;; 결국... 이글 작성하면서 5Ghz구매완료...

 

 

 

 

 

iOS SDK Release Notes for iOS 6 beta 3

Contents:

Introduction
Bug Reporting
Notes and Known Issues


Introduction

iOS SDK 6.0 provides support for developing iOS apps and 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 that run on iPhone, iPad, or iPod touch running iOS 6. You can also test your apps using the included iOS Simulator, which supports iOS 6. iOS SDK 6.0 requires a Macintosh computer running OS X 10.7.4 or higher (Lion).

This version of iOS is intended only for installation on devices registered with Apple's 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

Please report any bugs not mentioned in the “Notes and Known Issues” section using the Apple Bug Reporter on the Apple Developer website (http://developer.apple.com/bugreporter/). Additionally, you may discuss these issues and iOS SDK 6 in the Apple Developer Forums: http://devforums.apple.com. You can get more information about iCloud for Developers at: http://developer.apple.com/icloud

Notes and Known Issues

The following issues relate to using iOS SDK 6.0 to develop code.

Address Book

  • When an app is in a fresh privacy state and tries to present a ABNewPersonViewController, the user cannot dismiss that view controller properly even if they allow access to contacts. The user must force quit the app and relaunch.

  • Requesting access to contacts:

    • Users are able to grant or deny access to contact data on a per-app basis. To request access to contact data, call the ABAddressBookRequestAccessWithCompletion function after calling the ABAddressBookCreateWithOptions function. The ABAddressBookRequestAccessWithCompletion function does not block the app while the user is being asked to grant or deny access. Until access has been granted, the ABAddressBookRef object will not contain any contacts and any attempt to modify contacts fails with a kABOperationNotPermittedByUserError error. The user is prompted only the first time access is requested; any subsequent calls to ABAddressBookCreateWithOptions will use the existing permissions. The completion handler is called on an arbitrary queue. If the ABAddressBookRef object is used throughout the app, then all usage must be dispatched to the same queue to use ABAddressBookRef in a thread-safe manner.

  • Checking access authorization status:

    • An app can use the authorization status API to check if it can access contacts, calendars, reminders or photo library. This API is independent from the the request access API and will not prompt the user to grant or deny access. With this API an app can adjust the display of its UI elements that would access the data class. For example, if access to contacts is authorized or not determined then a UI button to pick a contact can be displayed.

    • For Address Book, call the ABAddressBookGetAuthorizationStatus function. For Event Kit, call the authorizationStatusForEntityType: class method of EKEventStore. For Assets Library, call the authorizationStatus class method of ALAssetsLibrary. The meaning of the status values that are returned is as follows:

      • Authorization Status Not Determined - The user has not yet made a choice regarding whether this app can access the data class.

      • Authorization Status Restricted - This app is not authorized to access the data class. The user cannot change this app’s status, possibly due to active restrictions such as parental controls being in place.

      • Authorization Status Denied - The user explicitly denied access to the data class for this app.

      • Authorization Status Authorized - This app is authorized to access the data class.

Apple TV

  • In some cases, the screen may show the wrong resolution. Restart your Apple TV to return it to the correct resolution.

  • FIXED: Netflix videos may not resume where you left off.

  • FIXED: The History list in the YouTube app gets cleared when you exit and reenter the app.

  • Apple TV may be slow to respond while a download is in progress in the background.

  • Apple TV may restart while using the Remote app.

  • Apple TV may restart when changing the system language.

  • Photo Stream does not load when logging in a second time. Restart Apple TV to resolve.

  • Music does not play during photo slideshows.

  • New Behaviors:

    • Pick remote speakers in Settings > AirPlay.

    • Set an onscreen code for AirPlay in Settings > AirPlay.

    • Save multiple iTunes Store accounts in Settings > iTunes Store.

    • Press and hold the Select button to rearrange icons on the main menu.

    • Hide the main menu icons in Settings > General > Parental Controls.

Bonjour

  • The NSNetService class and CFNetService APIs do not include P2P interfaces by default. To browse, register, or resolve services over P2P interfaces, an app needs to use the Bonjour DNSService*() APIs noted below.

  • Setting the interfaceIndex parameter to kDNSServiceInterfaceIndexAny in the following API's will not include P2P interfaces by default. To include P2P interfaces, you must now set the kDNSServiceFlagsIncludeP2P flag when using kDNSServiceInterfaceIndexAny or set the interfaceIndex to kDNSServiceInterfaceIndexP2P. The affected APIs are:

    • DNSServiceBrowse

    • DNSServiceRegister

    • DNSServiceResolve

    • DNSServiceRegisterRecord

    • DNSServiceQueryRecord

Dictionary

  • There is a known issue with dictionaries when attempting to define a word in any language other than English or Japanese. When the reference library is presented, the user is presented with the option to download a dictionary - that download may not begin. The user can tap outside the popover on an iPad or tap the "Done" button on the iPhone or iPod touch in order to dismiss the download request.

Event Kit

  • Requesting access to calendars or reminders:

    • Users are able to grant or deny access to event and reminder data on a per-app basis. To request access to event and/or reminder data, call the requestAccessToEntityType:completion: method of EKEventStore. This will not block the app while the user is being asked to grant or deny access. Until access has been granted for an entity type, the event store will not contain any calendars for that entity type, and any attempt to save data will fail.

    • The user will only be prompted the first time access is requested; any subsequent instantiations of EKEventStore will use the existing permissions. The completion handler is called on an arbitrary queue.

Game Center

  • When creating a new Game Center account in-app on the iPad, the popover for selecting the month for your date of birth shows up with no content to select.

  • The authenticate method of GKLocalPlayer has been removed. Authentication will automatically commence when the completion handler is set.

iCloud

  • When creating an iCloud account, you can use any email based Apple ID, or you can use your existing iCloud account. If you had a MobileMe account that you have not yet moved to iCloud, you must move it first by visiting http://me.com. Moving to iCloud is only available for a limited time. Logging into a MobileMe account is not supported in iOS 6.

    • icloud.com email addresses are now available for iCloud mail users. Users signing up for new Apple IDs, or enabling Mail on their iCloud account for the first time, will automatically receive an @icloud.com email address instead of a me.com email address. iCloud users with @me.com addresses that have been used with iOS 6 beta 3 will receive an @icloud.com email address that matches their @me.com address.

    • icloud.com email cannot be sent from www.icloud.com. Users should use http://beta.icloud.com at this time if they wish to send email from their icloud.com address using a web browser.

  • Provisioning profiles must be enabled for iCloud in the iOS Provisioning Portal. To enable a provisioning profile for iCloud, navigate to the App ID section of the iOS Provisioning Portal and configure your App ID for iCloud. After enabling the App ID for iCloud, regenerate your provisioning profiles to enable them for iCloud.

  • The setSortDescriptors: method of NSMetadataQuery is not supported.

  • In iOS 6, files that are protected via Data Protection cannot be used with iCloud Storage APIs.

  • File names are case-insensitive in OS X but case-sensitive in iOS. This can lead to problems when sharing files between the two platforms using iCloud. You should take steps on iOS to avoid creating files whose names differ only by case.

  • The behavior of coordinated read operations on iCloud Documents has changed.

    On previous iOS releases, when your app performed a coordinated read operation on a file or package, and the iCloud daemon noticed that there was a newer version of the item available, the coordinated read operation blocked until the newer version of the item was downloaded and written to the disk.

    Starting in iOS 6 beta 3, when you start a coordinated read operation on a file or package for which you already have a local version, the coordinated read will be granted as soon as possible, and the new version, if any, will download in the background. This call will block for downloading reasons only if you do not have any version of the file available locally.

    Additionally, when the file is conflicted, the iCloud daemon will not wait until it has all the conflict losers of the file available to make the file available to your app. It will make the different versions of the conflicted file available as soon as it can. Your app can use the existing file coordination and the UIDocument callbacks to be notified when the conflict losers have been downloaded and are available.

iMessage & FaceTime

  • FIXED: The Answer and Decline buttons are missing when receiving calls in landscape orientations.

iTunes

  • iTunes 10.6.3 is required for iOS SDK 6.0.

  • FIXED: When restoring from an iTunes backup, the device intermittently shows up as a new device after rebooting. If that happens, set up the device as a “new device” when prompted to restore for the 2nd time. All data should have been restored correctly but sync settings including App arrangement in iTunes are lost.

Maps

  • In iOS 6 and later, Map Kit is built on a new infrastructure hosted by Apple. Earlier iOS releases will continue to use Google’s service.

    • API compatibility will be maintained (see known issues below).

    • Maps are now supported in the Simulator.

    • Map data will continue to evolve—only a limited amount of high resolution satellite imagery is currently available.

  • FIXED: If Maps is not running in the background, a "Maps cannot connect to the internet" error is displayed when it is launched from a 3rd party app.

  • FIXED: If Maps has not yet been launched, the current location does not show up when it is launched from a 3rd-party app.

  • Routing apps that do not specify a coverage file during development will always be displayed in the Maps routing search results.

  • Testing and debugging of coverage files for routing apps is only supported during development through the Xcode "Run" workflow. (You can specify the coverage file for a given Run scheme using the Options pane of the Run section of the scheme editor.) Apps that are archived and distributed (outside of the App Store) onto devices will not have access to the app's coverage files.

  • Maps does not zoom into the current location when launched from a 3rd party app.

Newsstand

  • Only simple http downloads will work with Newsstand.

Passbook

  • FIXED: An airplane icon appears between the origin and destination for all transit types.

  • The "Description" field is now a required field for a Pass. All passes created without it will fail to validate and will not ingest.

  • FIXED: The Passbook database has been reset. You’ll need to add your passes again.

  • Passbook in the simulator no longer requires https/ssl when using a webServiceURL when ingesting a pass.

  • Unable to show boarding passes on lock screen.

Reminders

  • FIXED: There are issues when adding and editing reminders in the Reminders app on iPhone devices:

    • The Done button is missing when adding a new reminder.

    • The app crashes when you tap the Edit button to edit a reminder.

Security

  • In iOS 5, signing a certificate with an MD5 signature is not supported. Please ensure that certificates use signature algorithms based on SHA1 or SHA2.

  • In iOS 6, there are improved privacy controls for Calendars, Reminders, Contacts, and Photos.

    • Users will see access dialogs when an app tries to access any of those data types. The user can switch access on and off in Settings > Privacy.

    • Developers can set a "purpose" string for each class of isolated data. iOS displays this string to users to help them understand why their data is being requested. These strings can be added using Xcode's Project editor, in the Info tab. The relevant key names begin with the string "Privacy -".

    • There are changes to the Event Kit and Address Book frameworks to help developers with this feature.

Simulator

  • The app delete confirmation alert panel takes a while to show up in iOS Simulator.

  • FIXED: Tapping the buy button in the view of an SKStoreProductViewController object in iOS Simulator causes the app to crash.

  • No privacy alerts are displayed in iOS Simulator for apps that access Photos, Contacts, Calendar and Reminders.

  • Downloading in-app purchase hosted content in iOS Simulator is not supported.

  • When attempting to play an MP3 sound in the Simulator, you will hear a popping sound instead.

  • FIXED: Using the iOS 5.1 SDK with the iPad (Retina) profile will result in a SpringBoard crash. The iOS 5.1 SDK works with all other profiles and the iPad (Retina) SDK works with the iOS 6.0 SDK.

  • FIXED: Ads of type ADAdTypeMediumRectangle do not appear in iPad Simulator.

Shared Photo Stream

  • User must go to Settings > iCloud to ensure that they receive Shared Photo Stream Notifications.

  • In order to share a Photo Stream with iOS 6 beta, you must invite someone using their iCloud email address or they will not receive the invitation.

  • Upgrading from iOS 6 beta 1 to beta 2 will cause your device to re-download all of your Shared Photo Streams.

  • The Shared Photo Stream feature is set to OFF when updating from iOS 6 beta 1 to a later release. The default setting should be ON.

  • Turning off Shared Photo Streams may leave camera in an unresponsive state, force quitting camera will resolve this issue.

Social

  • Weibo shows up in the Settings app only if a Chinese keyboard is enabled.

  • The requestAccessToAccountsWithType:withCompletionHandler: method of ACAccountStore is now deprecated. To access user accounts, please use the requestAccessToAccountsWithType:options:completion: method.

    In the options parameter of this new method, pass nil to access Twitter and Weibo accounts. To access Facebook accounts, pass a dictionary with the following keys (which are documented in ACAccountStore.h):

    • ACFacebookAppIdKey

    • ACFacebookPermissionsKey

    • ACFacebookPermissionGroupKey

    You should no longer add this dictionary to your app's Info.plist file, as was required in beta 1.

SpringBoard

  • FIXED: After restoring a device in iTunes or performing an "Erase All Contents and Settings", the current wallpaper may not appear until the device is rebooted once.

Status Bar

  • It is now possible to set status bar tint parameters in your app’s Info.plist file. You might do this to ensure that the status bar color matches the navigation bar color of your app during startup. To set the status bar tint, add the UIStatusBarTintParameters key to your Info.plist file. The value of this key is a dictionary with the appropriate values describing the navigation bar your app has at startup time. Inside the dictionary should be the UINavigationBar key, whose value is also a dictionary. That dictionary contains the initial navigation bar's style (with the Style key) and whether it's translucent (with the Translucent key). If your navigation bar uses them, you can also specify its tint color (with the TintColor key), or the name of its custom background image (with the BackgroundImage key).

UIKit

  • In iOS 5.1, the UISplitViewController class adopts the sliding presentation style when presenting the left view (previously only seen in Mail). This style is used when presentation is initiated either by the existing bar button item provided by the delegate methods or by a swipe gesture within the right view. No additional API adoption is required to obtain this behavior, and all existing API, including that of the UIPopoverController instance provided by the delegate, will continue to work as before. If the gesture would be insupportable in your app, setting the presentsWithGesture property of your split view controller to NO disables the gesture. However, disabling the gesture is discouraged because its use preserves a consistent user experience across all apps.

  • FIXED: In iOS 6, changes have been introduced so that you no longer need to set a delegate and implement a method for Single-Finger and Single-Tap gesture recognizers, in an effort to make them work well with the UIControl objects.

  • In iOS 6 and later, the UIWebView class paints its contents asynchronously.

  • FIXED: Developers trying out Auto Layout with UIScrollView objects might notice jitters in the scroll indicators on devices with Retina displays.

  • Autorotation is changing in iOS 6. In iOS 6, the shouldAutorotateToInterfaceOrientation: method of UIViewController is deprecated. In its place, you should use the supportedInterfaceOrientations and shouldAutorotate methods.

    • More responsibility is moving to the app and the app delegate. Now, iOS containers (such as UINavigationController) do not consult their children to determine whether they should autorotate. By default, an app and a view controller’s supported interface orientations are set to UIInterfaceOrientationMaskAll for the iPad idiom and UIInterfaceOrientationMaskAllButUpsideDown for the iPhone idiom.

    • A view controller’s supported interface orientations can change over time. Even an app’s supported interface orientations can change over time. The system asks both the topmost full screen view controller (typically the root view controller) for its supported interface orientations whenever the device rotates or whenever a view controller is presented with the full screen modal presentation style. Moreover the supported orientations are retrieved only if this view controller returns YES from its shouldAutorotate method. The system intersects the view controller’s supported orientations with the app's supported orientations (as determined by the Info.plist file or the app delegate's application:supportedInterfaceOrientationsForWindow: method) to determine whether to rotate.

    • The system determines if an orientation is supported by intersecting the value returned by the app’s supportedInterfaceOrientationsForWindow: method with the value returned by the supportedInterfaceOrientations method of the topmost fullscreen controller.

    • The setStatusBarOrientation:animated: method is not deprecated outright. However it now works only if the supportedInterfaceOrientations method of the topmost full screen view controller returns 0. This puts the responsibility of ensuring that the status bar orientation is consistent into the hands of the caller.

    • For compatibility, view controllers that still implement the shouldAutorotateToInterfaceOrientation: method do not get the new autorotation behaviors. (In other words, they do not fall back to using the app, app delegate, or Info.plist file to determine the supported orientations.) Instead, the shouldAutorotateToInterfaceOrientation: method used to synthesize the information that would be returned by the supportedInterfaceOrientations method.

  • FIXED: In certain situations, the Auto Layout system might not engage automatically for a view. To workaround this problem, override the requiresConstraintBasedLayout class method in your view and return YES from your implementation.

  • The willRotateToInterfaceOrientation:duration:, willAnimateRotationToInterfaceOrientation:duration:, and didRotateFromInterfaceOrientation: methods are no longer called on any view controller that makes a full screen presentation over itself—for example, by calling presentViewController:animated:completion:.

    • You should make sure that your apps are not using these methods to manage the layout of any subviews. Instead, they should use the view controller’s viewWillLayoutSubviews method and adjust the layout using the view’s bounds rectangle.

  • In iOS 6, the viewWillUnload and viewDidUnload methods of UIViewController are now deprecated. If you were using these methods to release data, use the didReceiveMemoryWarning method instead. You can also use this method to release references to the view controller’s view if it is not being used. You would need to test that the view is not in a window before doing this.

  • FIXED: Calling any of the attributed string drawing methods without specifying a value for the NSFontAttributeName attribute is likely to throw an exception. The workaround is to set a value for the NSFontAttributeName key before drawing or sizing an NSAttributedString object.

  • Setting values for the shadowOffset or shadowColor properties of a UILabel object, whose attributedText property contains a valid attributed string, is unsupported. Use the NSShadowAttributeName attribute of the attributed string to set the shadow instead.

  • Due to compatibility concerns, the NSBaselineOffsetAttributeName attribute is no longer supported in iOS 6.

  • The NSTextAlignmentNatural value is unsupported and will throw an exception when used with the textAlignment property of UILabel or supplied as the alignment parameter to the drawInRect:withFont:lineBreakMode:alignment: method of NSString.

  • The setContentStretch: method of UIView has been deprecated in this beta release. To achieve the same effect, use the resizableImageWithCapInsets: method of UIImage and display the image with a UIImageView.

  • The resizableImageWithCapInsets: method of UIImage effectively resizes images by tiling. As a performance optimization, it uses stretching rather than tiling when the user would not be able to tell the difference, like when a single column or row is being stretched. But in certain circumstances, one might want to actually stretch some region of an image. In iOS 6, the resizableImageWithCapInsets:resizingMode: method allows the caller to specify a tiling or stretching resizing mode.

  • The UICollectionViewLayout class has changed:

    • The class now supports the customization of the animations created during rotation. The names of methods for customizing insert and delete animations have also changed so that the same hooks can be used for rotations as well as for insertions and deletions.

    • The class has changed some method names. Specifically, decoration views are no longer referred to by "reuse identifier" but rather by "element kind." Apps that are using decoration views will need to modify their code and rebuild to accommodate this.

  • FIXED: In iOS 6, a bug was fixed where UIWebView.isLoading was set to NO before the main frame finished loading. Now, UIWebView.isLoading is set to NO when the main frame is done loading.

  • The bottom edge of a UILabel view is now different from its baseline.

    Previously, auto layout was interpreting the bottom of a UILabel to be the same as its baseline. While convenient in many cases, it caused problems if you wanted to place the top edge of one label against the bottom edge of another. In such a scenario, the bottom label would overlap the top one, and descenders from the top label could crash into ascenders from the bottom label. Now, auto layout interprets UILayoutAttributeBottom as the bottom of the text box (presuming the label is not bigger than its intrinsic content size), and UILayoutAttributeBaseline as the baseline of the text. If you have already created code for laying out labels according to the bottom or center point, your text will move around a little and you will need to adjust your constraints.

  • Apps with table views in their nib or storyboard files, and that were built using previous versions of iOS 6 beta, will require a clean build with beta 3 and newer.

  • Here are some notes regarding auto layout support for UIScrollView:

    • In general, auto layout considers the top, left, bottom, and right edges of a view to be the visible edges. That is, if you pin a view to the left edge of its superview, you're really pinning it to the minimum x-value of the superview’s bounds. Changing the bounds origin of the superview does not change the position of the view.

    • The UIScrollView class scrolls its content by changing the origin of its bounds. To make this work with auto layout, the meaning of the top, left, bottom, and right edges within a scroll view now mean the edges of its content view.

    • The constraints on the subviews of the scroll view must result in a size to fill, which is then interpreted as the content size of the scroll view. (This should not be confused with the intrinsicContentSize method used for auto layout.) To size the scroll view's frame with auto layout, constraints must either be explicit regarding the width and height of the scroll view or the edges of the scroll view must be tied to views outside of its subtree.

    • Note that you can make a subview of the scroll view appear to float (not scroll) over the other scrolling content by creating constraints between the view and a view outside the scroll view's subtree, such as the scroll view's superview.

    • Here are some examples of how to configure the scroll view:

      • Mixed approach:

        1. Position and size your scroll view with constraints external to the scroll view—that is, the translatesAutoresizingMaskIntoConstraints property is set to NO.

        2. Create a plain UIView content view for your scroll view that will be the size that you want your content to have. Make it a subview of the scroll view but let it continue to translate the autoresizing mask into constraints:

          UIView *contentView = [[UIView alloc]
              initWithFrame:CGRectMake(0,0,contentWidth,contentHeight)];
          [scrollView addSubview:contentView];
          // DON'T change contentView's translatesAutoresizingMaskIntoConstraints,
          // which defaults to YES;
        3. Set the content size of the scroll view to match the size of the content view:

          [scrollView setContentSize:CGMakeSize(contentWidth,contentHeight)];
        4. Create the views you want to put inside the content view and configure their constraints so as to position them within the content view.

          Alternatively, you can create a view subtree to go in the scroll view, set up your constraints, and call the systemLayoutSizeFittingSize: method (with the UILayoutFittingCompressedSize option) to find the size you want to use for your content view's size and the contentSize property of the scroll view.

      • Pure auto layout approach:

        1. In this case translatesAutoresizingMaskIntoConstraints must be set to NO on all views involved.

        2. Position and size your scroll view with constraints external to the scroll view.

        3. Use constraints to lay out the subviews within the scroll view, being sure that the constraints tie to all four edges of the scroll view and do not rely on the scroll view to get their size.

          A simple example would be a large image view, which has an intrinsic content size derived from the size of the image. In the viewDidLoad method of your view controller, you would include code like the following:

          UIScrollView *scrollView = [[UIScrollView alloc] init];
          UIImageView *imageView = [[UIImageView alloc] init];
          [imageView setImage:[UIImage imageNamed:"MyReallyBigImage"]];
          [self.view addSubview:scrollView];
          [scrollView addSubview:imageView];
           
          scrollView.translatesAutoresizingMaskIntoConstraints = NO;
          imageView.translatesAutoresizingMaskIntoConstraints = NO;
           
          NSDictionary *viewsDictionary = NSDictionaryOfVariableBindings(scrollView,imageView);
          [self.view addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"H:|[scrollView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];
          [self.view addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"V:|[scrollView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];
          [scrollView addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"H:|[imageView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];
          [scrollView addConstraints:[NSLayoutConstraint constraintsWithVisualFormat:@"V:|[imageView]|" options:0 metrics: 0 viewsDictionary:viewsDictionary]];

          This would give you a scroll view that resized as the view controller's view resized (such as on device rotation), and the image view would be a scrolling subview. You don't have to set the content size of the scroll view.

Safari & WebKit

  • WebKit on iOS now supports the requestAnimationFrame and cancelAnimationFrame methods in JavaScript, as described here http://www.w3.org/TR/animation-timing/.

    • Note that because the specification is still at the Working Draft state, these methods have the webkit prefix, so they are window.webkitRequestAnimationFrame, window.webkitCancelAnimationFrame.

  • The default app cache quota has been increased from 5MB to 25MB.

  • The JPEG subsampling threshold was increased from 2 MP (megapixels) to 5 MP on all supported hardware except iPhone 3GS and iPod touch (4th gen).

  • Support has been added for <input type="file"> tags in web forms. Users can upload existing photos and videos from their photo library or take a picture or video using the camera. Previously this form control was always disabled.

  • With Safari 6.0 on OS X, developers can now use the Web Inspector (web development tool) with attached iOS devices and iOS Simulator. Developers can use the Web Inspector to debug Safari and the UIWebView class in their own apps built and run from Xcode. This replaces the Debug Console banner in Safari.

  • In iOS 6 and later, web data (SQL Web Storage and LocalStorage) from a UIWebView object can be stored in a directory that will be backed up. To enable backing up this data, set the WebKitStoreWebDataForBackup key to YES in your app’s user defaults. This should be done only if your app relies on web content data that cannot be reloaded. If your UIWebView object opens links to arbitrary web content, this key should be set to NO. Toggling the value of this key will not preserve existing web view data.

  • In iOS 6 and later, Safari no longer registers for the common feed: RSS/ATOM scheme. Apps that can view those types of feeds are encouraged to register for that URL scheme.

  • WebKit no longer always creates hardware-accelerated layers for elements with the -webkit-transform: preserve-3d option. Authors should stop using this option as a way to get hardware acceleration.

  • Experimental CSS3 Flexbox support will be disabled. Please switch from using -webkit-flexbox and -webkit-inline-flexbox to -webkit-box and -webkit-inline-box.

  • As of iOS 6, embedded YouTube URLs in the form of http://www.youtube.com/watch?v=oHg5SJYRHA0 will no longer work. These URLs are for viewing the video on the YouTube site, not for embedding in web pages. Instead, the format that should be used is described in https://developers.google.com/youtube/player_parameters.

  • In iOS 6, the keyboardDisplayRequiresUserAction property was added to the UIWebView class. The property defaults to YES, which means that calling focus() on a form element will not bring up the keyboard. By changing the property to NO, a JavaScript call to focus() on a form element will focus the element and automatically bring up the keyboard.

  • As of iOS 6, calling focus() on a form element in a web app will focus the element.


 

몇일전 기사를 보고 애플 지도상에서 의 독도를 검색해봤더니;;

 

역시나 기사대로 였다;;

 

자세한 항의 방법이나 문제 제기 방법에 대한 내용이 안보이는 터라~

 

혼자 해보고 맞는 방법이다 싶어 이렇게 약소하나마 적어본다~

 

1. 우선 애플 지도에서 검색을 합니다 . 기분나쁘지만 일단 검색어를    竹島

    검색된 위치에서   竹島 >  를 터치 합니다.

 

 

 

 

2. 검색된 내용에 대한 위치 정보 및 기본 정보를 보여주는데요. 이 부분에 하단부분에 보면 문제 리포트 가 있습니다.

문제제기를 바로 이곳에서 할수있겠습니다.!! 바로 문제 리포트 터치

 

 

 

 

 

3. 어떤 문제에 대한 리포트를 할것인지를 선택하게 되어있습니다.

우리는 타케시마라는 표시가 잘못되있다는걸 문제 리포트 할것이니~

 

정보가 올바르지 않음 을 터치 한 후에 다음을 터치 합니다.

 

 

 

 

4.  Suggest corrections below ~ (아래에서 수정 내용을  제안 하라고 합니다, 즉 수정 한뒤 보내기 를 터치하란 소리~)

 

수정할 부분인

 

name 부분을 터치 후 Dokdo

 

하는김에 주소도 완벽하게 address 터치 후 Dokdo-ri, Ulleung-eup, Ulleung-gun, Gyeongbuk, Korea 를 입력

 

그리고 맨 아래에 url 을 외교통상부 독도 주소를 적어주면 좋을듯 해서 ~  http://dokdo.mofat.go.kr/ 로 수정~

 

(아이폰/아이패드시라면 제 블로그 모바일로 직접 접속후에 복사하시길 추천)

 

수정후에 오른쪽위에 보내기 터치 하시면 완료~!! (해보니 여러번해도 가능한듯 해보입니다~)

 

 

 

 

ps. 왜 한글로 독도 가 아닌 Dokdo 냐 하시는분이 있을까 싶어 ~

 

일단 한국어 아는사람중에 독도가 우리땅인거 모른 사람은 없을꺼라고 보이는게 그 이유구요 한글로 독도 이렇게 리포트하시는거야 뭐 하시는분 맘이겠죠 ㅎㅎ

 

저번에 컬투쇼에서 들어보니 독도 표기가 반크 외에 다른 지식인분들 활동 전에 5% 였고 활동 후에 겨우 30% 이게 현실이라고 하네요~

 

국력도 물론 중요하지만 우리 같은 애플 디바이스 사용자인 국민으로도 이 정도 별로 어렵지않은 문제리포트~ 할수 있으리라 봅니다.

 

개발자 버전 사용자 만이 아닌 9월 iOS6 정식때도 변화가 없다면 한국 아이폰/아이패드 유저의 단합된 능력을 보여주자구요~!

 

 

 

 

 

 

+ Recent posts

티스토리 툴바