Hello,
I just installed e/os on a fairphone 6, but I got an issue on an update to the native calendar app. When I try to install it, it says the signature of the update does not match. I saw that the solution was to remove and reinstall the app. However, as a built-in app, I can only do it with adb. I tried, but it reinstalls exactly the same app and I still have the issue. Any idea of how I can solve that?
what appid exactly are you updating / removing and from what source? inbuilt system app is foundation.e.calendar, but I’ve never seen an external source offering an update on it. Fork upstream appid is ws.xsoh.etar
It is foudation.e.calendar
I’ve not installed any other calendar app and when I remove it via ADB, it disapears from App lounge updates
where is the update to foundation.e.calendar offered, what’s the process you used to update it?
It is in App Lounge :
I can’t click update. But when I do update all, I get the error:
“La mise à jour me peut être appliquée car la signature de la mise à jour de Agenda ne correspond pas à la version installée sur votre téléphone.
Pour y remédier vous pouvez désinstaller Agenda puis la réinstaller depuis App Lounge. Note : ce message ne s’affichera plus.”
Which can ne translated as:
“The update cannot be applied because the update’s signature of Calendar does not match the version installed on your phone.
To solve this, you can uninstall Calendar then reinstall it from App Lounge. Note: this message won’t be displayed again”
ah, this is sourced through the e gitlab per project id (calendar), forgot. So seems applounge is picking the wrong apk then for your release version probably?
That community apk in there uses the proper cert, so assume the official too. I guess that “v1.0.48-test” build should be the culprit, that uses Android testkeys
The installed Calendar app is at version 1.0.47 and I use the latest e/is version 3.0.2
Is there anything to do ? Or should I wait for a fix in a future version ?
I guess this points at a bug in version picking for system apps, it should pick the proper version. But I’m flummoxed it even tries to on non-test builds. Are you running a testing build?
(the update being denied is actually how it’s supposed to work when the certificate differs - that is Androids apk security model)
While it is disallowed to talk of testing builds I can confirm seeing as @Pato on a testing a15 but in App Lounge the “item” cannot be clicked to “Show details”. Thus by clicking on the “Update” link one is doing it “blind”.
As you say
looks valid on my testing build.
I run /e/os version 3.0.2-a15-20250627504414-official-FP6
Just for the record, I can confirm this issue. Behaves exactly the same here.
what cert is shown for you?
adb pull $(adb shell pm list packages -f | grep =foundation.e.calendar | sed 's/=foundation.e.calendar//g' | sed 's/package://g')
apksigner verify --verbose --print-certs base.apk | grep -A1 'Signer #1 certificate DN'
also, this should be the same as the settings ui (ro.lineage.display.version), but I’m curious. What does this return?
adb shell getprop ro.lineage.version
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: fe36b00ac2f05f2e295033c6dec24ea4520ed439245939748d8f03a5e0c190a9
checks out if it would pick the Etar-official.apk
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: fe36b00ac2f05f2e295033c6dec24ea4520ed439245939748d8f03a5e0c190a9
vs Etar-test.apk
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: c8a2e9bccf597c2fb6dc66bee293fc13f2fc47ec77bc6b2b0d52c11f51192ab8
I guess the issue should be the official img checking that calendar repo at all, getting the top entry, the top entry being a qa-build. I’d post this to the devs telegram or into the gitlab backlog, but would think they’re already aware.
I have the same issue with e/os 3.02-a15-20250627504414-official-FP6 on Fairphone 6.
It may be related that the version of Bliss Launcher is 1.3.1 and is reported as installed in the App Lounge.
Now in Settings I see the version of Bliss Launcher to be 3.1.2, but what is running looks very much like 1.3.1.
Is there any way to maybe manually uninstall the App Lounge versions of Calendar, App Lounge (and others? How to check?) and install the system versions?
can any FP6 user run that adb shell getprop ro.lineage.version ?
3.0.2-a15-20250627504414-official-FP6
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: fe36b00ac2f05f2e295033c6dec24ea4520ed439245939748d8f03a5e0c190a9
thx, that’s all fine. My hunch was wrong or the function returns empty. I don’t hang out on telegram but someone there should post this. I usually don’t file gitlab backlog entry when I can’t debug the issue myself.
Which group should I join to post this? Should I point them to this thread here?
unsure, if you have a gitlab account and are affected by the bug, backlog probably better than telegram. There’s a dedicated testing group, but it could be the wrong place as this affects the official image.