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.
Related
I've written to Google Play's support about this issue. At first the flatly denied it, but after I submitted screenshots, database logs, etc... they said they were "looking into it."
Basically every time I submit my app to Google Play... the word "Text" is inserted into almost every EditText field. This includes, Comments, Editable profile fields, etc...
According to the screenshots this appears to be caused by Google Play's automated testing. I've verified that the IP address of the poster does indeed belong to Google.
I've never seen anything like this in over 30 years of programming and I'm at a bit of a loss for what to do... It happens ONLY when I submit an app update to Google Play.
There's really nowhere else I could think of to ask. Has anyone ever SEEN anything like this? How can I prevent this from happening?
When you upload your app, it goes through the Pre-Launch Testing, where it will use test devices to automatically click/type/use your app and try to find bugs and see whether it will crash anywhere.
If you don't want this:
Go to your app in the Google Play Console
Click Release Management on the left
Click Pre-Launch Report
Click the settings tab
Disable it
I have a published android app.
On the first page I go to on developer console it has some stats.
One of the is "crashes and ANRs".
Are these automatically reported by android/play services out of the box?
Or do I need to opt in to them somehow?
mine reports '-' character under this stat. Does that mean zero, or like no data?
Thanks
Yes, you don't need to opt in.
However, to my knowledge, these are only crashes when the user has pressed the submit crash report error when the app crashed.
- means zero or no crashes for that matter
As Google states (https://support.google.com/googleplay/android-developer/answer/6083203?hl=en-GB):
"You'll see all ANRs collected from Android devices whose users have opted in to automatically share usage and diagnostics data. Data is available for the previous two months. For more information about how Android users opt in to share data, go to the Accounts Help Centre."
In the Accounts Help Centre's article, Google explains how users can enable and disable sharing the information and what information is shared.
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 am trying to implement Google in app billing to my Application. I created SKU product id and implemented the billing process in code. While I am trying to test the in-app billind after I enter all the test account details, location, phone no etc and clicking save button it gives the error "Error retrieving information from server RPC S-7 AEC-0". I too published the app created the test account and signed in to the device with test account.
Can any one please help me to fix this. I am totally messed up....
I got the same problem while implementing the in app billing version 3 into my project. It is very awkward issue.we have tried to resolve it and tried to find out the solution but we can not found any solution to resolve it, searched on Google or Stack Over Flow and many other sites but no luck.Have try to remove account account from the phone and clear cache of play store but not getting success.
I think this is fault on previous sample code and that is solved in the new sample code.
what you should do to get solution?
I believe you just have to get the updated code the the in-app billing classes and you shouldn't run into the same problem again.
Google hasn't pushed out the changes to the SDK Manager yet as far as I know. Just copy/paste the new classes into yours and you shouldn't run into the problem any longer.
and also remove your code of purchase product activity(MainActivity in the sample code).
Get the new code changes here:
https://code.google.com/p/marketbilling/source/detail?r=7ec85a9b619fc5f85023bc8125e7e6b1ab4dd69f&path=/v3/src/com/example/android/trivialdrivesample/MainActivity.java
Hope it will help you.
If other ways didn't help, try to make sure that no apps have made any changes to your system settings, for example, disabling the permissions of google play services, something like this.
Note that only cards with a US billing address can be added on the Wallet app.
Go to Settings and tap Credit and debit cards.
Tap the + sign, on the top-right corner, and enter your card's information. If you see a camera icon in the "Card number" field, you can take a picture of your card's number instead of entering it manually.
Tap Add credit or debit card.
Reference:
https://support.google.com/wallet/troubleshooter/3222463?hl=en&ref_topic=3209985#ts=2896139,2896157
I'm trying to implement Google Play Services following Google's documentation and I'm seeing the following when I try to connect my GameClient:
E/Volley: [4953] il.a: Unexpected response code 401 for https://www.googleapis.com/games/v1/players/me
E/Volley: [4953] il.a: Unexpected response code 401 for https://www.googleapis.com/games/v1/players/me
E/SignInIntentService: There is no linked app associated with this client ID.
I've checked that the SHA1 fingerprint of the certificate signing the APK, the SHA1 of the debug certificate, and the SHA1 given to the Google API do match up and they do. I've checked that the app id is declared in the manifest in the application item (I've taken in my case the 13 digit numerical id, not one that also includes a package). I've also checked that the test accounts I'm using are each listed in the Developer Console and they are; they're each #gmail.com too, and they include my developer address. They've each activated Google Plus.
I've tried this from an API 16 S3 device and an API 17 Google API simulator. The app's package name is correctly declared in the manifest, on the developer console and matches the API package name. The app is listed as a client of the game service, and is shown as 'ready for testing'.
In short I'm struggling to see what my mistake can be and what I've missed. I think I have everything from Google's troubleshooting addressed too. I've looked at the main questions here on StackOverflow, and they're covered. Whatever it is I'm missing is probably staring me full in the face. What can I be missing?
I got stuck on this problem for a long time until I realised that I had two strings in my app called "app_id". One from the Facebook SDK and one from Google. I renamed the Google app_id (and changed the corresponding manifest reference) and all was well.
It is POSSIBLE that you have a similar problem. If you can't see the error then I would try to write out the app_id to syslog to confirm that this is not the cause of the problem.
Incidentally, all my Google app_id s (client ids) are 12 bytes not 13, so perhaps you should start by checking that.
Good Luck !
Even after redoing everything, everything, I still encountered the same problem. However, I subsequently encountered a "This package is already in use" error message on Google API even though I had undeleted all projects and removed all clients before deleting these again.
This turned out to be a blessing: The solution to this was to recreate my debug key before adding the new fingerprint to Google API in another new client id.
And lo... my original problem went away.
I hade the same problem and for me it worked to re-link the app in Game services -> Linked apps -> Link another app.
You didn't explicitly state that the gmail accounts you're testing with are added as Google Plus users in a Google Plus community that is configured as the testing community for your app -OR- that you're using a google group as the testing community and those gmail accounts are part of that community.
If you have done those things, then it might be the issue stated here:
https://code.google.com/p/google-plus-platform/issues/detail?id=554
This answer might sound encouraging to solve your problem, but don't get your hopes up. I've done all that the original poster did, plus the things above, and I'm still stuck.
I've even followed all of the tips stated here:
Google Play Game Services - unable to sign in
And it would appear the depths of the chasm that Google lets you fall into regarding GPS is far deeper than the depths I've plumbed. Joy.
I had the same problem ,I am not sure that the following action is the one that resolved the problem but its worth the try,
Seems that I didnt had the Drive API enabled ,I had it in the enabled apis but i had to actually click the gear icon next to it and then click enable and provide the application name.
Just link the same package as many times as you have Client ID's in your Developer Console "Debug & Release Client ID's"
The thing is if you link your app to the Game Services with the wrong SHA1 fingerprint, Games Services will pick it up and associate it as the main Client ID.
Once you link the same app again to your Game Services, it will automatically pick up the other Client ID's
I had exactly the same problem, and in my case, I fixed it regenerating the API Key from the Google APIs Console. Go to Credentials, select your API key and then click on "Regenerate Key". You don't need to update anything in your code or link more apps, just regenerate and it starts working magically.