I already successfully implemented Inmobi in my Android app.
But the problem is reward ad or Interstitial Ad showing in landscape and I want to show as only portrait mode.
I have searched and found that this can set via Ad experience settings and after that I created custom ad experience template, but how to set this custom template in my app?
I have made a mobile app with Flutter and I use Admob.
Users started to use my app and when I check on Firebase it says users view non personalized ads. What can I do to make Admob show personalized Ads to my users?
Good afternoon, I am try to implement ads in my application but my real AD does not appear, only test AD, in the admob tab it appears that more than 300 requests were made, and there is no ads in the application. Is it necessary for me to publish my app in the play store so that the ads start to appear? And my account has been verified for a long time. In my Logcat appear this error Ad failed to load: 3, what i needed to do , to the ads start to showing?
page admob
Logcat
As per the Documentation you are getting the following error code:
public static final int ERROR_CODE_NO_FILL
The ad request was successful, but no ad was returned due to lack of
ad inventory.
Constant Value: 3
If you are getting this error, then your code is correct. The issue is
that AdMob does not always have an ad to return for every request.
This may happen particularly if you have just registered your AdMob
publisher ID, as it takes some time and multiple requests before the
new ID starts returning ads.
I also faced the same issue. My app was showing test ads, but not real one.
In my case ads started showing up when I uploaded my app to Google Play.
To confirm your app shows ads correctly, you may first add your app to test tracks first.
Error code 3 means your implementation is correct but your app is not approved by google admob,so you have to submit your app for approval, once your app is approved than your app will start receiving ad after 24 hrs and you have to setup your payment method in google admob.
you can submit your app through this link for approval:
https://support.google.com/admob/contact/android_APK_submission?hl=en
If you are using app-ads.txt for your app, then you also have to include this line in your app-ads.txt file in order to load ads using the demo ad units:
google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0
Here the official Google AdMob reference: https://developers.google.com/admob/android/test-ads
It shows when your device is not connected with Test Mode in your AdMob account. Connect your device with test mode and try this error will resolve.
https://apps.admob.com/v2/settings/test-devices/list?_ga=2.248138183.156733708.1671428691-2046682952.1670650994&_gac=1.127285631.1670650998.Cj0KCQiA1sucBhDgARIsAFoytUvUl2cXmiqt4eGOJlPz7EOFYJxnbpcLX3uIEhk71c3oHZ3BxMsgBE0aAlkcEALw_wcB&_gl=1*1ubza84*_ga*MjA0NjY4Mjk1Mi4xNjcwNjUwOTk0*_ga_6R1K8XRD9P*MTY3MTQyODY5MS40LjAuMTY3MTQyODY5MS4wLjAuMA..
I just migrated one of my apps from Google Plus signin to Google Signin and updated some achievements code, as I was using deprecated methods and Google Plus is disappearing.
To my surprise, the permissions dialog that shows up when a user signs in to Google Games has change in a scary way:
Before, it said the app could:
View your langiage preferences
View your age range
Share your Google+ profile information and view and manage your game activity
View your basic profile info
With the new version, it just says:
Create, edit, and delete your Google Play Games activity
Does anyone know where this is coming from?
In the process of migrating libraries (I also installed Firebase analytics), some new API keys were automatically created in my Google APIs dashboard, and an additional OAuth 2.0 client ID. There, under "OAuth consent screen" I can see many scopes my app is supposedly using that look unnecessary to me:
../auth/plus.circles.members.read
../auth/plus.login
../auth/plus.profile.agerange.read
profile
../auth/drive.appdata
openid
../auth/plus.login
../auth/plus.profile.agerange.read
../auth/plus.profile.language.read
../auth/games
../auth/games_lite
../auth/plus.moments.write
Can I delete the ones that I don't think I need? Will this remove the scary warning?
One of the other apps I have not yet updated shows fewer scopes (still more than I need):
../auth/plus.circles.members.read
profile
openid
../auth/plus.login
../auth/plus.profile.agerange.read
../auth/plus.profile.language.read
../auth/games
../auth/plus.moments.write
Thanks
Edit: From what I've found out so far, the auth screen depends on the way you create the client used to sign in, and I think I'm using a pretty standard way:
mGoogleSignInClient = GoogleSignIn.getClient(this,
new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_GAMES_SIGN_IN).build());
Edit 2: I went to my API console, restricted the uses and scopes of my app, resubmitted my OAuth screen for approval, GOT IT APPROVED... and the Android app keeps showing the scary auth screen.
I also contacted Google for help from the Play Dev Console. Received no reply.
I'm just following Google's advice. As stated here,
// This way you won’t get a consent screen
GoogleSignInOptions signInOption = GoogleSignInOptions.DEFAULT_GAMES_SIGN_IN;
https://developers.google.com/games/services/checklist
Edit 3:
After I got my simplified OAuth screen approved. Firebase created new api keys on its own, so I'm guessing it doesn't like the changes I made manually. I am alos getting non-fatal crash reports from users rejecting the app permissions (error 12501) after trying to access the achievements screen. Google has not responded at all.
I've faced the same problem and got it fixed using
GoogleSignInOptions.DEFAULT_SIGN_IN
instead of GoogleSignInOptions.DEFAULT_GAMES_SIGN_IN
i am applying ads on my applications using android studio 3.0
but when i run the application it give this notification in Run Panel
Google Play services out of date. Requires 12210000 but found 10298470
help me fixing this problem
You are requiring services 12.0.0 in your build.gradle file, but the emulator or device has an out of date google play services. If you are using an emulator, you need to use an emulator with Google Play so that you can update the services version. https://stackoverflow.com/a/35498283/3962777