You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Google play protect is flagging this app as harmful
To Reproduce
Steps to reproduce the behavior:
Install or update the app directly from github releases with play protect enabled.
The message will appear. This will also show as a notification.
Expected behavior
For this to not occur, presumably its a false positive but still a concern
Screenshots
Desktop (please complete the following information):
OS: N/A
Browser N/A
Version N/A
Smartphone (please complete the following information):
Device: Samsung Galaxy S21
OS: Android 14
App Version: 1.3.3
Additional context
Any idea why its being flagged? I assume its a false positive. Not sure if the F-Droid build is affected as this was with the github release build.
The text was updated successfully, but these errors were encountered:
I believe Google Play Protect utilizes results from multiple file scanning platforms.
It's absurd that some file scanning platforms label apps as malicious based solely on the permissions they request.
So if we are using the GitHub release version we can just ignore the flagging? I tried uninstalling and reinstalling multiple times but the bug is still present. I would like to be able to use the latest version since the one packaged for f-droid is older. I hope Google will fix their problems.
Describe the bug
Google play protect is flagging this app as harmful
To Reproduce
Steps to reproduce the behavior:
Expected behavior
For this to not occur, presumably its a false positive but still a concern
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Any idea why its being flagged? I assume its a false positive. Not sure if the F-Droid build is affected as this was with the github release build.
The text was updated successfully, but these errors were encountered: