I created a new app today and put it on Google Play after testing on the emulator and 2 devices I own. A friend then downloaded it to give it a look-see and said that he did not see any ad (using AdMob). This baffled me 'cos I had seen the test ad on my development device and in the emulator.
I thought I had done everything I needed to do correctly with the new app, but I checked two older apps that I'd created previously which also used AdMob, to satisfy myself.
I ran these two apps from within Android Studio on my Motorola Xoom connected via USB. I seem to be now getting errors in LogCat like this across all 3 apps...
E/GooglePlayServicesUtil﹕ The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.
Two of these apps are apps that I've not touched for some time, I just re-opened them in Android Studio today to see if they could help me understand why the new app wasn't working as I'd expected. I can confirm 100% that ads have been working in them prior to this.
I do see the test AdMob ad on my development devices. I also see:
I/Ads﹕ Ad finished loading.
Eventually in LogCat.
Can anyone help me understand this better? I looked at another SO question and it seemed to be related to location services, but none of my apps make use of location.
I checked on the AdMob dashboard, and it is also clearly showing that the new app has a number of impressions today, which is even more confusing.
I am using Android Studio 0.4.6.
I am using Google Play Services com.google.android.gms:play-services:4.2.42.
I have performed a Clean, Rebuild on these projects and I have stopped and restarted Android Studio. Any input appreciated so I can understand what's truly going on here.
There is nothing to be concerned about.
Current version of Google Play Services seems to have a benign bug where this message sometimes gets displayed:
E/GooglePlayServicesUtil﹕ The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.
But it doesn't stop your app from working or ads being displayed.
If there are no ads available for a certain area/device then occasionally an ad won't get displayed. But that is perfectly normal. It's why you should use mediation to make sure you always have ad fill.
Related
i'm new to coding and as a final project on a course I decided to build and Android app, since it's what I want to focus my studies later (kinda regret it now...).
My idea is about an app that will have GPS services and actions based on GPS locations, so I started following tutorials from the basics up, now i'm following a basic tutorial about a GPS app (in Kotlin) that just displays the current location with an on/off switch.
I'm still getting familiar with Android Studio and all the methods etc, but as of now I got to solve many of my problem since the documentation is plenty.
For the last 4-5 days i'm struggling to get it to work since i never got to get the location from it, I've followed the tutorial, I've copied code from repositories that followed the same tutorial, but in the console I keep getting:
2022-07-13 15:06:25.275 4791-4815/com.example.gps_activity_test W/GooglePlayServicesUtil: com.example.gps_activity_test requires the Google Play Store, but it is missing.
2022-07-13 15:06:25.275 4791-4815/com.example.gps_activity_test W/GoogleApiManager: The service for com.google.android.gms.internal.location.zzaz is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
up until today the second error message was logging
android.gms.internal.service.zap
instead of
android.gms.internal.location.zzaz
I've been searching for service.zap, or googlePlayServiceUtil or GoogleApiManager, but nothing to help, and I only found this github issue for an errorcode similar to mine, but I haven't understood much anything about it.
I've reinstalled google play services in my emulator, and tested the app on my physical phone but no luck.
Also using custom logging messages or displaying a text update only goes so far in the code before this problem blocks it from proceeding
The app seems to work fine, it doesn't crash, but the UI values stay at 0.0 not updating with the location informations, since I guess the app doesn't receive.
All the videos i've watched only ask for COARSE_LOCATION and FINE_LOCATION while only adding implementing the 'com.google.android.gms:play-services-location:20.0.0' copied from the documentation and also added and removed others following what I understood from the docs
As a beginner, the android doc is kinda a nightmare to understand plus it seem to constantly change and reading questions/answers or tutorials from just a year ago, many methods or arguments are different or deprecated.
Any insights on what to do?
I've been stuck for 4-5 days with no step forward...
Going on with the tutorial seems useless, since it is all based on locations, so even if I copy all the new features and functions, I'd still be stuck not knowing if they're working or not.
thanks for your time, sorry if I didn't provide enough context
Reinstalled Android Studio
Reinstalled the emulated device (specifically choosing one that has already google play store installed) and opened the project again.
Now it works also on my physical phone.
I am trying to use my own/REAL AdUnits instead of the TestAdUnits but I have no idea where to get the Test Device Ids for my iOS and Android devices.
Docs say to look at the logs to locate the test id, but I have inspected everything that gets printed to the console and it does not print either of the devices test ids.
I am building and running my project in VS Code
After a while of looking through logs, I realized there are some missing steps in Flutter's package explanation.
First, Firebase needs to be linked to you AdMob app, AND you need to re-download the GoogleService-Info.plist file for iOS and the google-services.json for Android.
After that, in iOS you need to go into Settings -> Privacy -> Advertising and disable Limit Ad Tracking. This will allow for the ID to be printed.
I think you probably searched on admob and adsense console.
maybe the google play developer console will be helpful.
For now im only using testAds since my app is not done yet.
All my new apps get "ERROR_CODE_NO_FILL" error and get "I/Ads: No fill from the ad server." and "W/Ads: Failed to load ad: 3" errors in the Logcat.
My old apps still getting ads (from the same AdMob account), test ads are working well.
I tried to install the app on another device and I got the same problem also created new ad units, tried different version of Android Studio but there was no hope and the weird thing is that when I create new APK files from the old projects they get the same error however the old APK files getting ads normally (Both of them uses the same ad unit id, AdMob account and same app id). I have been searching for a solution for a week, I tried everything and got the same error. everything looks normal but I don't know why I get this error, so please help me. I was working on a project and I am done but I can't get ads any more.
PLEASE HELP ME. and sorry for my bad English.
I had same problem for admob ads .i added test id then also not showing ads on device. it's disable for 3-4 week after publishing live.
because there is only one download so.when you have 5+ installed device from store then your automatically showing on app.
if your admob ads are not showing on app don't worry it's will enable after few days.
I'm facing the same issue as in Stack Overflow question "Google Play services are updating" in Google Maps API.
Unfortunately, out of nowhere, some of my users are suffering this issue, as well as my own phone. On the other hand, for other users it seems to work perfectly fine.
This issue appears only on maps in my app.
I've tried to clean Google Services's cache on my own phone - still nothing.
On my emulator it works fine.
I've searched all over the Internet and haven't managed to find a working solution for this.
The most important part is this: Most of the solutions that I've found were ones that needed to be done on a specific device, like cleaning a cache and then restarting the phone. But, when we are talking about an issue that occurs and harm a large portion of my users - there has to be a solution on which I can use in order to help them all at once, by myself, without them needing to do some actions on their own phones.
Otherwise, it would be very frustrating for them, and it would make some of them uninstall my app, and because of what? A bug that I have nothing to do with? Everything worked just perfectly fine until about two days ago, and I didn't make any changes to my app since then at all... so... why?
This bug is reported by many people in the Google issue tracker. It looks like a wide range of Huawei devices is severely impacted by the latest Play Services update to version 12.6.73. Apparently something changed on the Google side and they are currently investigating what is happening.
The issue is tracked in the following bug:
Authorization Failure in Google Maps Android API v2 (Google Play Services 12.6.73, Huawei devices)
Star the bug and follow messages from Google engineers.
UPDATE 2018-05-15
Some messages from the bug
Have just got off the phone to Google and Huawei. Huawei seem to be
admitting responsibility. They told me there is an EMUI update due in 1 to
2 weeks that should fix "all google maps issues".
Also ah...#google.com states
Google has been able to reproduce the problem on a physical device and is now focusing on addressing the root cause through either a fix or other mitigation.
It looks like Google and Huawei have to look into this issue together in order to provide a permanent solution.
UPDATE 2018-05-16
Google posted the following message in the bug
In collaboration with Huawei, Google engineers have identified the root cause of this issue as an unexpected change to the filesystem permissions. The issue can impact any Android app on a Huawei device which renders a Google map.
Our engineers are preparing a new version of Google Play Services which should resolve the problem. It will be targeted to devices running Android 7.0 Nougat, or higher. We will post another update with the status of the rollout.
Thanks for your patience.
UPDATE 2018-05-17
Finally good news from Google
We are pleased to report that a beta version of Google Play Services is ready. We believe this version mitigates the issue on Huawei devices running Android 7.0 Nougat, or higher. An important caveat is that each time the device is rebooted, you will need to wait about one minute before launching the affected applications.
Starting today at midnight (Pacific Time), the beta will be rolled-out to a segment of the community that has signed-up for the Google Play Services Public Beta Program. It will ramp to increasing segments of the beta audience over the next few days. We invite you to join the beta program at https://developers.google.com/android/guides/beta-program to obtain an early release of this and future versions of Google Play Services. Once beta testing is complete it will be rolled out in stages to all users.
UPDATE 2018-05-18
As a follow-up to our last update (comment#342), we believe this issue is fixed in Google Play Services version 12.6.85. If you are still encountering the problem, please ensure your device has this version installed.
As previously noted, there can be a delay (usually less than one minute) between the time the OS is finished booting and Google Play Services starts. If you launch one of the affected apps during this window, it may not render a map. If this happens, re-launch the app after a minute or so. Subsequent launches of the app should succeed every time.
FINAL UPDATE 2018-05-22
As of 10:00 AM (PDT) on May 21, 2018, Google Play Services version 12.6.85 was pushed to 100%, following the initial beta rollout. We believe this resolves the Google Play Services issue on all impacted Huawei devices.
Huawei is working on a longer term solution which is beneficial to its users and developers.
We apologize for this incident and the impact it may have caused. We are conducting an internal investigation of this issue and will make appropriate improvements to our systems to help prevent future recurrence. Stay tuned for an Incident Report.
AFAICT there is nothing an app developer can do to fix it. As #xomena mentions in her answer Google is working on it.
Just to add the complete solution for an end-user here:
go to Settings > Apps & Notifications > App > Google Play Services > Storage
click Clear Cache
go to Manage Space and click Clear all data
Be aware that the issue reappears if you reboot your device
Someone created a video you can refer your users to at https://youtu.be/VgMtZnyem5Y
It's is going to be fixed soon, guys:
https://issuetracker.google.com/issues/79405933
Go to Settings → App → Google Play Services, and disable it to go back to the factory version.
Restart the phone and go to Google Play Store to do the update on Google Play Services.
It works for me. I can see the Google map again in a third-party app. If it says uninstall/disable, do that.
There is nothing you can do at this time, except clear Google Play Service data (without rebooting the phone). At the next reboot, maps services get updated, and the issue will be there again.
We just can wait for Google to fix it with a mitigation update, and Huawei give users new firmware via OTA that better comply with the last Google API without what seems like an "authorization" issue.
Today Google released version 12.6.85 on the beta channel which fixes the map bug.
You can suggest your user to subscribe as a beta tester:
https://play.google.com/apps/testing/com.google.android.gms
Or direct download on APK mirror:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-6-85-release/google-play-services-12-6-85-040408-197041431-android-apk-download/
I tried disabling to restore to the factory version - unfortunately this means most of my apps required Play Services will not run, and I can't seem to reinstall the latest version.
I am using Honor 7x.
I am in the process of releasing a game on the Play Store.
I had previously set up AdMob banner and interstitial ads using test ids. These worked perfectly. No problems. The app was then uploaded, with test ids being replaced with the correct add unit ids that I created in AdMob.
The ads did not show up, and the game would crash. The situation then gets weirder: after narrowing down the issue to AdMob, I reverted all add unit ids to their respective test ids. The odd behaviour is still there, even though functionally, the game is identical to what it was before attempting to release it.
One other thing to note is that prior to release, the app was not being signed under publishing settings. I also changed that back to what it was before. I'm not sure if it has something to do with signing the app... Previously compiled versions from before attempting to release still work fine.
Has anyone dealt with such an oddity, and is there a remedy?
So eventually I came right with all of this. I'm not sure what exactly happened to cause this. Could have been me accidentally deleting a file or folder. Could have been something got corrupted. Regardless, the solution was simple. Delete everything to do with admob from the unity project. Re-install. All is peachy.