Billing-in-app error - android

I am trying to test in-app-billing. But when I purchase a good digital, I am getting error message that "A server error has occurred. Retry, or cancel and return to previous screen".
Can you suggest me to fix this issue ?
Thanks.

Searching Google for this error message reveals a lot of users in non-US countries experiencing the same issue. Could it be that Google is blocking your phone from purchasing through a non-US carrier? Try someone else's app that also does in-app purchasing and see if you are able to purchase something using their app.

Refer to this topic, a lot of fixes can be found here
http://www.google.com/support/forum/p/Android%20Market/thread?tid=3f8673f746c68442&hl=en

Please look at this thread:
Application Error : This version of the application is not configured for Market Billing
I have the same problems after upload new version of my application. After 1-3 hours problem was gone.
It's look like update problems on Google Play.

Related

Google places autocomplete closes due to billing error android

I am using google places auto-complete. I have enabled the API and also added a billing account. But still, on running the app, the fragment closes on typing an this error is shown
I/TAG: An error occurred: Status{statusCode=You must enable Billing on the Google Cloud Project at https://console.cloud.google.com/project/_/billing/enable Learn more at https://developers.google.com/maps/gmp-get-started, resolution=null}
The request is registered in the cloud platform but the error percent is 100 %. I do not understand the issue here. If anybody could help?
Based on the error message you had included; Please follow this documentation here as the document will have you follow the four step process in order to use the Google Maps Platform.
Furthermore, if you still have issue after following the documentation please let us know so we can further investigate the issue.

Android In App Billing - Error Retrieving Information From Server

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.

Google Play Store - Unexpected error (-32600)

What does the "An unexpected error occurred. Please try again later. (-32600)" mean? Today I tried to upload a new version/APK and I received this error. It offered me to save it as a draft. Now I can't Unpublish it, Delete version, Deactive version or anything else. I'm stuck with this error. I tried to Deactivate last published version. to Unpublish the whole application, to delete "Draft in Beta" versions. But whatever I do I get that error. I even tried to logout and login again. And tried different browser. Nothing helps. Anybody got an idea what could be wrong and how to solve this?
Same error here.
I contacted Google Support:
"We had an issue with our most recent update for the Developer Console and have rolled back the changes. You should be able to manage APKs and publish your app normally in the next few hours. If you still receive an error message by the end of today, please let me know and I'll be happy to investigate further."
I found a work around. Go to the APK section in your dashboard and click unpublish from there in the top menu. It gives an alert that it may take a few hours to be removed from the play store. Worked for me :)

Not Getting In-App Purhcasing CallBack for KindleFire Android

I am stuck for 5 days regarding Inn-App purchase flow. I have uploaded a version with amazon in-app 3 months ago in Amazon store. It worked well. I was able to sell in-game items through it. But, few days ago, I launched a new version of it including amazon mobile ads. And surprisingly, my app was rejected due to in-app purchase error. I updated the code little, re-submitted (didnt update app version code and version name), but got the same bug report from amazon testing team. I don't have any clue about this. My previous version worked so well, and in this version, I maintained all the purchasing flow exact same.
There is a new settings in my developer portal called Security Profile. I have not include it in my app.Is that any related to in-app purchasing ? (I also included amazon game circle in my app).
The main problem is, amazon testing team is not getting live response i.e IAP API calls are not being performed in a "Live" mode. Means, onSdkAvailable() is returning false.
My code is exactly the same as their ButtonClicker example.
The receiver is properly set on the manifest.
I use following lines in proguard,
-keep public class com.amazon.**
-keepclassmembers public class com.amazon.*{ ; }
-dontwarn com.amazon.*
As I dont have any real kindle fire device, so, resolving this issue is getting difficult for me. I am testing the app installing amazon test client in my android device. And, everything works fine there.
So my questions are,
How to make sure that IAP API calls perform in a "Live" mode ? Is there any settings which have to handle at amazon mobile distribution portal ?
Is updating version code and version name will solve that problem ?
Any other solution ?
Please help me out ..
I had IAP application and checked with SDK tester and submitted, there was not a problem. Are you sure it is IAP problem, as your application was working fine previously. was it rejected for new api's which you added in the application.
Raise issue on amazon contactus (https://developer.amazon.com/help/contactus.html). those guys will answer. As they have records why your application got rejected. and the response is pretty neat.
after struggling, I had figure out the actual problem..
In my proguard, I wrote,
keep public class com.amazon
later, I define,
keep class com.amazon**
and my problem solve. So, that was a problem of pro-guard.

Linking Play Developer Console to Google Wallet Error

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.

Categories

Resources