Signature of the Calendar app does not match

having now a device where I can see the behaviour. This was implied, but for the record, the test apk is fetched. From /data/user/0/com.android.providers.downloads/databases/downloads.db -

INSERT INTO downloads VALUES(15,'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',0,NULL,NULL,'file:///storage/emulated/0/Android/data/foundation.e.apps/cache/foundation.e.calendar/foundation.e.calendar_1.apk',NULL,'/storage/emulated/0/Android/data/foundation.e.apps/cache/foundation.e.calendar/foundation.e.calendar_1.apk','application/octet-stream',4,NULL,0,NULL,200,0,1751834984605,'foundation.e.apps',NULL,NULL,NULL,NULL,NULL,7681169,7681169,'W/"12ae32cb1ec02d01eda3581b127c1fee"',10136,NULL,'Calendar','',2,1,1,-1,0,0,NULL,0,NULL,1,0,0,NULL);

→ artifacts/v1.0.48-test/raw/app/build/outputs/apk/release/Etar-test.apk

1 Like

Same here, fresh install using ā€œOfficial buildā€

How where you able to do this? I seem to not be able to:

FP6:/ $ pm list packages | grep -i calendar
package:com.android.providers.calendar
package:org.fossify.calendar
package:foundation.e.calendar
package:foundation.e.webcalendarmanager
FP6:/ $ adb uninstall foundation.e.calendar
/system/bin/sh: adb: inaccessible or not found

I can also confirm this behavior. Same here. Can’t update Calendar on FP6, getting the same error message.

Theres no update, it’s a bug

I can confirm this with a freshly unpacked fairphone6 which came with /e/OS preinstalled

After the initial setup, I saw there’s an OS update (to 3.0.2-a15-20250627504414-official-FP6), did that as the first action, and got the same error in the app lounge

I put it in a bug entry yesterday, so I guess it will find its way

3 Likes

It worked, I no longer see the ā€œupdateā€ in Aurora.

Issue has been reported to the team and should be resolved ASAP.

yeah saw it. And it was on failing getprop ro.lineage.version readout , spidey bug senses!