[TIMOB-26951] Android: Target API Level 29 (Android Q) by default
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | None |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2019-10-30T14:59:41.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 8.3.0 |
Components | Android |
Labels | android, build, target |
Reporter | Joshua Quick |
Assignee | Joshua Quick |
Created | 2019-03-29T20:43:05.000+0000 |
Updated | 2019-10-30T14:59:41.000+0000 |
Description
*Summary:*
When building for Android, Titanium should target API Level 29 (aka: Android 10.0) by default if installed under the Android SDK.
Titanium currently targets up to API Level 28 (aka: Android 9.0).
*Note:*
Titanium currently does not target API Level 29 by default. This is a safety precaution until Titanium addresses all of Android Q's breaking changes. But a developer can opt-in to targeting the newest API Level (at their own risk) by adding the following to their "tiapp.xml" file.
<ti:app>
<android xmlns:android="http://schemas.android.com/apk/res/android">
<manifest>
<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="29"/>
</manifest>
</android>
</ti:app>
Is there a list of known issues when targeting Android Q? We'd like to adapt to it asap
bq. Is there a list of known issues when targeting Android Q? Yes, of course. We've already written up "Release 8.3.0" tickets to address them. I suggest you wait until we've address them all. For your reference, Google documents the breaking-changes that occur when "targeting" Android Q here... https://developer.android.com/preview/behavior-changes-q In the meantime, I suggest that you stick to 8.1.x which "targets" Android P, but is also backward compatible with Android Q.
PR (master): https://github.com/appcelerator/titanium_mobile/pull/11284
FR passed. API level 29 is used as the default target.
Closing ticket. Improvement can be seen in SDK version
8.3.0.v20191028152746
Test and other information can be found at: https://github.com/appcelerator/titanium_mobile/pull/11284