-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apk cannot be installed under Android #814
Comments
Does it also happens when you try the APKs from https://github.com/AlbrechtL/welle.io/actions/runs/10682830350? |
yes, I get the very same error when attempting to install from the above link. |
Strange - something is going wrong during building ... |
Same here, the apk from the above link doesn't work neither. |
IIRC, you must sign the package (add a step or the required variable at configure time for this in android.yml github actions job), that's probably why it fails. https://doc.qt.io/qt-6.5/cmake-variable-qt-android-sign-apk.html Which requires you to update the version of Qt-Android used to build in android.yml
|
That could be the reason. @tenzap As you are the author of the Android Action pipeline can you update it and add the certificate process? Afterwards I can add my certificate. |
Sorry I'm not in that business |
Hi, will this problem be solved? |
https://github.com/AlbrechtL/welle.io/actions/workflows/android.yml is the CI workflow that builds the android app, just select the most recent run and download the desired artifact (either any/all arch, or aarch64(arm64)-only). It is actually being signed by the workflow now, so that can be included in releases binaries, and this issue is solved. |
https://github.com/AlbrechtL/welle.io/actions/runs/11262592193/artifacts/2037144642 Tested .... and it installed and works great!
|
Hint, the link only works when you are logged in in your browser (= I am using an app for github and all links are opened with a separate browser). Otherwise you will get a 404 error from github ... |
The Android version dated 20240830 gives the following error on Android 13 and also Android 9
First reported in #804 (comment) by user @rkarikari
The text was updated successfully, but these errors were encountered: