Re: [Qbs] Signing an Android APK
On Mon, 11 May 2020 at 20:10, Christian Gagneraud wrote: > > n Mon, 11 May 2020 at 19:43, Raphael Cotty wrote: > > > > Hi, > > > > Release keystore support is not implemented yet: > > https://bugreports.qt.io/browse/QBS-1546 > > > > Can you explain a bit more 'jks' keystore type? > > It turned out that it's just a file extension, the file format is the same. > I'm now able to sign and run the APK from QtC, i just changed the > hard-coded values. > > I've commented on QBS-1546. I'll open a change request, changes are quite trivial. Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Signing an Android APK
n Mon, 11 May 2020 at 19:43, Raphael Cotty wrote: > > Hi, > > Release keystore support is not implemented yet: > https://bugreports.qt.io/browse/QBS-1546 > > Can you explain a bit more 'jks' keystore type? It turned out that it's just a file extension, the file format is the same. I'm now able to sign and run the APK from QtC, i just changed the hard-coded values. I've commented on QBS-1546. > About the non-repeatable errors, can you set > Qt.android_support.verboseAndroidDeployQt to true and provide the log? I have several issues, some might be due to QtC/Qbs integration, QtC is crashing sometimes as well... I've added the property, and let you know if i find something wrong. Thanks, Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Signing an Android APK
Hi, Release keystore support is not implemented yet: https://bugreports.qt.io/browse/QBS-1546 Can you explain a bit more 'jks' keystore type? About the non-repeatable errors, can you set Qt.android_support.verboseAndroidDeployQt to true and provide the log? Le lun. 11 mai 2020 à 03:57, Christian Gagneraud a écrit : > On Mon, 11 May 2020 at 09:03, Raphael Cotty > wrote: > > > > Hi, > > > > If you look at the sdk.qbs file in the Android module then you'll see > that you can provide a file for the keystore (pattern *.keytstore). > > If not then qbs uses the default keystore file > ($HOME/.android/debug.keystore on Linux). > > Hum, looks like non debug signing is not implemented, keystore alias, > password, ... are hardcoded in sdk/utils.js: prepareAaptPackage(). > As well I had to add a tagger since our keystore has 'jks' file extension. > The keystore comes with a property file, that contains all the details > for the signing process, i don't know if it's standard or an in-house > procedure. > This could be a Freescale specific system too, our AOSP is based on > the imx8 one. > > > Qbs also relies on androiddeployqt but only to gather the dependencies. > The generation of the apk package and the signing is done by qbs rules. > > I have non-repeatable errors in there, but a clean build seems to > always work, i can generate APK in debug mode with default keystore. > It crashes, but that's another story. > > Chris > ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Signing an Android APK
On Mon, 11 May 2020 at 09:03, Raphael Cotty wrote: > > Hi, > > If you look at the sdk.qbs file in the Android module then you'll see that > you can provide a file for the keystore (pattern *.keytstore). > If not then qbs uses the default keystore file ($HOME/.android/debug.keystore > on Linux). Hum, looks like non debug signing is not implemented, keystore alias, password, ... are hardcoded in sdk/utils.js: prepareAaptPackage(). As well I had to add a tagger since our keystore has 'jks' file extension. The keystore comes with a property file, that contains all the details for the signing process, i don't know if it's standard or an in-house procedure. This could be a Freescale specific system too, our AOSP is based on the imx8 one. > Qbs also relies on androiddeployqt but only to gather the dependencies. The > generation of the apk package and the signing is done by qbs rules. I have non-repeatable errors in there, but a clean build seems to always work, i can generate APK in debug mode with default keystore. It crashes, but that's another story. Chris ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Signing an Android APK
Hi, If you look at the sdk.qbs file in the Android module then you'll see that you can provide a file for the keystore (pattern *.keytstore). If not then qbs uses the default keystore file ($HOME/.android/debug.keystore on Linux). Qbs also relies on androiddeployqt but only to gather the dependencies. The generation of the apk package and the signing is done by qbs rules. The Qt.android_support module is in charge of controlling androiddeployq ( https://doc.qt.io/qbs/qml-qbsmodules-qt-android-support.html). Also look at Android.ndk ( https://doc.qt.io/qbs/qml-qbsmodules-android-ndk.html) and Android.sdk ( https://doc.qt.io/qbs/qml-qbsmodules-android-sdk.html). Raph Le dim. 10 mai 2020 à 18:16, Christian Gagneraud a écrit : > Hi there, > > I'm experimenting with converting a project to Qbs. > It is relatively small and is (so far) C++/Qt only. > I have a few apps, and i need to generate APKs, and sign them. > I couldn't find any mention of signing in Qbs docs, is this something > supported? > I currently (not using Qbs) rely on androiddeployqt, is this tool used > by Qbs under the hood? Can i control it from Qbs? > > Thanks, > Chris > ___ > Qbs mailing list > Qbs@qt-project.org > https://lists.qt-project.org/listinfo/qbs > ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
