Buildbox 3.2.1 Release - Heyzap Sdk Or Library Violates

I am using Buildbox 3.2.1 release and I have received a violation mail from google today.

- Anyone had received violation notification. Any help?
- Is it safe to remove Heyzap SDK from the build?
- Will be Ad-mob ad's works if we remove it?


APK REQUIRES PROMINENT DISCLOSURE
We’ve identified that your app is using Heyzap SDK or library, which facilitates the transmission of collection of installed packages information without meeting the prominent disclosure guidelines. If necessary, you can consult your SDK provider(s) for further information.

APK REQUIRES VALID PRIVACY POLICY
Your app is uploading users' installed packages information via Heyzap SDK without posting a privacy policy in both the designated field in the Play Developer Console and from within the Play distributed app itself.

 

i have the same problem and i fixed it just go to your game project "android\app\libs" and delete heyzap library
after that build new APK or Android App Bundle and submit new update

 

Finally problem solved after removing the Heyzap library

 

After deletion Heyzap library, you AdMob works?

 

Yes all good after deleting the libraries

 

ok how do you delete the libraries? is this the case for 2.3.10 version of build box?

 

@SpoonCrysis I am not very sure with version 2.3.10 but for 3.x version you can delete from android\app\lib folder "PTAdHeyzap.jar" and "PTAdLeadBolt.jar". I hope with the new version of buildbox these libraries are no more existing. However, better to have it in check-list before deploying to playstore.

 

I did a few updates last night I can confirm that PTAdHeyzap.jar is already removed from 2.3.10 by default when you export.

you don't need to remove anything its already done.

FYI when you reupload the APK make sure you don't have any active old beta or alpha version because they will reject your app again so make sure all the old versions are deactivated. You should be fine.