Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-80406

androiddeployqt does not sign Android App Bundles

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2: Important
    • Resolution: Done
    • Affects Version/s: 5.14.0 Beta3
    • Fix Version/s: 5.14.1, 5.15.0 Alpha
    • Component/s: Build tools: Other
    • Labels:
      None
    • Platform/s:
      Android
    • Commits:
      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

      1. Build Android app
      2. 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
      3. 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

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              taipan BogDan Vatra
              Reporter:
              fseiffert Frederik Seiffert
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes