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

Play Protect warning for version 2.3.2 from F-Droid #172

Open
hyyrdbzm opened this issue Mar 19, 2024 · 7 comments
Open

Play Protect warning for version 2.3.2 from F-Droid #172

hyyrdbzm opened this issue Mar 19, 2024 · 7 comments

Comments

@hyyrdbzm
Copy link

Screenshot_20240319-142904_1
Screenshot_20240319-142946_1
Screenshot_20240319-143252_1

@tmo1
Copy link
Owner

tmo1 commented Mar 19, 2024

Well, what does it say when you click on "More details"?

@hyyrdbzm
Copy link
Author

Screenshot_20240319-200252_1
"Learn more" leads to https://support.google.com/android/answer/2812853?hl=en

@hyyrdbzm hyyrdbzm reopened this Mar 19, 2024
@tmo1
Copy link
Owner

tmo1 commented Mar 19, 2024

The message(s) displayed:

This app may be harmful

and

Installing this app may put your device at risk.

do not match any of the "Google Play Protect Warning Strings for Malware and MUwS Categories" provided by Google. SMS I/E is certainly not malware by any reasonable definition (here are Google's definitions). I suppose I could file an appeal, but I'm not sure I feel like dealing with Google's inscrutable policies and egregious / non-existent customer service.

@hyyrdbzm
Copy link
Author

Ok, it's not issue for me too, just to let you know.

@tmo1
Copy link
Owner

tmo1 commented Mar 19, 2024

Thank you. I'll have to decide what, if anything, to do about this.

@rseabra
Copy link

rseabra commented Mar 21, 2024

That page further below providers details that appear to be a perfect match for the case:

https://developers.google.com/android/play-protect/warning-dev-guidance#app_blocked_by_play_protect

I'm sorry, @tmo1 but I'm not knowledgeable enough to validate their recommendations on your code regarding sms permissions, but could you please double check?

Maybe it's an easy fix and no appeal would be required.

Thanks,
Rui

@tmo1
Copy link
Owner

tmo1 commented Mar 21, 2024

That page further below providers details that appear to be a perfect match for the case:

The problem is that the more specific aspects of the guidance are, AFAICT, not being violated by the app, and, the less specific aspects are just so vague that I don't know what to do with them.

With regard to permissions in particular, I'm pretty sure that every permission the app requests is necessary for the app to be able to do what it does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants