Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Exodus app mistakenly use Google Play report for an installed F-Droid app (same handle) showing wrong tracker's number #526

Open
user4andre opened this issue Jan 4, 2025 · 9 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@user4andre
Copy link

Describe the bug

The app Material Files (version 1.7.4) is available in the Play store with the trackers Google CrashLytics and Google Firebase Analytics.
These trackers are not included in F-Droid version.

If you check the F-Droid version immediately after installation with the Exodus app or directly on the website, no trackers are displayed.
After a short time (updating the database in Exodus), the trackers from the Google Play version are displayed.

I have also created a ticket for the Material Files app.
zhanghai/MaterialFiles#1369

To Reproduce

  1. Install the Material Files app via F-Droid.
  2. check app in F-Droid app -> 0 Tracker
  3. wait a little, then update database and check again -> 2 trackers

If you check F-Droid version of Materal Files on Exodus webside 0 trackers are reported.
If you check Google Play version of Materal Files on Exodus webside 2 trackers are reported.
Same version code is used in boath app shops (ignoring differences).

Expected behavior

The trackers (none in this case) should be displayed according to the installed F-Droid app.

Version details

I use:
Android 13
Material Files 1.7.4 (F-Droid version)
Exodus 3.3.2 (from F-Droid)

Install method

F-Droid

@codeurimpulsif
Copy link
Contributor

@user4andre Hi, are speaking of the Exodus Android app or the Exodus plateform?

@user4andre
Copy link
Author

@codeurimpulsif

The change from displaying right (F-Droid) information to wrong (Google) information happens in Android Exodus 3.3.2 (F-Droid) app. In the app version 3.3.2-23 is displayed when clicking ( i ) button.

I checked right tracker information by using aurora store app.
First search for Material Files.
Then clicking "Neue Analyse anfordern" (German language setting, Translation: "new analyse") to open Exodus homepage, were I can select the source Google Play or F-Droid.
Then starting a new analyse and clicking display report when finished.

Yesterday I deinstalled Material Files app and installed it again from F-Droid in the evening.
Until now I can not observe the described behavior.
At the day I repoted the bug I could observe it 2 times.

I will send an update when it happens again.

@user4andre
Copy link
Author

update @codeurimpulsif

The error did not occur again on the device on which the described behavior was first observed.

On a second cell phone (also Android 13), I had also installed the Material files app with F-Droid.
If I go to Settings > Apps > show all .. apps > Material Files in the Android interface, I see “App installed with F-Droid Basic” at the end of the app info.
In the Exodus app, “User” is indicated as the installation source below the app icon and name. The two trackers of the Google version are listed below this.
After uninstalling the Material Files app and reinstalling it (via F-Droid), the Exodus app again shows no trackers.

The bug seems to be difficult to reproduce as it appears to occur sporadically.
I find it particularly strange that the Exodus app and the data in the Android settings match the installation source F-Droid, but the trackers from the Google Play version are displayed in the app.

If anyone can tell me what I need to do to upload screenshots, I could post some pictures.

@codeurimpulsif codeurimpulsif transferred this issue from Exodus-Privacy/exodus Jan 7, 2025
@codeurimpulsif
Copy link
Contributor

@user4andre Did the app on Google Play Store and F-Droid have the same handle? It may be the cause.

Can you give us the handle of the app?

@user4andre
Copy link
Author

@codeurimpulsif
What do you mean with handle? I am no programmer or IT-expert.
An example may help me.

@user4andre
Copy link
Author

user4andre commented Jan 7, 2025

@codeurimpulsif
May be this link can answer the question better than me.
https://reports.exodus-privacy.eu.org/de/reports/search/me.zhanghai.android.files/

@codeurimpulsif
Copy link
Contributor

@user4andre yes thanks, the handle is the "identifier" of the app (me.zhanghai.android.files for this example)

@codeurimpulsif
Copy link
Contributor

As I can see there is no issue on the Exodus plateforme but the handles of the app are the same for the Google Play Store and FDroid version, so maybe the Exodus app can't know which version you have on your phone and by default select the first it found (the Play Store or FDroid one, depending on conditions maybe) and show the number of trackers.

But I'm not a dev of this app (and we don't have maintainer for now) so I don't know.

I will keep this issue opened if anyone find a solution. Thanks!

@codeurimpulsif codeurimpulsif changed the title [Bug] Display of trackers from Google Play store for App from F-Droid after short time and database update in Exodus [Bug] Exodus app mistakenly use Google Play report for an installed F-Droid app (same handle) showing wrong tracker's number Jan 8, 2025
@codeurimpulsif codeurimpulsif added the good first issue Good for newcomers label Jan 8, 2025
@user4andre
Copy link
Author

user4andre commented Jan 8, 2025

You should keep in mind that the app initially displays the data correctly and later changes to Google Playstore related data.

Material Files has the same handle (me.zhanghai.android.files) and the same version numbering (1.7.4) for both app stores although the apps are different.

There are several other apps with the same handle but with an app store label included in the version number. The problem does not occur there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants