This screen that #Google shows on #Android when installing #FDroid really bugs me. It is purely based on the integer value targetSdkVersion, without considering our security model, public audits results, track record over 10+ years, exclusive use of memory safe languages, or even what our code actually does. It is as if #FDroid marked anything that comes from Google as containing ads and trackers. 1/2
Looks like the latest release of #FDroid, v1.17.0, does not get flagged by #Google, at least in the #Android 14 emulator. I heard some reports that v1.16.4 also isn't flagged. I don't really know why its flagging F-Droid then. v1.16.4 has an unchanged #targetSdkVersion, but v1.17.0 has it bumped to 28. I have found no way to get info on why they are flagging the app, just this silly "unsafe" warning screen. Is F-Droid being flagged by Google Play Protect on your devices? Please let me know.
@eighthave No, because I have an ungoogled device with CalyxOS.
The Play store tells me that F-Droid was made for an older device.
Thanks for clarifying. I was confused.
@eighthave no flagging here yet, on three devices.
@eighthave F-Droid 1.16.4 is flagged as unsafe. 1.17.0 isn't.
Fairphone 4 with Android 12.
@eighthave I use LineageOS and a warning pops up when I use an app targeted at an older Android version when it needs permissions. I don't see that warning on F-Droid but going in the settings revealed that it was considered as a "Legacy app", but installing F-Droid Basic Alpha (targets A13) I see no issues whatsoever.
@eighthave BTW I don't have gapps installed.
@vitali64sur Could you try installing version 1.17.0? I believe that's fixed now
@eighthave I use Droid-ify now.
@vitali64sur ok, that's fine. I was just hoping you could test the F-Droid client to see if it still triggers that warning
@eighthave F-Droid Basic alpha doesn't have this problem so I'd assume this is fixed. :)
@eighthave I like F-Droid
@eighthave By the way, as said before no warning pops up. In the settings it was just listed as a legacy app.