Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
5.15.2, 6.x
-
Android
-
2021wk22PO2, 2021wk24PO2, 2021wk30POAndroid, 2021wk32POAndroid, 2021wk34POAndroid, 2022wk42FOQtforAndroid, 2022wk44FOQtforAndroid, 2022wk46FOQtforAndroid
Description
Starting in August 2021, apps must target API level 30 (Android 11) or above. That also means that APK Signature Scheme v2 is now required.
https://developer.android.com/distribute/best-practices/develop/target-sdk#pre11
Currently if I set targetSdkVersion = 30 in build.gradle deployment in the aab format fails on Android 11 devices. I experienced this issue after I updated a Samsung phone from Android 10 to Android 11.
Skipping createRCC adb: failed to install C:/_t/build-untitled36-Android_Qt_5_15_2_Clang_Multi_Abi_c76acd-Release/android-build//build/outputs/apk/release/android-build-release-signed.apk: Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES: Scanning Failed.: No signature found in package of version 2 or newer for package org.qtproject.example] Installing Android package to device.
Attachments
Issue Links
- is required for
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
| For Gerrit Dashboard: QTBUG-91255 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 440319,7 | Android: Fix signing of APKs that are generated when an AAB is also built | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 441176,2 | Android: Fix signing of APKs that are generated when an AAB is also built | 6.4 | qt/qtbase | Status: MERGED | +2 | 0 |
| 441218,4 | Android: Fix signing of APKs that are generated when an AAB is also built | tqtc/lts-5.15 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |
| 441219,3 | Android: Fix signing of APKs that are generated when an AAB is also built | tqtc/lts-6.2 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |