Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.14.0 Beta3
-
None
-
-
3b54009b13e9629b75827a59f8537451d25613a4 (qt/qtbase/5.14)
Description
When calling androiddeployqt with the --aab option (new in 5.14, see QTBUG-68202) and signing parameters, only the resulting APK is signed but the AAB is unsigned. This prevents uploading the AAB to Google Play.
Steps to reproduce
- Build Android app
- Run e.g.
androiddeployqt --aab --release --sign my.keystore --storepass mypass --input project-deployment-settings.json- -output android-build- -android-platform android-28- -jdk path/to/JDK
- Run
jarsigner --verify path/to/android-build.aab
Expected results
jarsigner says that the AAB is signed.
Actual results
jarsigner outputs:
no manifest. jar is unsigned.
Attachments
Issue Links
- resulted from
-
QTBUG-68202 Support the new Android App Bundles with androiddeployqt
- Closed