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
using the keys when generating and signing target files 3. Some of the apks are signed using the release key, some use the newly generated apk-specific keys
The /e/OS Docker image
does not generate apk-specific keys when generating signing keys 4
signs each apk with the apk-specific key if the key files exist5 before calling ota_from_target_files
We don't currently sign APEX files during the build. I don't know
a. generate the apk-specific keys
b. sign the APEXes during the build
Background
ota_from_target_files
Footnotes
https://source.android.com/docs/core/ota/apex ↩
https://wiki.lineageos.org/signing_builds#generate-keys-without-a-password ↩
https://wiki.lineageos.org/signing_builds#generating-and-signing-target-files ↩
https://gitlab.e.foundation/e/os/docker-lineage-cicd/-/blob/master/src/init.sh?ref_type=heads#L35 ↩
https://gitlab.e.foundation/e/os/docker-lineage-cicd/-/blob/master/src/build.sh?ref_type=heads#L382 ↩
The text was updated successfully, but these errors were encountered: