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.
Related
I published my app in internal app sharing. After I shared link to download to myself, but to another account. I turn on internal app sharing in Google Play on my phone. When I click downloading, I catch error -> Error retrieving information from server. DF-DFERH-01
I tried to test in two phones, but with same google account.
There is a step I missed - testers have to opt in to the test program before they can use the shared link, and until they do they get the opaque DF-DFERH-01 error. On the Play Console under Release Management, select App releases. In Internal test track, click Manage. Under Manage Testers click the drop arrow. This opens up a panel, and near the bottom is an opt-in URL. Copy this and send it to testers. They have to click on this link and agree to opt in to the test program. They can then download the current version. After this they can also use internal app sharing links for new builds.
In my case, I was trying to access the internally shared debug app not a production testing app. For this, I was using Internal App Sharing feature. To be able to install and use such apps one's email needs to be added to an email-list(as per the settings we had) otherwise, anyone with the link can install.
Problem
The problem is despite having my email in the list, and email representing a google account I was not able to install it. I faced this error.
Click here to see the Screenshot
Cause
I maintain about 8 google accounts on my mobile and I was logged in to all of them. I realized having multiple accounts is causing the issue.
Solution
Instead of logging out from all the google accounts, I simply created a new user in my mobile and set it up. Then I opted-in to Internal App Sharing in the App store. Then shared the app link via google-keep. Voila, I was able to install it.
In my case I just had to wait ~48 hours and it Just Worked with no other changes.
A few more silly things to consider if you are new to Google Play Console.
You need to make sure to enable Internal App Sharing on Google Play Settings, here is a tutorial for that.
Do not forget to publish your modifications by clicking on publication overview (sorry for the Portuguese language on the pic, but you can find through the icon):
And then publishing it by clicking on the blue button (publish modifications or something like that):
After doing this, try to clean the cache of your play store and remove all updates from play store (after doing this you'll need to enable Internal App Sharing again).
I was able to get rid of the error by clearing the storage of the google play store app then open the play store app again and enabling the internal app feature then opening the internal app sharing link again.
sometimes if that didn't work , restarting the device does the trick!
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.
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 implement in app billing v3 and its work fine for android test product_id. But when i create my own product_id in my developer account. Than upload my sigend apk as a draft and install signed apk on device and try to run the app, but I continually get "Error while retrieving information from the server. [RPC:S-7:AEC-0]". This problem remains same even after 2 days.
Can anyone have a solution for this?
Try like this, Even i faced the same previously
First method
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.
if it fails,
On a computer (not tablet or phone) sign into your Google Wallet, click Payment Methods then edit to edit info.
I made my test account to be synced in my device and ready to test the app.
While I am about to purchase the product in my app the google play prompts me to continue after entering credit card details.
After entering details of the card in the device it is showing error as
Error while retrieving information from the server [RPC:s-7:AEC-0]
I am using Google play version 3.10.9
And i already tried to uninstall the update of google play removing my account and rebooting device but no use found the same error again and again could any one help me out of this
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 had that problem too...turns out my credit card info on file needed updated to my new expiration date.
These instructions came from troubleshooting on my phone.
On a computer (not tablet or phone) sign into your Google Wallet, click Payment Methods then edit to edit info. Hope it works for you too!
This worked for me when I encountered the same issue on my KitKat.
Remove your account from the device (Settings > Accounts > Google > Remove Account)
Remove the following data:
Settings> Applications > All> Downloads > delete data.
Settings> Applications > All> Play Store> delete data.
Settings> Apps > All> Google Services Framework (or if they have it in English: Google Service Framework) > delete data.
Log in again and it was fixed for me.
I got similar error while using in-app-purchase in android. My mistake is I used wrong purchase id while instantiating the purchases.
public static final String PRODUCT_ID_ASTRO_Match = "android.test.product";//wrong id not in play store dev console
Replaced it with:
public static final String PRODUCT_ID_ASTRO_Match = "android.test.purchased";
and it worked.
on the BlueStacks emulator worked for me the following solution
Go to ”Settings” -> “Applications” -> “Manage Applications” and select “All”
Go to “Google Play Services Framework” and select “Clear Data” & “Clear Cache” to remove all the data.
Go to “Google Play Store” and Select “Clear Data” & “Clear Cache” to remove all the data regarding Google Play Store.
Go to “Settings” -> “Accounts” -> “Google” -> Select “Your Account”
Go to “Menu” and Select “Remove Account”.
Now “Restart” your mobile device.
Go to “Menu” and “Add Your Account”.
and try to perform update or download.
I had the same issue - it sorted itself out in ~3 hours after I uploaded the app to the Play console. According to Google:
Warning: It may take up to 2-3 hours after uploading the APK for
Google Play to recognize your updated APK version. If you try to test
your application before your uploaded APK is recognized by Google
Play, your application will receive a ‘purchase cancelled’ response
with an error message “This version of the application is not enabled
for In-app Billing.
While the message is not the same, I suspect the root cause to be the same.
Call to your bank and ask them to activate your card to internet-use. Thats what helped me.
Check that the application on the test device and Google Play developer console really match.
I might have a bit of a special case but it might help someone: First, I had uploaded a package to Google Play that I had created with an ant build script. Second, on the test device, I debugged the same application (or so I thought). I got the "Error while retrieving information from server. [RPC:S-7:AEC-0]", and logcat displayed:
Class not found when unmarshalling: com.google.android.finsky.billing.lightpurchase.PurchaseParams, e: java.lang.ClassNotFoundException: com.google.android.finsky.billing.lightpurchase.PurchaseParams
The problem was that in the ant script, I have aapt command for modifying the package name. However, Eclipse does not run that command, so there was a package name mismatch between the applications in Google Play and the test device.
The same problem Error while retrieving information from server. [RPC:S-5:AEC-0] was resolved after these steps:
Change password of your Google account via web.
Wait for a Sign-in error notification on your device.
Type new password and problem should disappeared.
Actually, this helps me.
This error coud be also due to your google account already having Google Wallet/Google Checkout account linked. The existing account cannot be used for example it is a merchant account. Took me 20 minutes to figure out. Add new Google Account to your device, restart. While in Google Play switch to your new account. Buy your app/book/movie.
As a last resort, if all other suggestions fail, then backup all your data and do a factory reset.
If you are in a country such as Argentina, you should call your bank and verify that your card is authorized for international purchases. Certain credit cards in that country (such as pre-paid credit cards) are ONLY authorized for domestic purchases and purchases in bordering countries. They DO work online, but the purchase must be from a bordering country. What this means is that you may get this message because your card is valid but denied. I know, because this has happened to me today. Hopefully this helps someone else understand what their system is telling them.
As I never had a paid app in my google account I don't think its related
to credit cards nor to cache clear in google services.
the trick that worked for me :
change the Android date back and forth once (manually).
re-sync my google account (manually).
go to Play app and download . all worked just fine this time.
I did notice a 2-3 hours idle will also fix it by itself.