I have integrated an app with Google+ platform as well as a Google+ button so far. Things seem to be working ok, but I keep on getting this message appears in the logs quite often..
06-30 15:14:58.296: E/ActivityThread(2308): Failed to find provider info for com.google.plus.platform
Has anyone seen this before. Can anyone explain to me what it is as I cannot find any explanation for it yet?
Well I think i have found the reason for this message after adding admob to one of my new projects. Fortunately its is not an error, but a warning.
And it happens if the application google+ is not installed in the phone where the application runs. It seems that admob tries to find specific ads for a person based on his google plus account if he has installed the app in his phone.
Or it just throws the message
Failed to find provider info for com.google.plus.platform
and continues to show general ads.
What i have done was to install the google+ app in my phone and logged in with my account.
And after that when i run my app it doesn't throw this message when ads are being refreshed.
So you can't do something to fix this warning and you should not be worried about it as your ads will continue to show without a problem.
if you are getting this error while you have added Google Admob add, then it comes usually due to the wrong ID we have putted in the xml file:
ads:adUnitId="ca-app-pub-1403552879675846/2424242"
Its not a publisher ID, but it is the application unique id:
In Admob, go to Monetise, All Apps.
ckick on your app to open
you will get 'Add Unit ID' just below your app
Now replace it in xml file and run it.
Related
You guys have any idea as to what may be the possible cause of this error in UMP SDK for Android?
Publisher misconfiguration: Failed to read publisher's account configuration; please check your configured app ID. Received app ID: ca-app-pub-3940256099942544~3347511713.
ca-app-pub-3940256099942544~3347511713 is Test Application ID
and this Error Pops up when trying to use Obtaining Consent with the User Messaging Platform
I followed the procedure as outlined in https://developers.google.com/interactive-media-ads/ump/android/quick-start
I do not get an option to create / view Funding Choices account, but still this is a test application id.
public void onConsentInfoUpdateFailure(FormError formError)
{
}
I fixed this error by logging into Admob and configuring my GDPR and IDFA messages here: https://apps.admob.com/v2/privacymessaging
After I configured and allowed those messages the error went away, and it worked even while displaying test ads on an emulator.
I faced a similar case and the solution is simple. You're using the sample AdMob ID: ca-app-pub-3940256099942544~3347511713 and thats the case.
It's good enough to displays test ads but not to set user's consent and it end up with an error. You are actually trying to send the request in AdMob test account what is not allowed.
For UMP to works, you need to create a real (your own) AdMob account and use its AdMob ID. If you still need to run test ads, just set the test device ID https://support.google.com/admob/answer/9691433?hl=en
I'm trying to add support to social login with Google on my application using the package google_sign_in.
I got to add support of that on iOS, and it's working. But on Google, for some unknown reason, it can't work anymore.
Few days ago it was working, but now it just start the following loading, and then shows the error Couldn't sign in:
On OAuth consent screen, since I updated some informations on my application, I needed to request again the authorization, but it says that the previous consent is still in use... but I don't know if would be the root of the problem and I really need to wait 4~6 weeks to work again on Android.
The problem was fixed. It was being caused by a wrong jks of Firebase.
I am getting this error but when I put test ads they work fine but original are not working please help me out in this.
Error - W/Ads: Failed to load ad: 3
this is said ,as per google support
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
My answer is
Add your payment information on main page of admob site, if you haven't already done this.
You have to publish game on google play at least to internal test to see ads, for my case there was the message when I'm installing game on phone "Unknown developer".
For more information add your code to the issue.
I am using Android in app billing for in app purchases.
In rare cases a number of my users are reporting this error:
"Error retrieving information from server. [RPC:S-7:AEC-0]"
This is happening in production and not in testing. And I'm unable to reproduce this locally to debug.
What does this error mean and how to resolve it?
You might want to take a look at This Previous Question
Check if you are using latest version of Google Play.
OR
Following the steps below.
RPC:AEC:0 error is known as CPU/RAM/Device/Identity failure.
Only possible way you can follow to get rid off this error is,
Go to settings >application > Play Store >Clear Data & Clear Cache.
Go to accounts >Google >Remove account.
Reboot device.
Again Settings>Account >Google >Log In.
Refer to this link
OR
Factory Reset is the last working option, if none of the above worked.
I believe that this might have the solution that you are looking for. Since the question mentioned that he/she noticed the issue with a test account, it may be that your customers are not using the latest version of Google play or that they need to clear their cache.
You can also View this Youtube Video titled "How to Fix " Error retrieving information from server [RPC:S-7:AEC-0] "
In my case the problem was that Google suspended the merchant account for the application.
I've a major issue with linking my Play Developer Console to Google Wallet. I've already search the Google Help for any solution and didn't find one. The problem is, that Error message appears after hitting “Set up a merchant account now” button in my Google Play Android Developer Console (Settings/Account Details). After that another screen pops out with an error:
Oops! An error occurred while processing your request.
Regardless of any steps I've done such as changing to a different browser(Firefox to Chrome and back), clearing cache&cookies and so on... nothing is working.
Any ideas?
Any resolution yet?
I just encountered the same issue. Also no followup from google teams.
A possible solution I am looking into is to use an alternative payment system such as http://www.zooz.com/
I have the same problem a few days ago. After exchanging several emails with the service, they didn't know to tell me what happened, only they made me waste time. Then I started to fill the form on the Wallet account to avoid having to write every time I tried to link the accounts, and in this form itself is run the Javascript and I notice that my address could not be longer than 64 characters... I wrote a short version and I got my accounts linked.
In short, if you can not link your Google Play and Google Wallet accounts, check the size of your inputs, Javascript alerts dont work fine.
BTW: Outside USA could also be the fault of the VAT-ID, try to leave it empty.