v1.63 flagged as harmful by Google Play Protect

[ghost]

Not sure what has caused this but v1.63 is being flagged as harmful by Google Play Protect, v1.62 and below are fine.

[chenxiaolong]

Does Google Play Protect provide any details about why it's flagging BCR?

I'm unable to reproduce this on my device.

[ghost]

Does Google Play Protect provide any details about why it's flagging BCR?

I'm unable to reproduce this on my device.

Strange, and it doesn't provide any other information.

[chenxiaolong]

Darn, I'm not really sure what would be causing this then.

[now0clock]

Click the "Learn more" and see.

It's something to do with the READ_CALL_LOG permission.

See here,

https://support.google.com/googleplay/android-developer/topic/9877467?hl=en

[chenxiaolong]

Interesting, I wonder why it only started complaining about that now. READ_CALL_LOG has been around since version 1.40.

I hate this, but I think we might just need to tell people to ignore the warning. I don't plan on making a separate build of BCR with this functionality removed.

[ghost]

Versions below v1.63 don't get flagged by Play Protect so I'm kinda doubting that specific permission is the reason here. Tried v1.61 & v1.62, they both install fine and without that warning.

[DoulosTrieste]

Set Play Protect to disable "Improve harmful app detection", then disable Play Protect and enable it again.