Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

Account Manager is updated through App Lounge, but App Lounge continues to show it as updatable.

  • /e/ version:
  • Device model(s):
  • Developer mode enabled: yes/no
  • Device rooted: yes/no
  • Trackers blocker enabled: yes/no

Summary

System apps like Account Manager do not properly reflect the updated status.

The problem

Steps to reproduce

Install Account Manager update through App Lounge.

What is the current behavior?

The "Update" button continues to show as "Update" instead of "Open".

What is the expected correct behavior?

The "Update" button should change to "Open".

Technical informations

Relevant logs (adb logcat)

Relevant screenshots

Solutions

Workaround

Possible fixes

This is happening because our JSON files do make App Lounge believe that there is an update by adding the date to the version_name in the JSON. This was agreed upon here: https://gitlab.e.foundation/e/backlog/-/issues/2509#note_569880

Example: JSON version_name = "4.3.9-ose+202407291626"

But the actual APK continues to have the old unchanged versionName.

Example: build.gradle versionName = "4.3.9-ose"

After installing an update APK, App Lounge compares with the actual versionName of the installed system app (which is old) with the version_name from JSON, and continues to think that a new version is available, even though it just installed the exact version.

This can be remedied by adding the date in the build.gradle file of the app itself, instead of adding it from the gitlab-ci script.

Edited by Sayantan Roychowdhury