I am trying to publish my application to play store but I get following error.
I am new to flutter and I don't know where to upgrade this SDK as I have not included it in my build.gradle or pubspec.yaml
Error
SDK Stripe Android SDK (com.stripe:stripe-android), 10.4.6 facilitates the transmission or collection of personal and sensitive information. Such behavior must comply with Google Play's Prominent Disclosure & Consent Requirements and applicable privacy policy requirements as described in the User Data policy. You can't publish this release due to this policy issue.
To be allowed to publish, you may consider upgrading to 16.9.0, which the SDK provider has recommended for use instead. Please consult the SDK provider for further information.
I had exactly the same error in the Google Play console. It was asking to upgrade sdk to 16.9.0 meanwhile that version was aborting.
The only solution which worked in my case was upgrading SDK to 10.5.0.
implementation 'com.stripe:stripe-android:10.5.0'
It is a hot fix version which resolves the Google Play compliance issues.
Hope this will hep you.
There's a simple fix to this:
Install patch-package & add it to your post-install script
Go to node_modules/tipsi-stripe/android/build.gradle and change implementation 'com.stripe:stripe-android:10.4.6' to implementation 'com.stripe:stripe-android:10.5.0'
Re-sync gradle
Apply patch: yarn patch-package tipsi-stripe
Done!
In case anyone uses React Native, this helped me to get it updated and launched in Google Play Store: https://gitmemory.com/issue/tipsi/tipsi-stripe/785/861289460
The error was caused due to the use of stripe-payment : 1.0.9 in pubspec.yaml and simply upgrading it didn't actually solve the problem. I had to open build.gradle in a new window as android project and in the file build.gradle, implementing suggested 16.9.0 and whenever we change the build.gradle it starts re-indexing and afterwards the issue was resolved.
Related
After publishing the app I got the following error in Play Console.
For the solution, it is said that it is necessary to choose a version above the "implementation 'com.google.firebase:firebase-crashlytics:18.3.0' version, for example 18.3.1, but I had never added it anyway.
Would it be enough to upgrade firebase packages in package.json to solve this problem? Or what else should I do?
the reason you don't see the implementations on the React Native side is because adding implementations should be handled under the hood by the package you added in package.json.
So in theory updating it should be enough.
However since this is Firebase update also all firebase packages to an equivalent version
When I want to upload my flutter aab in Play Console, I got the below warning.
Critical issues have been reported with the following SDK versions:
com.google.android.gms:play-services-safetynet:17.0.0
What the SDK developer told us:
The SafetyNet Attestation API is being discontinued and replaced by the new Play Integrity API. Begin migration as soon as possible to avoid user disruption. The Play Integrity API includes all the integrity signals that SafetyNet Attestation offers and more, like Google Play licensing and better error messaging. Learn more and start migrating at https://developer.android.com/training/safetynet/deprecation-timeline
Kindly help me resolve that. The app is made in flutter.
If you are not using safety net anywhere just do the below changes in your code.
implementation platform('com.google.firebase:firebase-bom:30.2.0')
implementation('com.google.firebase:firebase-auth') {
exclude module: "play-services-safetynet"
}
This is what works for me, Playstore complains about SDK critical issue.
I was using firebase_auth on top of google sign in in my flutter application, and firebase_auth has com.google.android.gms:play-services-safetynet:17.0.0 as its dependency.
You can check what package is dependent on safetynet by running gradlew command. Navigate to android folder within your flutter project and run ./gradlew app:dependencies
So I removed firebase_auth and use only google sign in, now all good with Playstore. My application is flexible and does not require safety/verification nor firebase auth, hence I am ok to remove the firebase part for now. You can do similar troubleshooting and identify package dependent on safetynet and decide. Hope this helps your case too.
I have answered in a similar question here, you need to update com.google.gms:google-services because it contains safetyNet API.
Use ver 4.3.13 and the warning has gone.
Play Store Warning : play-services-safetynet (com.google.android.gms:play-services-safetynet) has reported critical issues with version 17.0.0
I am using Appsflyer library in my project. Previously I was using version 5.0.0. Then I got this message when uploading a new version.
The developer of AppsFlyer SDK (com.appsflyer:af-android-sdk) has reported version 5.0.0 as outdated. You must upgrade to a newer version (5.1.0+) before you can publish a new release to production.
So I updated the version from 5.0.0 to 6.5.4. But I still get this message. I am unable to upload app to play store.
If you need any other information, please let me know through the comments section. I will update it here. Thank you all in advance.
Before posting this question I tried "invalidate cache / restart" option. It didn't work. But after reading the comment from Pierre, I cleaned the project and tried again. Surprisingly it worked. Thank you Pierre.
I had the same issue with a different library. even after removing the library still, issue came. and I was using react native. first tried with ./gradlew clean then ./gradlew build. then it solved
I am trying to add Firebase to the android app using Cordova to implement push notification.
so for I was able to add 'google-services.json' to the root of the project.
however when I am trying to build an android app using the command
cmd>cordova build
it's giving me following error.
Could not resolve all dependencies for configuration ':_debugApkCopy'.
Could not find com.google.firebase:firebase-core:9.0.0.
this is occurring despite adding google play services plugin to Cordova.
I am new to hybrid app building , please help me on this.thanks
You need 'Android support Repository'. Open sdk manager check weather this is installed or not. Install/Update it. If already installed, you may need to uninstall and reinstall Android support repository. then restart your PC
You may also install google play services and google repository. many plugins may require these two.
I have an android app in which I am using Google Maps API for Android v2. It was working fine in my phone until I upgraded my phone to Marshmallow. After updating my phone once I uninstalled it and again installed it using Android Studio it started having random crash. And every time the error was
V/GoogleSignatureVerifier: Signature not valid. Found:
MIIDDTCCAfWgAwIBAgIEPmxzXDANBgkqhkiG9w0BAQsFADA3MQswCQYDVQQGEwJVUzEQMA4GA1UE
ChMHQW5kcm9pZDEWMBQGA1UEAxMNQW5kcm9pZCBEZWJ1ZzAeFw0xNTA5MjExMjE1MDNaFw00NTA5
MTMxMjE1MDNaMDcxCzAJBgNVBAYTAlVTMRAwDgYDVQQKEwdBbmRyb2lkMRYwFAYDVQQDEw1BbmRy
b2lkIERlYnVnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoTlzAY3DX0+vQmRo5stW
izwv76mghc1mbdxQnI16N6Ci/LFPOsiQLfYgt/qqitKCmo2kWWzfKNxN1Qyg5KaFdXRxpM8Ec7Xm
fkMX5cXzJOBDS62uWoDXpjiaXNOBeCvHDwC02EfOGfBd8csnO7sm3htHP8l2Jbn4uAY/zRQ+F4+C
Y477hSMxUvcDYoOoAcsye7pEu1bvPLSRxM44kjjhBFJlLYw6QtzE00khMrwdgBQwSdY0vtUPj9NM
hKGRuGoK/suIpd9e82EhqbUSlYsd62I/HV3390Eo/N2xXCsK7jrRdz6G9MjHfnUQLN80frZXGApl
LWiBti2soI9HhI++dQIDAQABoyEwHzAdBgNVHQ4EFgQU3JFv8ivvt36O8WrsmkXRWYCDbEEwDQYJ
KoZIhvcNAQELBQADggEBAFLFGhfV6F4VOMCdKky6drHD10LzvR8/6QJzf/yp1QARzb3aR319g1my
f6Ffsaam9SKKj6OO92Jz7RTgUvZ6aD5sgRJXKcetmrGNWLGvsg0Rn+OxyEJ6dp4z49Oj5xyXjREp
6zv3QXxENib6EmPYKkFRS6cIe3QOMPsa6Q0KBKQFNnRAW+A+VBAVfEQYB1lgUMXUD+L9pc9EGNcN
zbatMn4FuWeyrhVaiSgMqyNHghUISgAZF76ImkQoPHVwgu7DzQQ44bXAwAbLFIwVhate/C0zN5ps
TjBZ4ojF0Z9mFM9tbLzBYCL2BpNCtYbp9uMpp4YtnX0+2sdxU6vi+ffSeAk=
Looks like updated Google Play services might be causing problem. Help would be appreciated.
This logcat warning is caused by a bug introduced in Google Play Services 9.x. It can be safely ignored, I don't believe it causes a crash, so your crash may be caused by a different issue. The message should go away with a future update to play services.
This issue has been acknowledged by an engineer at Google in the answer to this post.
I had the same issue recently. What caused it for me was when the phone auto updated Google Play Services to version 9.0.83.
The only solution I found was uninstalling the update and allowing Google Play services to re-update.
To remove the update:
Settings > Apps > Google Play services > Hit the three dots and uninstall updates. Then reinstall the updates through the play store.
Start the app and it should ask you to upgrade your Google Play services.
The version was originally 9.0.83 after doing these steps it downgraded to 8.7.03.
I don't feel like this is a solution since I have a few people testing my app and a few of them are having the same issue (the ones on version 9.0.83). I'm not too sure what changed with 9.0.83
I was also getting same exception and I fixed it.
Note: I am working on google analytics and was getting this exception. But my app was not crashing I was getting this in Logs. you can also try this solution.
add this in project level gradle file.
classpath 'com.google.gms:google-services:2.1.0'
and this one for module level gradle file.
compile 'com.google.android.gms:play-services:8.4.0'
and move `below plugin at the end of file (at last line) of module level gradle file.
apply plugin: 'com.google.gms.google-services'
`
I was facing same problem after changing the system and project config.
Try these steps:
Check if you have enabled offline work for gradle: Goto File > Settings > Gradle. Deselect Offline Work if it's checked.
Then confirm if you have latest version of google services mentioned as dependencies in project level build.gradle:
classpath 'com.google.gms:google-services:2.1.0'.You can find latest version here: https://jcenter.bintray.com/com/android/tools/build/gradle/
Clean and build the project after the gradle sync completes.
These steps solved the issue for me. In case you've changed the system used for building this app, make sure to update the SHA1 in your project on Google Developer Console and update the Maps API key in your android project.
What fixed it for me was deleting the debug.keystore file found in the .android folder.
figured it out after reading that the debug.keystore file expires after a year and the system needs you to delete so it can create a new one.
https://developer.android.com/tools/publishing/app-signing.html#expdebug