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


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


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



[이슈]

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


[체크]

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

- 볼륨버튼을 조작해 보기

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




[원인]


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



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


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


[해결]

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




끝;;

'Tip' 카테고리의 다른 글

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


개요
  • 트랜드마이크로, 권환 및 데이터 탈취, 모바일 랜섬웨어 등의 기능을 수행할 수 있는 안드로이드 악성코드(GhostCtrl) 발견
     

  

주요내용

 

  • GhostCtrl 악성코드는 유명 앱(whatsapp, Pokemon GO 등)을 가장하여 악성 APK 설치를 유도하며, 사용자가 설치를 취소해도 계속해서 팝업창 생성
  1. 설치 후 아이콘을 삭제하며, com.android.engine 이라는 명칭으로 백그라운드에서 실행 및 C&C 서버와 암호화 통신
  • GhostCtrl 악성코드는 관리자 권한 탈취, 모바일 랜섬웨어 기능, 난독화를 통한 악성 루틴 은닉 기능 등 세 가지 변종이 존재
  1. 그 외에 블루투스 연결 제어, 지정한 전화번호의 문자 메시지 탈취, 암호 삭제 및 재설정, 카메라/비디오 녹화 후 C&C 서버로 전송 등 다양한 기능 수행 가능

<그림1. 모바일 랜섬웨어와 유사한 기능을 수행하는 코드>
모바일 랜섬웨어와 유사한 기능을 수행하는 코드

 

시사점

 

  1. 모바일 OS 최신 업데이트 및 중요 데이터의 주기적인 백업 필요
  • 앱 다운로드 시 요구 권한을 확인하여야 하며, 리뷰를 참조한 후 설치하는 것을 권장
     


[출처]
1. TrendMICRO,, “Android Backdoor GhostCtrl can Silently Record Your Audio, Video, and More”, 2017.7.17.
2. BLEEPINGCOMPUTER “GhostCtrl Is an Android RAT That Also Doubles as Ransomware”, 2017.7.17.



작성 : 침해대응단 탐지1팀


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


출처 : 보호나라 http://boho.or.kr




아이네임즈에서 호스팅 신청시, 


워드프레스 유료 테마 88종 과 특정 플러그인을 무료로 사용할 수 있게끔, 


설치 지원 한다해서 슬쩍 봤습니다.




아시다 시피, 


워드프레스는 웹페이지 제작 및 관리를 위한 프로그램 중의 하나 이고,


서울시청 홈페이지 제작시 사용 되었다는 것으로 많이 유명해졌었죠..


(아주 오래전 일이지만요..)



이제는 


반응형 홈페이지 제작이라 하면, 기본적으로 워드프레스를 많이 떠올리고,


많은 에이전시에서도, "땡큐" 하게 사용하고 있지요..






사용 제한은 아래와 같은데, 


아이네임즈 호스팅 서비스를 사용하는 기간 내에는 


제공하는 유료 테마를 제한 없이 무료로 사용 할 수 있다는 것 같네요..



제한 조건 중에 하나가 리눅스 I Basic  이상 상품 이라길래, 


호스팅 상품이 비쌀줄 알았는데,


생각보다는 저렴한 듯 하네요.. (제 기준에..)








어떤 테마가 있나 보니 고르다가 지칠수도 있을 만큼 좀 많네요.. (개인적으로 이런거 다 보는거 귀찮아 합니다..)


각 테마별로 미리 보기도 제공하니, 시간될 때 천천히 훑어 봐야겠네요..







이미지는 주지 않는다 하니, 


테마만 셋팅 되는듯 하고, 나머지는 직접 작업을 해야 하는 것인듯..


설치 하면 위와 같은 사이트가 뜨기를 원하시는 분들께는 맞지 않을수도 있겠네요..





또 다른 서비스가 뭐 있나.. 훑어 보니..


"스마트빌더" 라는게 있네요..


기본이 아이네임즈 호스팅 서비스 중 특정 상품을 이용해야 하는걸 보니


이것도 호스팅 상품에 해당되는듯 하네요..

-빌더형이 다 그렇지요 뭐..




데모체험하기를 들어가보니..


제공 템플릿이 아까 워드프레스 88종 보다.. 훨~씬 많습니다.. 헐!!


하나하나 보는건 또 다음으로 패쓰! (위에서 쓴것처럼.. 귀찮아 합니다..)






선택 하기 눌러 보니


이거는 미리보기에 있는 페이지가 "풀셋팅"이 되어서 나오는 모양을 보아하니..


아무것도 모르고, 워드프레스에 들이대는거 보다는 이게 훨씬 쉬워보이긴 합니다.

 -아무래도 틀이 잡힌 상태에서 뭔가하는게 더 쉽고, 컨텐츠만 갈아 끼면.. 바로 완성이네요..





드래그앤드롭 방식에.. 




반응형에..




특히 매뉴얼을 문서로 주는게 아니라 


동영상으로 제공하니 따라 하면, 해볼만하겠네요 ㅎㅎ




비용도 뭐 저정도면 쏘쏘.. 하네요.. (이것도 본인 기준임)




다음에 워드프레스 쓸 일 있거나,


누군가가 간단하게 홈페이지 만들어 달라 하면,


아이네임즈 호스팅 신청해서 만드는것도 나쁘지 않을듯 하네요..




한동안 바쁘단 핑계로 블로그를 관리 못하는 와중에 티스토리측에서 DNS 관련한 설정변경 작업이 진행되었는데...

 

공지된 내용으로 DNS 설정 내용을 변경 해두었으니 정상적으로 블로그가 돌고있을꺼라 생각했는데!!!

 

블로그가 뜨지 않고...티스토리 404 페이지만 뜨고있음을 발견~!!

 

 

 

이유는 대체 티스토리가 공지도 없이 왜 그랬는지 전혀 이해 할수는 없지만..

 

아래 그림의 2번 항목이 초기화 되고 내 블로그의 기본주소인 http://skyand.tistory.com 으로 설정되어 있었다....

 

2차 주소를 클릭하여 원래 주소인 skyand96.com 을 설정하고 저장 하고 나니 정상적으로 블로그가 뜬다...

 

대체 왜 이걸 초기화 해버린걸까... 왜 공지사항에는 이거에 관련된 내용을 고지를 안한거지......

 

 

자세한 설정 방법은 글 맨 하단에 요약 본 참고

 

 

 

 

[티스토리에서 제공하는 기본주소를 사용하지 않고 본인이 보유한  도메인으로 연결해서 사용하는 경우]

 

1. 도메인 을 구매한 레지스트라 의 사이트에서 네임서비스 설정을 변경해줘야 한다.

 

- 앞으로도 이런식의 아이피 변경이 될것을 생각한다면  CNAME 으로 도메인을 설정하는게 좋다. ( host.tistory.io 혹은 blog.tistory.com )

=> skyand96.com CNAME blog.tistory.com

=> www.skyand96.com CNAME skyand96.com

 

 

참조 : 아래 그림은 싸이팩(cypack.com) 의 부가서비스 > 네임서비스 화면 => 싸이팩에서는 버튼 클릭으로 바로 설정 가능

 

 

 

2. 반드시 블로그 관리 > 기본정보 > 주소설정 부분에서 2차 주소 로 본인의 사이트 주소가 설정되어있는지 체크

 

'Tip' 카테고리의 다른 글

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

랜섬웨어(Ransomeware) 란?


사용자의 피시의 주요 파일을 암호화 하여 해당 파일을 사용 불가하도록 한뒤 해당 파일을 인질로 삼아 돈을 요구하는 형태의 악성코드


중요한 파일을 보관하고 있는 상황에서 해당 공격을 받은경우 해당 파일을 사용할수 없는 심각한 상황을 맞게 된다.


돈을 지불하여도 암호화된 파일을 복구 해준다는 보장도 없고, 백신을 이용해 랜섬웨어를 제거한다고 해도 이미 암호화된 파일은 복원되지 않는다.


암호화된 파일을 복호화 하기 위해서는 암호화 시에 사용한 키가 필요한데 대부분 이 키를 공개하거나 비용을 지불하여도 받을 확률은 거의 없기 때문이다.


최근에는 심지어 한국 피시들을 노리는 번역된 비용 요구 까지 보이고 있어 주의가 필요 하겠다.


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


랜섬웨어를 예방하기 위한 방법


- 운영체제 를 비롯한 모든 프로그램의 최신 업데이트

- 백신 은 필수로 사용하고 역시 최신 업데이트 상태를 유지 하며 주기적인 검색 스케쥴 필요

- 광고가 많거나 신뢰도가 떨어지는 사이트는 아예 방문하지 않는게 상책

- 3번의 경우가 불가피 하다면, 주요 공격 방법인 플래쉬 를 끄는것도 방법

- 이도저도 힘들다면 크롬을 사용 (알려진 악성코드는 사전에 차단하여 사이트 접속을 막아줌)

- 수신 메일 확인시 첨부파일 함부로 열어보지 않기 (열어볼필요가 있다면 다운로드후 백신을 통해 검사 한뒤에 확인

- 중요 문서는 수시로 백업하거나 일기전용 혹은 폴더를 보안 구역에 따로 배치( 백신/보안툴 에 기능이 있는 경우)


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



여러 방법이 있지만 요즘 잘 안쓰는 플래쉬를 끄는 방법 만으로도 최근 클리앙, 뽐뿌 등 광고를 통한 랜섬웨어 유포에서 조금이나마 안심 할 수 있다.


1. 익스플로러 에서 플래쉬 끄기


- 우측 상단의 톱니바퀴 (익스11) 클릭

- 메뉴중 '추가기능 관리' 선택





-  추가기능 관리 에서 플래쉬 (Shockwave Flash Object) 항목을 클릭하여 선택한뒤 우측 하단의 '사용 안함' 클릭




- 이 후 플래쉬기 필요한경우 다시 플래쉬를 선택한뒤 사용함 클릭해주면 사용할수 있다.




2. 크롬 에서 플래쉬 플러그인 끄기


- 크롬 창을 연뒤에 주소창에 'chrome://plugins' 을 입력 하면 아래와 같은 크롬 플러그인 설정 페이지를 볼수있다.

- 플러그인 중 플래쉬 (Adobe Flash Player) 아래 사용 중지 를 클릭하면 플래쉬 플러그인 사용중지가 가능하다.



 

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

3. 안랩 랜섬웨어 무료 복구툴

- CryptXXX 랜섬웨어 부분 복구툴 
: 다운로드 ( cryptxxx_decryptor_3.x.exe ) 


- CryptXXX 랜섬웨어 복구툴
:  다운로드  (cryptxxx_decryptor.exe )









무료 돌잔치 초대장 만드는 방법!


달팽 가입 http://dalpeng.com


회원가입 하고, 로그인 하고 신청하기 들어가서 '무료 신청하기' 클릭하면

무료형으로 청첩장, 돌잔치 사용 가능하니 '돌잔치' 클릭한 뒤 원하는 초대장 주소 선택하고 사용!


그러면 이런 초대장 빌더 페이지가 노출되고,

각 정보 입력 부분에 정보 입력하면 손쉽게 무료 모바일 돌잔치 초대장 완성.


무료로 돌잔치 스킨은 1개만 사용 가능.


아기 사진 넣어주고, 초대장 제목 넣어주고~


돌잔치 열리는 날짜와 장소, 그리고 초대장을 돌릴 분들께 노출되는 초대글까지 입력 완료

엄마, 아빠 이름까지 넣을 수 있으니 좋은듯-하지만 난 안넣음.



아이 이름 넣는 프로필 부분. 유료형 기능인데 이름은 유료형이 아니어도 노출이 된다고-

좌측에 보이는 미리보기로 보니 '첫 생일파티에 초대합니다' 라는 문구가 '시후의 첫 생일파티에 초대합니다'로 변경되어 있음.


사진은 있는거 다 넣고~


동영상도 유투브에 있는 영상 삽입이 가능한데, 소스 퍼오기 이런거 아니고 깔끔하게 영상 주소 삽입하면 되는듯


이제 마지막 돌잔치 초대장 카카오톡으로 보낼 때 노출되는 문구 입력까지 하면 무료 돌잔치 초대장 완성!

쉽네..금방 금방 만들 수 있으니 좋네.


만든건 거의 15분 이내였던듯-

무료형 돌잔치 초대장도 나쁘지 않은데, 유료형 초대장이 예뻐서 유료형으로 결제할까 말까 고민하게 만드는듯

아, 무료형 돌잔치 초대장은 스킨이 1개인것도 있지만 사용기간이 초대장 만들고 나서 1개월까지만 가능하니

아기 돌잔치 20~25일 전 만들어서 카카오톡이나 문자로 돌리면 되겠다 ㅋㅋㅋㅋ






구글맵 API 를 기본으로 사용하는경우 일본해(동해) 가 기본으로 표기되어진다...


단순히 구글맵을 한국 지역화 하는 방법만으로도 이를 정상적으로 수정하여 사용 할 수 있다.


구글은 안해줘도 우리가 할수있다면 우리가 사용하는 지도 만이라도 수정해서 사용해야하겠다.


보통 구글 API 사용시 상단에 


 <script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?sensor=false"></script>


요 형태의 주소를 넣게되는데, 이때 이 주소 뒤에 지역화 &region=KR 값을 추가해주면 된다.


 <script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?sensor=false&region=KR"></script>





끝!



아베스트 (Avast) 백신 제거 방법




avastclear를 사용하여 소프트웨어를 제거하는 방법


제어판의 프로그램 추가/제거를 사용하여 Avast를 제거할 수 없을 때가 있습니다.

이런 경우 제거 유틸리티인 avastclear를 사용하면 됩니다.


1. 데스크톱에 제거 유틸리티 avastclear.exe 를 다운로드합니다.


- 다운로드 링크 : http://files.avast.com/iavs9x/avastclear.exe


2. Windows를 안전 모드로 시작합니다.


3. 제거 유틸리티를 엽니다(실행).


4. 기본이 아닌 다른 폴더에 Avast를 설치했다면 찾으십시오. 참고: 선택한 폴더의 모든 내용이 삭제되므로 주의하십시오.


5 .제거를 클릭합니다.


6 .컴퓨터를 다시 시작합니다.

'Tip' 카테고리의 다른 글

티스토리 블로그 안뜰때  (0) 2016.12.19
아베스트 삭제 방법  (0) 2015.11.19
모바일웹 테스트  (0) 2015.08.11
크롬 에서 사이트들이 깨져 보일때 :: net::ERR_CACHE_READ_FAILURE  (0) 2015.02.03

개발자 버전인 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




watchOS SDK Release Notes for watchOS 2

Important:
This is a preliminary document for an API or technology in development. Apple is supplying this information to help you plan for the adoption of the technologies and programming interfaces described herein for use on Apple-branded products. This information is subject to change, and software implemented according to this document should be tested with final operating system software and final documentation. Newer versions of this document may be provided with future betas of the API or technology.
Contents:

Introduction
Bug Reporting
Notes and Known Issues
Introduction
watchOS SDK 2.0 provides support for developing watchOS apps. It is packaged with a complete set of Xcode tools, compilers, and frameworks for creating apps for watchOS. These tools include the Xcode IDE and the Instruments analysis tool, among many others.

This version of watchOS is intended for installation only on devices registered with the Apple Developer Program. Attempting to install this version of watchOS in an unauthorized manner could put your device in an unusable state.

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 watchOS SDK 2.0 in the Apple Developer Forums: https://forums.developer.apple.com/community/pre-release/watchos-2-beta.

Notes and Known Issues
Activation Lock
Note
Activation Lock is enabled on your Apple Watch if you have Find My iPhone enabled on your iPhone.

Connectivity
Note
Enable "Install All Apps" in Watch.app -> General -> App Install for WatchConnectivity to work correctly during Build and Run cycles.

Keychain
Note
Keychain items created on an Apple Watch are not viewable on an iOS device.

Maps
Known Issues
If you do not see map tiles load on the Watch Simulator, launch the Maps app in the iOS simulator first. After that, map tiles will load.
The MKMapItem method openInMapsWithLaunchOptions: does not work.
WatchKit
Notes
WKInterfacePicker has a new method to remove focus.
The method focusForCrownInput has been renamed to focus.
Installing a WatchKit 1.0 app with an Xcode prior to 7.0 requires that "Automatic App Install" be enabled in the Watch app under General -> App Install.

Copyright © 2015 Apple Inc. All rights reserved. Terms of Use | Privacy Policy | Updated: 2015-09-09

'iOS' 카테고리의 다른 글

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




애플 워치도 기존 아이폰과 동일하게 베타 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

모바일웹을 직접 기기에서 일일이 모두 테스트하기란 생각보다 쉽지 않다


우선 모든 기기를 구할수 없다는게 가장 큰 이유 이기도 하다.


과거 포스팅에서 관련 내용으로 몇번 소개했던 프로그램으로도 가능하지만 최근에 사용하는 두가지 방법을 소개하고자 한다.


> 다음 트로이 ( Troy ) - 모바일웹의 사이즈만 테스트 한다면 추천

- 단순히 모바일 기기의 사이즈만 규격화 한 테스트만 가능하다.

- 하지만 여러기기 에대한 정리가 잘되어있고, 멀티스크린 모드로 (모니터만 크다면) 많은 기기를 동시에 볼수있다.

- 제법 국내 지원 기기들을 지원(사이즈만..)한다.

- 물론 트로이는 반응형 웹 테스터 이다  그리고 약 2년전에 다음 labs 에서 제공한 서비스 이다.



1. 우선 트로이 접속 ( http://troy.labs.daum.net )


- 접속하면 아래와 같은 화면을 볼수있다. 여기서 위에 주소란에 원하는 사이트 주소를 입력하고 좌측에 디바이스를 선택만 하면 

바로 우측공간에서 확인이 가능하다.

- 이때 좌측 상단에 멀티스크린모드 스위치를 켜주면 여러 디바이스를 동시에 확인해 볼수 있다.

직접 user_agent 를 적용하거나 수정 할수 있는 기능은 없어 내 블로그 주소를 넣었지만 모바일 페이지로 보여지지는 않고 있다;;




2. 상세 기능 사용법


- 1. 회전 을 클릭하면 기기가 가로 형태로 변경되는것을 볼수있다.

- 2. 주소창보이기 는 클릭시 실제 기기내 브라우져의 주소창을 재연하여 반응형 구현 내용을 디테일하게 확인해 볼 수 있다.



총평 : 반응형 사이트를 운영중이라면 여러 기기에서 동시에 테스트를 진행해 볼수 있는점은 장점 이라 하겠다.



> 크롬 카나리 ( Chrome Canary ) - 추천


- 크롬은 크롬이지만 '강심장에게만 권장', '야간업데이트', '병렬 설치' 등의 카피로 소개 하고 있는 크롬의 카나리 이다.

- 사용중인 크롬 정식 버전과 '병렬 설치' 가능하다 ( 같이 쓸수있다는 말을 참 어렵게 표현한  구글..

-  위에서 소개한 다음 트로이와 는 달리 user_agent 를 직접 반영한 테스트가 가능하며, 통신망 을 선택하여 실제 기기에서의 모바일웹페이지의 상태를 제법 유사하게 테스트 해볼수 있다.

- 트로이에 비해 기기 종류는 다양하진 않지만~! user_agent 수정과 디바이스 사이즈를 직접 조정 할수 있어 테스트 하려는 기기의 스팩만 안다면 얼마든지 테스트 해볼수 있다.


1. 우선 크롬 카나리 다운로드 페이지 에서 프로그램을 다운로드 하여 설치 한다 (설치 과정은 생략)

: https://www.google.co.kr/chrome/browser/canary.html



2. 사용방법

- 우선 설치후 카나리를 실행하면 일반 크롬의 영문버전으로 밖에 보이지 않는다.

F12 를 눌러 개발자 도구를 열고 아래 그림에 왼쪽 맨하단에 파란색 스마튼폰 모양을 클릭하면 아래와 같은 UI 를 볼수있다.

- UI가 단순 하여 대충 봐도 다 아시리리 생각된다.




3. 상세 기능 사용법

- 우선 Device 옆 셀렉트박스를 클릭해보면 여러 디바이스가 정의 되어있다. 원하는 기기를 선택하면

- 내용은 해당기기의 사이즈로 설정되고 UA 에는 해당기기의 일반적인 user_agent 가 자동으로 작성되고, 실제 기기의 접속 화면과 같은 모습을 볼수있다. ( 즉, user_agent 로 구분하여 사이트를 보여주는 경우에도 실제 구동 화면을 확인할수 있다.)

- Portait : 카나리 역시 가로형 변형 모드가 존재한다.




- Network 는 예상하는것처럼 실제 통신사 에서 제공할법한 속도를 제현 하여 테스트 해볼수 있다 ( 3G, 4G, wifi 등)

그외에 하단에 Screen 에서는 원하는 사이즈를, UA 에서는 원하는 실제 user_agent 를 설정하여 테스트 해볼수 있다.

- 그외에 아래 기기 모양에서도 가로 세로르 직접 수정 할수도 있다.


- 조금더 디테일한 기기 테스트도 가능하다. 스크린샷에서는 안나왔지만 하단부를 좀더 열어보면 아래와 같은 화면을 볼수있다.

- 특히 Emulation > Sensors 에서는 터치스크린, GPS 는 물론 스마트폰 기울기 까지 테스트가 가능하다 !

- Rendering 에서도 Show paint rectangles , Show composited layer borders , Show FPS meter , Enable continuous page  repainting , Show potential scroll bottlenecks 등의 내용을 적용할수 있다.



총평 : 크롬 카나리 에서는 제법 실제 기기와 비슷한 많은 테스트가 가능하다! 적극 추천!


끝~


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

watchOS SDK Release Notes for watchOS 2 Beta 4

Contents:

Introduction

watchOS SDK 2.0 beta provides support for developing watchOS apps. It is packaged with a complete set of Xcode tools, compilers, and frameworks for creating apps for watchOS. These tools include the Xcode IDE and the Instruments analysis tool, among many others.

This version of watchOS is intended for installation only on devices registered with the Apple Developer Program. Attempting to install this version of watchOS in an unauthorized manner could put your device in an unusable state.

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 watchOS SDK 2.0 in the Apple Developer Forums: https://forums.developer.apple.com/community/pre-release/watchos-2-beta.

Autosubmission of Diagnostic and Usage Data

Location Services, Diagnostics and Usage, and Contacts settings are shared between Apple Watch and iPhone. 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 on your iOS 9 iPhone.

Notes and Known Issues

Activation Lock

Note

Activation Lock is enabled on your Apple Watch if you have Find My iPhone enabled on your iPhone.

Apple Pay

Fixed in Beta 4

Apple Pay is not functional.

Connectivity

Known Issue

Your app may crash when using NSNumber and NSDate objects with the WCSession API.

Workaround: Convert an NSNumber or NSDate object to a string before calling WCSession APIs. Do the opposite conversion on the receiving side.

Contacts

Known Issue

Contact syncing doesn’t work in Simulator.

Complications

Fixed in Beta 4

Known Issues

File Transfers

Fixed in Beta 4

File transfers fail from Watch to iPhone.

Glances

Fixed in Beta 4

You may not see your glance appear while debugging in Simulator or on a device.

Known Issues

Glances become unusable when you have attached with a debugger.

Haptics

Fixed in Beta 4

Haptic feedback does not work with this beta.

Keychain

Note

Keychain items created on an Apple Watch are not viewable on an iOS device.

Notifications

Fixed in Beta 4

The following callbacks in WKExtensionDelegate have not yet been implemented.

  • - (void)didReceiveRemoteNotification:(NSDictionary *)userInfo;

  • - (void)didReceiveLocalNotification:(UILocalNotification *)notification;

Privacy

Fixed in Beta 4

If you disable the "Fitness Tracking" privacy setting on the companion device for your app, the app on the Watch side will still receive motion updates.

Siri

Known Issue

When invoking Siri by pressing the Digital Crown from the watch face, Home screen, or over an app, you may see words that you did not speak added to the Siri request.

Workarounds:

  • Use Hey Siri instead of the Digital Crown to trigger Siri.

  • Trigger Siri using the Digital Crown with Siri already in the foreground.

Watch App

Known Issues

  • Pairing iOS 9 beta 3 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.

  • Tapping Cancel does not work in the iForgot work flows in Watch Setup Assistant.

WatchKit

Known Issue

Some apps that run in Simulator may fail to launch on device.

Note: If you see this, please file a Radar so that we can follow up to obtain logs.


'iOS' 카테고리의 다른 글

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
iOS 8.4 업데이트  (0) 2015.07.01

세상에 없던 초대장

보내기만 하고 끝이었던 초대장이 아니라
이제는 친구들 지인들과의 커뮤니케이션이 가능한 초대장,
예식이 끝나도 갤러리 앨범, 방명록에서 소식을 전하는 초대장

01.
언제 어디서든
내용 및 스킨 수정 가능

신청 즉시 언제 어디서든 누구나 빠르고 쉽게 만들 수 있으며 사용 기간 중에는 언제든지 초대장 관리에서 수정이 가능합니다.

02.
PC,모바일,태블릿
어떤 화면이든
자유자재로 알맞게

달팽에서 제공하는 모든 초대장은 반응형 스킨으로 어떠한 기기에서든 자유자재로 알맞게 형태가 맞춰집니다.

03.
보내기만 하고 끝이었던 초대장이 아니라
친구들 지인들과의
커뮤니케이션이 가능

비회원 및 SNS계정으로 로그인도 할 수 있습니다. 갤러리 사진이나 이모티콘으로 글만으로 모자란 마음을 전하며, 그 내용이 특정 SNS로도 연동됩니다.

04.
초대장에서 버튼만 누르면
네비로 바로 연결

네비게이션앱(김기사,올레 내비)을 연동하여 초대장의 네비게이션 버튼만 누르면 약도의 장소로 바로 길찾기 안내가 시작됩니다.

05.
문자나 카카오톡에서
이미지 전송으로
스미싱 걱정없이!

단순히 초대장 링크만 보내지 않고 이미지를 함께 전송하여 스미싱 등의 불필요한 오해를 줄일수 있습니다.

06.
갤러리 사진을 더욱 즐겁게
볼 수 있는 사진 댓글 기능

모바일 청첩장&돌잔치 모바일 초대장의 갤러리 사진에 댓글을 달 수 있습니다.

07.
다양한 이모티콘으로
커뮤니케이션을
더욱 풍성하게

다양한 이모티콘으로 기분을 표현할 수 있습니다. 댓글에 재미요소가 더해집니다.

08.
합리적인
달팽 비즈니스 상품
사업에 시너지를

달팽 비즈니스 상품으로 효율적인 모바일 초대장 서비스를 제공하실 수 있습니다.
모바일 청첩장, 돌잔치 모바일 초대장

09.
스킨의 한계를 뛰어넘어
청첩장과 돌잔치 스킨
모두 사용 가능

청첩장과 돌잔치 스킨 모두 선택을 할 수 있어 연장만으로도 유용하게 사용하실 수 있습니다.

당신의 소중한 날을 위한 특별한 초대

어떤 의미로 전하시겠습니까?

달팽 바로가기 >

iOS SDK Release Notes for iOS 9 Beta 3

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

Known Issue

Lightning video dongles don’t work with this beta.

Activation Lock

Fixed in Beta 3

Your iPhone may indicate that Activation Lock is turned on for your Apple Watch when it is not.

App Extensions

Known Issue

Debugging an action or sharing extension can cause the extension to be missing in the UIActivityViewController object.

Workaround: Go to the More list and go back to show the extension again.

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

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

Known Issues

  • Attempting to create a new Apple ID via Game Center may cause a crash.

  • 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

  • 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.

  • If you enter an incorrect verification code for a two-factor authentication account in Setup Assistant, it may hang.

    Workaround: Press the Home button and go back to start setup again.

  • During Setup Assistant, tapping Cancel on the prompt that prompts you to enter the code for two-factor authentication will result in getting stuck at the login screen.

    Workaround: Press the Home button and go back to start setup again.

  • Apps that use app-specific passwords cause multiple notifications if your account uses two-factor authentication.

    Workaround: Disable the app in this beta.

Audio

Known Issue

The OpenAL framework is not available in this beta.

AVFoundation

Notes

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

    To minimize power usage, set this property to NOfalse 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 currentAVPlayerItem (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 underlyingAVPlayer object’s current item using replaceCurrentItemWithPlayerItem:.

  • The AVPictureInPictureController interface and the cancelPictureInPicture method are deprecated.

Calendar

Fixed in Beta 3

Calendar Time to Leave alerts may not be sent.

Camera

Known Issue

You can’t take photos in the Camera app using the side volume buttons with this beta.

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.

FaceTime

Fixed in Beta 3

In this beta, FaceTime calls do not connect on iPhone 6, iPhone 6 Plus, or iPad Air 2.

Family Sharing

Known Issues

  • Adding a family member inline fails.

    Workaround: Use invite to add family members.

  • Ask To Buy notifications don’t respond when tapped.

File Providers

Known Issue

On certain devices, the Document Picker is not displayed. Instead, you just see a white screen.

Foundation

Note

  • 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.

GLKit

Known Issue

GLKMesh and GLKMeshBuffer objects initialize incorrectly in this beta, which limits the use of GLKit with Model I/O.

Handoff

Known Issue

Handoff does not work with an iOS 9 device that does not have a passcode set.

HealthKit

Known Issue

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

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.

HomeKit

Fixed in Beta 3

  • Accessories that support multiple communication paths to HomeKit may appear duplicated.

  • Location-based event triggers do not work in Simulator.

  • After using HomeKit accessories or developing with the HomeKit framework, backing up to iTunes will result in an unrestorable backup.

iCloud Backup

Fixed in Beta 3

If you have two-factor authentication enabled, signing into your iTunes account while restoring from an iCloud backup may get stuck sending your verification code.

Known Issue

In rare cases, restoring from an iCloud backup will not restore your applications.

Workaround: In Settings > General > Reset, choose Erase All Contents and Settings, and then re-attempt the restore.

iCloud Drive

Fixed in Beta 3

Tapping an iCloud Drive document in search results doesn't do anything.

Instant HotSpot

Fixed in Beta 3

Some devices crash on connection to Instant Hotspot.

Keyboards

Fixed in Beta 3

There are display issues with QuickType suggestions in share sheets.

Note

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

Known Issue

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

Keychain

Fixed in Beta 3

Under certain circumstances, when enabling iCloud keychain on an OS X El Capitan or iOS 9 system using the iCloud Security Code, you may see “incorrect security code” or “could not set up iCloud keychain” even if you’ve entered the correct security code and SMS verification code.

Known Issues

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

    Workaround: Approve from another device.

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

    Workaround: Re-enable iCloud Keychain.

  • 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.

    Workaround: Log out of iCloud, log back into the account, and enable iCloud Keychain.

  • 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.

Localization

Fixed in Beta 3

For devices on which English is not the default language, some content may appear in English instead of the expected language.

Maps

Fixed in Beta 3

MapKit’s MKDirections do not get directions or ETA responses from MapKit in this beta.

Mail

Known Issue

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

Messages

Known Issues

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

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

MetalKit

Known Issue

MTKMesh and MTKMeshBuffer objects initialize incorrectly in this beta, which limits the use of MetalKit with Model I/O.

Music

Fixed in Beta 3

The Radio tab is not available in the Music app.

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.

  • It may not be possible to Love an album or playlist.

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

  • The Apple Music signup screen may not display correctly.

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)

Phone

Known Issues

  • Call history may be lost upon upgrade to this beta.

  • Voicemail may be unavailable after an erase install.

    Workaround: Reboot the device.

Photo Booth

Known Issue

Photos taken with Photo Booth are not saved.

Photos

Fixed in Beta 3

After restoring from iCloud backup, photos not stored in iCloud Photo Library fail to display thumbnails.

Podcasts

Fixed in Beta 3

If you change the media type of content in iTunes to "podcast episode," and then sync those podcasts, the Podcast app will crash on launch.

Safari

Notes

  • “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, seeHandoff Programming Guide and Shared Web Credentials Reference.

Known Issue

If you use Autofill on iPad, passwords may not be automatically entered into login fields.

Workaround: Manually input the text. Your passwords can be found in Settings > Safari > Passwords.

Search

Fixed in Beta 3

  • Tapping a Mail message, Maps favorites, Note, or Message in search results does not open the app on some devices.

  • When submitting an activity to be searchable with NSUserActivity, the metadata (attributeSet) does not get added to the index. The title and keywords property are the only activity metadata added to the index.

Settings

Fixed in Beta 3

  • You may see a black screen when trying to add Google or Yahoo accounts.

  • CoreSpotlight items indexed with description don't display the description in Search.

Known Issues

Third-party app settings sometimes do not appear in Simulator.

Setup Assistant

Fixed in Beta 3

iForgot links don’t work in Setup Assistant.

Siri

Known Issue

Siri Eyes Free may not work in this beta.

SpriteKit

Fixed in Beta 3

containsNode: and containedNodeSet do not work in this beta.

Spotlight

Known Issues

  • Tapping a Mail message, Maps favorites, Note, or Message in search results does not open the app on some devices.

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

Telephony

Known Issue

After purchasing a cellular data plan on an iPad, it may display an alert that indicates the plan has expired.

Workaround: Wait a few minutes, then toggle airplane mode.

UIKit

Fixed in Beta 3

UIModalPresentationPopover style doesn't update its barButtonItem anchor position when the window is resized.

Notes

  • 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 atUILayoutPriorityFittingSizeLevel) 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 settranslatesAutoresizingMaskIntoConstraints to NOfalse 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 NOfalse.

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

    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 & 3 and can result in unsatisfiable-constraints logging and broken layout.

    So on 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 on 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 sendinglayoutIfNeeded, 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 as UISimpleTextPrintFormatter, UIMarkupTextPrintFormatter, UIWebViewPrintFormatter, or theUIViewPrintFormatter 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 ofUIPrintPageRenderer has been updated to call drawPageAtIndex:inRect: multiple times with potentially different page sizes and margins. Various methods onUIPrintPageRenderer 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.

Watch App

Known Issues

  • Pairing iOS 9 beta 3 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.

  • Tapping Cancel does not work in the iForgot work flows in Watch Setup Assistant.

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' 카테고리의 다른 글

애플 watchOS 2 릴리즈 노트 베타4  (0) 2015.08.03
iOS 9 Beta 3 Release Notes  (0) 2015.07.10
iOS 8.4 업데이트  (0) 2015.07.01
iOS 9 릴리즈 노트 구글 번역본  (0) 2015.06.09

대게 p2p 를 통해 배포 된뒤 감염된 피시에 이메일 주소록을 탈취하여 발송 됩니다.


정상적인 첨부파일 형태로 발송되며 해당 파일을 열면 감염시키고 전파시키는 형태를 보입니다.


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

램섬웨이 대응 조치 권장 사항


1. 재부팅 후 f8 눌러서 윈도 부팅 옵션을 고름


2. 안전모드 with 네트워크로 부팅


3. 구글로 trendmicro cryptolocker removal tool 검색하거나 다음 링크에서 제거 툴 다운로드


http://www.trendmicro.co.kr/kr/security-intelligence/anti-threat-toolkit/


출처 : 한국트렌드마이크로 엔드포인트보안팀

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

트렌드마이크로 위협 제거 툴이란?

트렌드마이크로 위협 제거 툴(Trend Micro Anti-Threat Toolkit)은 사용자의 컴퓨터가 온라인뱅킹 정보탈취 악성코드인 P2PZeus 및 파일 암호화 후 몸값을 요구하는 악성코드인 CryptoLocker에 감염되었는지 검사하고 위협 발견시 제거할 수 있는 온라인 보안 도구입니다.

위협 제거 툴 사용 방법

시스템이 32비트 또는 64비트인지 확인 후, 위 다운로드 버튼을 클릭하여 파일을 다운로드 받습니다.
Zip 파일의 압축 해제 후, 실행파일을 실행하면 아래와 같은 화면이 나타납니다.
‘Scan Now’를 클릭하면 컴퓨터가 악성코드에 감염되었는지 검사할 수 있습니다.


악명높은 악성코드 P2PZeus와 CryptoLocker란?

P2PZeus와 CryptoLocker는 전세계 수만 명의 온라인뱅킹 이용자들을 대상으로 비밀번호와 계정정보를 탈취하여 돈을 요구하는 악성코드입니다. 영국에서만 15,500대의 컴퓨터가 감염된 것으로 추정되고 있고 수억 파운드의 불법 송금이 이루어진 것으로 알려져 있습니다. 이 두 악성코드는 근래에 가장 많은 수의 피해자들을 낳으며 악명을 떨치고 있습니다.

P2PZeus와 CryptoLocker의 동작 방식은 의외로 간단하고 효과적입니다. P2PZeus는 이메일을 통해 배포되는데, 감염된 컴퓨터에서 견적서나 이력서와 같은 정상파일을 가장한 첨부파일로 실제 연락처에 있는 계정들로 이메일을 발송합니다. 이메일을 받은 컴퓨터에서 해당 첨부파일을 열게 되면 다시 감염이 이루어지는 방식으로 확산되고 있습니다.

P2PZeus는 컴퓨터 내에 잠복하고 있다가 이용자가 온라인뱅킹을 이용하면 그 정보를 탈취합니다. P2PZeus는 정보 탈취 외에도 CryptoLocker를 컴퓨터로 불러들여 이용자의 컴퓨터 내의 정보를 불법적으로 암호화하고 이용자에게 팝업을 띄워 타이머를 보여주면서 시간 내에 돈을 내도록 협박합니다. 영국에서 발견된 메시지에는 1 비트코인, 약 200~300파운드를 요구하고 있는 것으로 밝혀졌습니다.

     
  그림1. CryptoLocker는 사용자의 중요한 파일이 암호화되었다는
내용의 바탕화면을 보여준다.
  그림2. 이 파일들을 해독하고 다시 액세스 하기 위해서는
프라이빗 키를 구입하도록 유도한다.
 

영국에서는 NCA를, 미국에서는 FBI를 필두로 진행되고 있는 이 두 악성코드와의 전쟁은 감염된 컴퓨터를 파기하여 감염된 컴퓨터 사이의 통신을 막음으로써 피해를 줄이고 있는 실정이나 사법당국 홀로 막아내기에는 역부족인 상태입니다. 이에 사법당국은 이용자들로 하여금 컴퓨터의 운영 시스템과 각종 프로그램을 업데이트하고 반드시 보안 프로그램을 설치하고 검사를 진행하기를 권고하고 있습니다.

이 악성코드에 대응하기 위해 트렌드마이크로는 무료로 툴킷을 제공하고 있습니다. 이 툴킷을 컴퓨터에서 실행하면 위 악성코드가 컴퓨터를 감염시키기 전에 위협을 제거할 수 있습니다.

 

이 업데이트에서는 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

+ Recent posts

티스토리 툴바