CODEWITHSUNDEEP
androidwear-osgoogle-play-console
Pojo
Pojo

Reputation: 81

Policy Declaration - Data Safety Section: Personal Info Data Type - Phone number

When I add the wearable dependency to my Android app and upload it to the Play Store, my app is rejected due to invalid data safety (Phone Number).

Screenshot

1

I have checked Manifest Merge (build/outputs/logs) and there are no permissions for READ_CALL_LOG, READ_PHONE_NUMBERS, READ_PHONE_STATE, READ_SMS.

Also, when I try to remove the dependencies.

implementation 'com.google.android.gms:play-services-wearable:18.0.0'
implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-play-services:1.6.4'

And uploading it on Play Store, my app update is approved.

Do we have to add Phone Number in Data Safety to support Wearable?

EDIT : Finally found out where is the issue. It's caused by the outdated of some libraries. The build.gradle files don't show any warning. We have to go to Build > Edit Libraries and Dependencies > Suggestion.

Upvotes: 8

Views: 2871

Answers (2)

Hatzegopteryx
Hatzegopteryx

Reputation: 700

One reason for this warning is the usage of Google Mobile Ads (GMA) SDK. https://play.google.com/sdks/details/com-google-android-gms-play-services-ads

Upvotes: 0

Andsoitiswritten
Andsoitiswritten

Reputation: 1

I had the exact same issue but the culprit was...

'com.google.android.gms:play-services-ads:21.5.0'

I went back to

'com.google.android.gms:play-services-ads:21.2.0'

and everything was fine.

Upvotes: 0

Related Questions