-
Notifications
You must be signed in to change notification settings - Fork 38
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
SDK automatically collects device location without verification of user consent #307
Comments
Thank you for reaching out to the Native Checkout SDK team. This integration path is now inactive for new merchants. New merchants can integrate the Native Checkout experience via the Braintree Android SDK or PayPal Android SDK. |
Hello, I am involving the team that owns this SDK to get their guidance. |
Hello, If you are seeing the Play Store flag your APK after updating to this version, please try following these steps:
After you have confirmed that you are using version 1.21.0, please double-check all tracks (even private and unpublished tracks) and then to submit an appeal to Play directly. If the issue is not resolved after following all of those steps, please share details in this thread. |
I encountered the same problem,How to solve it? |
@chpypl we just got the same rejection "Action Required: Your app is not compliant with Google Play Policies" after upgrading to
|
For anyone reading this, that are facing same issues. Update from our project - it got rejected by Google and we cannot make any new releases:
So we will be integrating another SDK. |
Hello all, We're working with Google to find out what's causing the Google Play store compliance issue. The SDK does not collect privacy data directly, however we do have 3rd-party dependencies that collect data when needed to protect our merchants and their customers from fraudulent transactions. Third-party data collection and infrequent Play Store policy changes make it difficult to get explicit guidance from Google to pinpoint the exact cause of compliance issues. We were informed that filing an appeal should help unblock developers from making updates. When making an appeal in the Google Play store, make sure to mention the following:
Google has told us that the appeals team has often granted approvals for appeals in extreme scenarios like this. Thank you for your patience as we work to resolve this matter. |
Hello, Version 1.3.0 is released and contains changes to resolve this issue. Please see the changelog for more information on integrating. |
Hello, I am opening an issue that is related to this one #281
The solution helped, issue was closed. But we received another letter from Google.
Some context
Previously we used:
After we go a warning that was the same like in the mentioned issue we changed the dependencies to and released the changes on December 12, that fixed the issue:
On February 8 we received another warning:
Google suggested fix:
Could you provide a possible solution?
The text was updated successfully, but these errors were encountered: