SystemApp update certificate error - official build fetching a test version apk
- /e/OS version: 3.0.2-a15-20250627504414-official-FP6
- Device model(s): FP6
- Impacted Application: App Lounge
- affected Repository: https://gitlab.e.foundation/e/os/etar_calendar/-/releases
The problem
the AppLounge updater detects a calendar updated and tries to install, failes with a certificate error
Technical details
debugging in the thread https://community.e.foundation/t/signature-of-the-calendar-app-does-not-match/71591 it was confirmed that the official build tries to fetch a test build: Etar-test.apk
https://gitlab.e.foundation/api/v4/projects/1698/jobs/artifacts/v1.0.48-test/raw/app/build/outputs/apk/release/Etar-test.apk?job=generate-apks
with signing cert
Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
Signer #1 certificate SHA-256 digest: c8a2e9bccf597c2fb6dc66bee293fc13f2fc47ec77bc6b2b0d52c11f51192ab8vs the signed cert from eCalendar.apk from IMG-e-3.0.2-a15-20250627504414-official-FP6.zip has
Signer #1 certificate DN: EMAILADDRESS=contact@e.email, CN=efoundation, OU=efoundation, O=efoundation, L=Paris, ST=Ile-de-France, C=FR
Signer #1 certificate SHA-256 digest: fe36b00ac2f05f2e295033c6dec24ea4520ed439245939748d8f03a5e0c190a9the different certificates will cause the error
Ideas
my first guess was on how the system version is read out, being blank and qualify as test device. Could applounge be barred from reading ro.lineage.version ?
Workaround
deleting the top entry with the test apk in the repo releases