False positive for AdMob detection by GooglePlay - google-play

In Google Play Console, under AppContent, we found a warning under Ads section stating:
We found ad SDKs in your app
Although we still can publish our app for now, this warning is bothering us.
It does not allow us to declare No, my app does not contain ads. The save button is greyed out.
The problem is, we did not integrate AdMob in our app! So what could trigger this false positive?
I have ran gradlew -q app:dependencies and extracted out our productionRelease section. A copy of the full dependency list can be found here: http://axzae.com/dependency.txt
The only "ads" related dependency we found is:
com.google.android.gms:play-services-ads-identifier:{strictly 17.0.0} -> 17.0.0 (c)
But we are just using adid as a unique identifier for identifying user. Could this be the false positive reason?
Any helps would be appreciated. Thanks.

If you or one of the libraries in your app are using Identifier for Advertisers (IDFA), Google play will tell you We found ad SDKs in your app
But if you are not showing ads do not worry about it, in this case it is indeed a false positive and Google know that and tell you to leave it as is (see the image below)
It is just for Google Play to check if you lied about the ads in your app, so they can later remove your app.
I found that some analytics SDKs uses this technique to identify unique users more efficiently.
for example OneSignal SDK uses this.

Related

Can't publish initial build of app in Google Play Console

When I try to publish a release in the Google Play Console, I constantly get this error:
Your app cannot be published yet. Complete the steps listed on the Dashboard.
And yes, I have indeed completed all the steps listed in the dashboard. I am using the new Play Console Beta, this is possibly related. What do I need to do before I can publish a release? Is there a hidden step?
After some searching, I found the button 'Use classic Play Console'. Apparently there are some steps to be finished that are simply not visible in the Beta:
Click on Use classic Play Console
Go to Pricing & distribution
Check the Content guidelines checkmark
Check the US export laws checkmark
Press Save draft
And you're good to go!
I had that problem and fix it. the problem caused by google console because they added one additional task in the app content about wither your app is consider a news app or not. so go to the inbox in your app and you will find that message from google click and you will be leaded to the content that you should fill. I hope that help any one having that issue.
I also had this problem. It was regarding setting your app as free from the App Pricing section as my application was free. So after setting that, I released my app.

My Android app is not displaying in play store search list, even if the app is in published status

I have developed an App and published the same in google play store console. Even after many days the app is not getting listed in play store while searching using App Name.
I have tried searching using the project name. Its shows my app while searching.
It's normal. It need time, interactions and downloads to scale the list.
Don't worry
Please enlarge the image and the answer is there

Google Play Testing Link Redirected to Application in Production

I am trying to update an application from the Google Play Console. The new version of the apk is uploaded as a beta test and I have obtained a link to download the beta test app. However, the link just redirects me to the Google Play where the current version of the app is shown.
Is there something wrong with my operations?? The testing link is obtained in the beta test page tab, from the link in "Beta testers" box. Does anyone know how I can obtain a link to the beta test app rather than the currently published version??? Many Thanks!!
Per:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
You need to be registered as a member of a Google + or Google Group that is designated for Beta or Alpha testing by the Developer. If you are not registered, you will only be able to download the production app from Google Play, NOT the Beta or Alpha version of the app from Google Play.
Having the "link" won't be sufficient, you need to opt-in to the beta or alpha via Google + or Google Group.
Please note that even if you properly opt-in via Google + or Google Groups as defined by the developer, you will need to wait several hours (perhaps 2-8 hours) for your status to propagate via Google Play.
So, perhaps you need to wait 2-8 hours even if your Beta/Alpha status is proper?
Hope this helps!

Google Apps Marketplace SDK : setup a contextual gadget

Ok, so without much notification given, adding market place listings to your vendor profile is no longer possible. The 'create new listing' button is greyed out.
I need to make changes to an existing marketplace listing but that gives errors. We are forced into the new SDK.
So I went ahead and enabled the apps market SDK, filled out all details including images of all sizes, add a COB extension for the contextual gadget and saved the whole thing.
A minute later I return to make a modification and dang... error: "We are looking into this.".
#Google: HELP !
UPDATE : I can reliably reproduce the error as explained here.
Enable Google Apps Marketplace SDK in your project
click on the gear icon, you will be directed to the old API Console
Fill out all details
Add a COB extension (Contextual gadget)
Save everything
Close the API console
Go back to your cloud console -> Google Apps Marketplace SDK
Click on the gear icon again
ERROR
Tested with several google accounts on different computeres and multiple projects on the cloud console.
#jonathanberi could we have a status on this issue, please? We are experiencing the exact same issue and we are unable to publish our app (which is ready) because of this bug. We have tried both creating a new Google Apps console project from scratch as well as modifying a draft of a yet to be published page with the same result. Is any information that we could provide to help?
You must fill out parameter name and a paramter value or your cloud console will return errors and you will not be able to recover from this.
Ouch, that were 3 useless weeks....

admob wp7 sdk dont work, alternative ad networks?

i use the admob wp7 sdk for displaying adds in my apps, but i dont see any, it looke like:
<google:BannerAd
xmlns:google="clr-namespace:Google.AdMob.Ads.WindowsPhone7.WPF;assembly=Google.AdMob.Ads.WindowsPhone7"
AdUnitID="MY_AD_UNIT_ID">
of course i insert my adUnitID, when i start my app i dont get anything to see, also when i enable test mode i cant see anything, what could be worng? on the homepage i see that i got requests because it counts up, but nothing to see.
other question:
are there any other add providers instead of smaato and adDuplex which provide a WP7 sdk?
As of today the Microsoft Ad SDK for WP7 can now be used in all territories where the marketplace is available.
Alternatively you could consider AdDuplex
I would recommend looking at the documentation and contacting admob support. Its a third party control so you would be lucky to find someone on here who can offer advice.

Resources