Ongoing issues with App Lounge where apps are available in both the Play Store and F-Droid.
- /e/ version: 1.12.3 stable
- Device model(s): FP3
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
Following the v1.12.3 update App Lounge is showing incorrect versions of apps in a search even though, for the first time in a few months, an update to a Play Store version of an app was able to be performed successfully. Summary
After updating to v1.12.3, in App Lounge settings I deselected automatic updates and also the option to update apps installed by other stores, and set it to show common apps and open source apps. On then checking for updates I was offered an update to the (installed) Play Store version of Vespucci (from Marcus Wolschon not F-Droid). This update was successful and I have confirmed it is the Play Store version as it offers aerial imagery from Bing that the F-Droid version does not.
However, when searching later in App Lounge for Vespucci it is the F-Droid version that is displayed with an 'open' box alongside.
To add to the confusion, when I search for Proton VPN the version displayed is from support@protonvpn.com (with an 'open' box alongside) despite the fact that it is the F-Droid version I have installed.
I have tried various other settings in App Lounge and always receive the same incorrect results in search. I have also cleared App Lounge's cache and storage wirh the same results.
The problem
Steps to reproduce
Try installing Proton VPN from F-Droid then searching in App Lounge for Proton VPN. It may be difficult to reproduce the Vespucci example as it is not currently possible to install the Play Store version of an app through App Lounge where the app is available in F-Droid.What is the current behavior?
The search result shows the app version from support@protonvpn.com not F-Droid.What is the expected correct behavior?
A search in App Lounge for an intalled app should show the version installed (in this case that from F-Droid), not that from a different store.Technical informations
Relevant logs (adb logcat
)
Relevant screenshots
Solutions
Workaround
None known.Possible fixes None known.