Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Play Console warning regarding com.braintreepayments.api:data-collector #452

Closed
fabiorbap opened this issue Dec 8, 2023 · 6 comments

Comments

@fabiorbap
Copy link

fabiorbap commented Dec 8, 2023

Braintree SDK Version

6.9.0

Environment

Both

Android Version & Device

No response

Braintree dependencies

implementation 'com.braintreepayments.api:google-payment:3.5.0'
implementation 'com.braintreepayments.api:drop-in:6.9.0'

Describe the bug

I just got a warning from the Google Play Console that says the following:

"Your app X version code Y includes SDK com.braintreepayments.api:data-collector or an SDK that one of your libraries depends on, which collects personal or sensitive data that includes but may not be limited to identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers as described in the user data policy.

Starting from 4 February 2024 midnight (UTC), new app releases containing the SDK version(s) that do not comply with the user data policy may be blocked from release. You may consider upgrading to a policy-compliant version of this SDK that does not include the violating code, if available from your SDK provider, or removing this SDK from your app.

According to your SDK provider, you may consider upgrading to 4.31.0, and/or contacting your SDK provider to see if a suitable later version might be available. Google is unable to endorse or recommend any third-party software.

ACTION REQUIRED: Upload a new compliant version AND deactivate the non-compliant version."

Looks like the SDK is using an internal dependency that is non-compliant with the Google Play Console policy.

I received this message today, so I'm not sure there is already a fix for that. I'm also using the google-payment SDK, so it might be there as well, but I don't want to create an issue there before I check where is the problem actually.

The suggestion of updating it or google-payment to 4.31.0 doesn't make sense - it would be a downgrade from the drop-in version I'm using, and that version doesn't exist for google-payment

To reproduce

Google Play Console reviewed the app according to its policies and reported that the app is non-compliant

Expected behavior

The app becoming compliant to Google Play data policies.

Screenshots

Screenshot_08_12_23__16_37
@jaxdesmarais
Copy link
Contributor

Hello @fabiorbap -

Thanks for reaching out and using the Braintree Android Drop-in SDK. Please upgrade to at least version 6.10.0 of the SDK (lastest is version 6.13.0) to resolve this issue. It was resolved in our braintree_android SDK version 6.31.0.

You will need to ensure that all of your build tracks (e.g. open, closed, internal testing) are up to date after updating the version of the SDK.

@fabiorbap
Copy link
Author

@jaxdesmarais Thank you for such quick feedback!
I'll try doing that then, and I'll post the results, although I'm pretty sure that will fix it.
Thanks!

wwwdata added a commit to wwwdata/flutter-braintree that referenced this issue Dec 14, 2023
In order to mitigate the following PlayStore issue
braintree/braintree-android-drop-in#452
that can lead to your app being removed, we need to upgrade the native SDK.
@Always-Bijoy
Copy link

Hey can anyone please guide me on where and how I update it? where should I find it 'com.braintreepayments.api:drop-in:6.9.0', in package sdk or implement it app.gradle.

@sshropshire
Copy link
Contributor

@Always-Bijoy you'll have to update the version in your app's build.gradle file (or wherever your app declares its dependencies).

Also when you release to Google Play you'll have to update all Production and Test tracks to point to the latest version of your app.

@Always-Bijoy
Copy link

Always-Bijoy commented Feb 16, 2024 via email

@sshropshire
Copy link
Contributor

@Always-Bijoy the screenshot didn't come through. Can you resend the screenshot along with a stack trace of the crash?

I'd also suggest you select File -> Invalidate Caches... in the system menu, check all 3 checkboxes (see below) and click "Invalidate and Restart." Then try to build and see if you get the same error.

Screenshot 2024-02-16 at 2 00 58 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants