Signing android release apk

  • The build output produces:

     [echo] No and key.alias properties found in
     [echo] Please sign C:\temp\build-myapp-Android_for_armeabi_v7a_GCC_4_8_Qt_5_3_1-Release\android-build\bin\QtApp-release-unsigned.apk manually
     [echo] and run zipalign from the Android SDK tools.

    But a little further it says:

    Total time: 12 seconds
    Signing Android package.
    jar signed.

    No -tsa or -tsacert is provided and this jar is not timestamped. Without a timestamp, users may not be able to validate this jar after the signer certificate's expiration date (2042-05-06) or after any future revocation date.
    Verifying alignment of C:/temp/build-myApp-Android_for_armeabi_v7a_GCC_4_8_Qt_5_3_1-Release/android-build/bin/QtApp-release.apk (4)...
    50 META-INF/MANIFEST.MF (OK - compressed)
    Android package built successfully.
    -- It can now be run from the selected device/emulator.

    So is it signed or not ?
    The output is confusing because first it states 'No ..' and later 'Signing Android package. - jar signed.'

  • if the package has in name release its signed and ready to put on market.

Log in to reply

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.