[TIMOB-9902] TiAPI: Update Android and IOS to support new SDK available on newer versions of the platforms
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Duplicate |
| Resolution Date | 2013-03-26T20:58:43.000+0000 |
| Affected Version/s | Release 2.1.0 |
| Fix Version/s | Release 3.2.0 |
| Components | TiAPI |
| Labels | api, core |
| Reporter | Vishal Duggal |
| Assignee | Ingo Muschenetz |
| Created | 2012-07-06T12:33:07.000+0000 |
| Updated | 2017-03-21T22:43:06.000+0000 |
Description
Android API's need to be updated to post 2.2 support.
IOS needs to research new features that have been introduced in IOS6 and make sure we are IOS6 compatible
Estimate is combined for all platforms.
It is important to notice that on iOS6, several things have changed, among them: 1. The way Autorotation works has completely changed, delegating the screen orientation control to the top level window instead of a pre-configured parameter, in a way that orientation control can change during execution time. 2. Several changes on the ScrollView. 3. As Maps engine has changed from GMaps, it is important to test everything related to Maps and Geolocation on Ti running on iOS 6, even though Apple kept Map Kit API compatibility, some new things were introduced. and much more... check: https://developer.apple.com/library/prerelease/ios/#releasenotes/General/RN-iOSSDK-6_0/_index.html Support for the new Statusbar customisations and the Passbook API is a very good thing to have. I urge developers of Appcelerator to always keep looking the iOS6 release notes, even as it is in Beta as it will be available to final users in 2 months. As iOS users have a strong tendency to always upgrade, we need to have Ti working ASAP in order to keep our apps working on the verge of a new iOS release.
Deferring this into 3.2 until we have a list of individual tickets, some of which we can move back into 3.1
Release 2.1.4 included iOS 6 support. The rest of the items have been already implemented or are scheduled in related tickets. Going to mark this as a duplicate.
Closing ticket as duplicate with reference to the above comments.