-
Notifications
You must be signed in to change notification settings - Fork 78
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
Comments
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 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. |
@jaxdesmarais Thank you for such quick feedback! |
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.
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. |
@Always-Bijoy you'll have to update the version in your app's 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. |
If I add this line to my build.gradle app crashed.[image: Screenshot
2024-02-17 at 1.56.17 AM.png]
implementation 'com.braintreepayments.api:drop-in:6.13.0'
…On Sat, Feb 17, 2024 at 1:30 AM sshropshire ***@***.***> wrote:
@Always-Bijoy <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#452 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG7E3266NM3IBIT6V6XMOFLYT6XUZAVCNFSM6AAAAABANDLPWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZGIYDANJRGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Best Regards,
Bijoy Ghosh
Flutter Developer
+880 1688 134326
***@***.***
|
@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 ![]() |
Braintree SDK Version
6.9.0
Environment
Both
Android Version & Device
No response
Braintree dependencies
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
The text was updated successfully, but these errors were encountered: