First of all: Identify the library that was causing the issue to understand where this is coming from. (e.g. using

gradle app:dependencies

) We had similar troubles with a third party SDK that fixed such a violation in a new version and Google still not approving our new release with that update. Writing an objection to the violation including • the identified root cause • the changes that were made and • proof of the fix (we included apk analyzer reports from before and after the change, showing the namespace being entirely removed) helped in our case.

@Thomas Urbanitsch Thanks for the Reply. Actually we made an mistake and panicked about the same. Actually the data Policy issue was with version 7 and currently we are on version 80 which complies with the new google policy. But I hope the thread might help others.