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

Android Application Bundle (aab) not signed

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Done
    • P3: Somewhat important
    • 6.4.0 RC1, 6.5.0 Beta1
    • 6.4.0 Beta2
    • Build System: CMake
    • None
    • MacOS 12.5, Qt6.4.0b2, cmake 3.24.0

    • Android
    • 042290d0fb (qt/qtbase/dev) 042290d0fb (qt/tqtc-qtbase/dev) d052236a2f (qt/qtbase/6.4) d052236a2f (qt/tqtc-qtbase/6.4)

    Description

      I have a cmake project that creates an Android app from the command line (without Qt Creator). That works fine.

      Signing the apk is possible using QT_ANDROID_SIGN_APK and setting the environment variables QT_ANDROID_KEYSTORE_PATH, QT_ANDROID_KEYSTORE_ALIAS, QT_ANDROID_KEYSTORE_STORE_PASS, QT_ANDROID_KEYSTORE_KEY_PASS. That works fine on the *_make_apk target.

      I now was trying to sign the generated Android Application Bundle (aab) on the *_make_aab target. This does not work.

      IMHO, the problem is that in Qt6AndroidMacros.cmake the "add_custom_target(${target}_make_aab ..." does not add ${sign_apk} to the androiddeployqt call (as it is done in the *_make_apk targets).

      Attachments

        Issue Links

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

          Activity

            People

              jbornema Joerg Bornemann
              frank2525 Frank Deinzer
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes