Develop Reference

Critical issues have been reported with the following SDK versions: com.google.android.gms:play-services-safetynet:17.0.0

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

Google Play Billing Unity plugin alternative

I'm new to Unity IAP. When looking for a way to integrate Google Play IAP into a unity project, I found the "Use the Google Play Billing Library with Unity" documentation which states:
The Google Play Billing Unity plugin will not be receiving updates moving forward. This means that the plugin will remain specific to Google Play Billing Library 3. Additionally, any apps that are updated after November 1, 2022 will no longer be able to use the plugin.
Does Google provide an alternative? Or should I just use Unity's IAP integration directly instead?

I came across the same text just now. I believe you are correct in your assumption that Unity IAP is the correct replacement for this, since according to their documentation UnityIAPGooglePlay the current version of this plugin already uses Google Play Billing v4, which is the minimum required version starting Nov 1.

How to update Google Play Developer API version to v3?

Got this warning while publishing the app:
We’ve detected that your app is using an old version of the Google Play Developer API. From December 1 2019, versions 1 and 2 of this API will no longer be available. Update to version 3 before this date.
https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html
I'm wondering why I got this warning as I'm not using Google Play developer API explicitly.
Can anyone tell me what does it mean and how to update it to v3?
The above link is not enough to solve the issue.
Upgrade every library to it's latest version already!!
Here is the snap of libraries I've used

I had the same problem. I had to update google-services.
See https://firebase.google.com/support/release-notes/android#2019-08-22 : "The google-services plugin for Android (v4.3.1) is now available. This release removes calls to a deprecated API. For more information, refer to the Firebase Android SDK Release Notes."
Hope this helps you!

Xamarin Android: Google Pay integration and Play Service 16.0.0.0

So in the Google pay integration with Android, Google says that devices should have play services 16.0 or more. But so far I can only find version upto 14.X.
What gives? has anyone ran into this issue?
I am using Stripe for integration. For some reason, I am getting this exception:
Android.Gms.Common.Apis.ApiException: 10:
then bunch of anonymized classes.

If you check the currently available version of GooglePlayServices on maven it is 16.1.2
But if you check NuGet for Xamarin.GooglePlayServices with pre-release enabled the latest version available is 70.1501.0-preview2 which if I am not wrong targets the maven version 15.0.1 and since I could not find any release notes in regards to when will be the latest GooglePlayServices NuGet would be released I would suggest you will have to wait until it is released.
A quick question though why do you need the latest GooglePlayServices I am pretty sure it is not needed for Google Pay integration.

As G.hakim points out, you need a version that supports Google Pay, not necessary the latest, although it's recommended to inspect and update the version of the libraries you typically use.
Google Pay specific logs are shared at a system level. That is, you need remove the filter in the logs to show all logs. If you then filter the output with the term "wallet" you should be able to find elements of the type WalletMerchantError that provide more details about the specific problem in your configuration / setup.

Migrate from a Google API Project to Firebase (Android or iOs)

I read the article about migrating a google api project to firebase:
doc
Has the migration of an Google API project to firebase an effect on the functionality of the current productive version of an App in Google Play or iOS? Will the defined API Keys (Oauth2 client ids, Google Places API keys, server keys...) still work after firebase migration?
Thanks!
Smilingm

I found a possible duplicate Question which was answered here:
Migration of Google Project to Firebase Console
I will try to migrate soon and check if problems occur. Update follows...