We have received a warning from Google about Microsoft AppCenter SDK (Distribution?) in one of our products. According to the latest changes in Google Play policy - I think Google didn't like the Distribution Package.

The published version has been built using DistributionPlay NuGet package variant, as it is described here https://docs.microsoft.com/en-us/appcenter/sdk/distribute/android#prepare-your-google-play-build
After a short research, I've found that Microsoft.AppCenter.Distribute.Android.Bindings.dll from Microsoft.AppCenter.Distribute package is still included in the released .apk file. That happening because of the main Xamarin.Forms project based on .NET Standard consumes regular Microsoft.AppCenter.Distribute while the Android project consumes faked Microsoft.AppCenter.DistributePlay package, so the APK contains both dll's - one from the fake NuGet package and one from the real one.
That can be easily re-checked by decompiling the next dlls:
(don't forget to decompress dlls by using this tool)

Microsoft.AppCenter.Distribute.dll - contains dummy code from Microsoft.AppCenter.DistributePlay
Microsoft.AppCenter.Distribute.Android.Bindings.dll - from the regular Microsoft.AppCenter.Distribute NuGet package;
Repo with examples + fixed NuGet, see readme.
https://github.com/bondarenkod/appcenter_distribution_play_issue
OR
I've developed a small fix. We just need to include faked assembly not only for the android project but for .NET Standard project also.
https://github.com/microsoft/appcenter-sdk-dotnet/compare/develop...Barvy:issue1515
AppCenter.LogLevel = LogLevel.Verbose before your call to AppCenter.Start(...) and include the logs here:Hi! Thanks for getting in touch with us!
I left some comments in your contribution PR.
The fix has been released in the 4.3.0 version of App Center SDK. Please update the App Center SDK to the latest version and let me know if this issue still persists.