Device and Network Abuse policy: Violation of Device and Network Abuse policy

[PriyanshuGuptaVandelay]

Hi team,
I am getting Device and Network Abuse policy: Violation of Device and Network Abuse policy
on google play. I have updated my unity version to 6000.2.6f2 after reading this article (Unity Platform Protection: Take Immediate Action to Protect Your Games and Apps). Google is still giving the same error on new release.
Please help.

Thanks,
Priyanshu Gupta

[Kurt-Dekker]

The Android game published on Google Play Console has been upgraded to Unity version 2022.3.62f2, however, the security warning remains

Hi folks, can you DM me your bundle ids? I will reach out to Google and inquire what’s going on there. Another thing to double check - did you patch every active application track (including closed or open testing)? Google will consider the application vulnerable if any of the tracks are unpatched.

[lupusoft]

Hello, I have same proble too :).
I use 6000.1.8f1 version. I tried minifying my project and trying not using custom gradle.
But the problem still persists. I have limited time. They will remove my app from the store in 1 month.

[Tautvydas-Zilys]

@lupusoft

I use 6000.1.8f1 version.

Was that meant to be 6000.2.8f1? If you’re truly on 6000.1.8f1, then you will either need to use Unity Application Patcher or you will need to update your version of Unity to at least 6000.1.17f1.

[lupusoft]

First of all, thank you for your interest. When I updated my UnityHub app, I noticed that the version I was using had a publishing issue, as you mentioned. I upgraded to the newer version, Unity 6000.2.10f1. But I’m still getting the same error.

[lupusoft]

Hi everyone, my issue has finally been resolved!
When I reached out to Google Play support again asking why the problem still persisted, they reviewed my app and replied that there was no action required on my part — the warning was cache-related and would disappear automatically after some time.
And yes, the warning is now gone and everything is back to normal!

[mrsiro217]

I ALSO HAD THE SAME ERROR AT 6000.0.62F1 LTS