I was checking my developer console and I found a yellow high lighted message on the top of Application list saying : "We have identified a potential advertising ID policy violation with your app(s) , Please review the flagged apps".
and I can see a yellow flag on the apps list with another message saying :"We have determined that your app uses a library or SDK (com.revmob.client) that is in violation of the Developer Program Policy. Please note that beginning Aug 1st, 2014 the Developer Program Policy requires all updates and new apps uploaded to be compliant with the advertising ID provision of the Developer Program Policy. Apps in violation may be subject to permanent removal from the Store"
And i understood that the issue is due to an older version of revmob sdk. In my app, the revmob sdk version is 6.4.2 and the latest version available is 6.9.8
And when i searched over google regarding the same, i found few saying updating the sdk is enough and few saying remove the sdk completely.
Anyone here who faced the same issue please help me out, should i update sdk or remove it completely?
Try install new libs version Revmob Android SDK 7.0.0 - 2014/11/28;
http://s3.amazonaws.com/sdks/revmob-android-sdk-7.0.0.zip
It helped me.
Related
This is my first time submitting an app to the Google Play store, so I'm not very experienced with the process at all. After struggling for a bit to get it to build correctly, I was finally able to upload an app bundle and send it in for review. A few minutes later I got an email saying my app was "vulnerable to Intent Redirection" and recommended the following article for support: https://support.google.com/faqs/answer/9267555. The problem is I don't understand much of what the article is saying! As far as I know, I haven't messed with anything like this. I've only downloaded the base NDK and SDK stuff from Unity Hub, and I haven't changed any of the code in Android Studio at all. I asked Google for support, and they said:
"We’ve identified that your app is using the AliPay SDK or library, which facilitates the transmission of phone number information without meeting the prominent disclosure guidelines. If necessary, you can consult your SDK provider(s) for further information or please upgrade AliPay SDK version to 15.5.5 or higher."
Please help! Is there an easy fix to this that I'm missing somehow? I don't even know what AliPay is, as I said I'm a total beginner here. In case it's useful info to have, I'm using Unity 2019.2.13f1 on a Macbook Pro running High Sierra 10.13.6.
Well, do what the message says "upgrade AliPay SDK version to 15.5.5 or higher".
Just go to Android Studio and open your build.gradle file then update that lib version. It will be marked with a yellow line, that means that lib has an update. Focus on that line, then do Alt + Click then Enter, now sync and you've done. Upload the new apk.
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.
I received this message today:
Hi AdMob Publisher, In early July, we sent out a notice to AdMob
Publishers who have apps running on SDK version 6.4.1 and lower, to
inform them about deprecating SDK versions and the need to upgrade by
September 15, 2016. We apologize for any inconvenience or unclarity
that the email may have caused to some developers. To ensure that you
have sufficient time to make the changes, we have extended the
deprecation date to October 17, 2016. We also reevaluated the SDK
versions being deprecated, so here is the updated information. What
will happen starting on October 17, 2016: • All support for non-Google
Play Services supported SDKs and Google Mobile Ads SDK version listed
here will be deprecated. • This means that all traffic from these SDKs
will be disabled. What you will need to do: In order to ensure that
your AdMob ads continue to serve after October 17, 2016, please
upgrade your apps to run on the minimum SDK versions listed here. If
you are using a Google Mobile Ads SDK version from Play Services that
is listed on this link, you are not required to take any action. If
you have any questions, please contact us on the developer forum.
Thank you, and stay tuned for more updates and tips. Cheers, The
AdMob Team
I am using Play services Version 4.4.52-000. Is this version ok? Do I need to update?
Click on link provided in email https://firebase.google.com/docs/admob/android-legacy-release-notes
"Prior to becoming part of Google Play services, AdMob had a
standalone SDK with the following versions and release notes listed
below ( Refer to link ).
On October 17th, 2016, AdMob will stop serving ads to the SDK versions
listed below. If your apps are still using any of these SDKs, follow
our Get Started to integrate with AdMob's Google Play services SDK."
The note you have gotten about the SDK needing to be higher than v6.4.1 refers to a legacy, standalone Mobile Ads SDK that was deprecated back in February 2014, and that had its own versioning system.
If your google_play_services_version > 4 , you don't need to make immediate update however it's good practice to upgrade to latest versions of play services library.
EDIT 7-Oct-2016: If you are using a Google Mobile Ads SDK version from Play Services that is listed on this link, you are not required to take any action.
I think majority of confusion occurred due to version numbers between Admob Standalone SDK and version number of Google Play Services.
I have already upgraded my Cordova version to: 5.0.0 and Google Play Developer console still showing this below alert and that affected my latest APK version.
Your app is using a version of Apache Cordova containing one or more security vulnerabilities. Please see this Google Help Center article for details, including the deadline for fixing the app.
Affects APK version 1.
In my admob account i was getting the following warning message:
Starting March 18, 2013, we will no longer support ad requests made through AdMob SDKs released before 2011. Please upgrade to the latest version of the AdMob SDK here.
i have updated my AdMob SDK in my app that had the old sdk, but in my sites/apps page, next to my app name i have a warning as (urgent SDK update required) .
Has anyone experienced with the same problem?how can i fix it?
i'm getting adds fine in my app,my only problem is that i have this warning in my account
You will still get this message if you still have lingering users on old versions of your app that are making ad requests using old SDKs. If you already launched with a newer version of the Google AdMob SDK, you just have to play the waiting game for those users to upgrade.