You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the latest release, I believe you simply published the APK built by the 'nightly' job.
Please note that this APK is not signed. Actually it is, but with the developer key, and it is valid only for 1 year iirc, hence it can be installed only during that period.
Would you please sign the APK with your keys? Either by updating the Travis job to have it done on each commit, or by signing at least the official releases when you punish them?
Under the hood, your Qt code is built and copied to the $ANDROID_BUILD_DIR, then Gradle is used to build the Java code and package the application. If an APK intended for release is built, then it should be signed with jarsigner and aligned with zipalign.
Is there an option to sign the nightly build via Github actions? I mean there is the function secrets. Feel free to take a look into it! For sure I can place a nightly build private key inside the Github action secrets.
For the latest release, I believe you simply published the APK built by the 'nightly' job.
Please note that this APK is not signed. Actually it is, but with the developer key, and it is valid only for 1 year iirc, hence it can be installed only during that period.
Would you please sign the APK with your keys? Either by updating the Travis job to have it done on each commit, or by signing at least the official releases when you punish them?
Instructions can be found here for qt6.
https://doc.qt.io/qt-6/deployment-android.html#building-the-android-application
Extract from that page:
Btw, for the older qt5, see #679
The text was updated successfully, but these errors were encountered: