I had an app that was working fine with inapp purchase - I still was in test mode but it was fine.
Then I decided to go to production but got issues - in the meantime nI had lost my certificate keys, so I had to use another package name, upload a new app on Google play and use new certificate credentials.
Anyway.
I did the exact same thing with this new app, and I also add the inapp purchase package, but when I launch the app I have this error :
Error while retrieving the informations from the server ([DF-AA-20])
Any idea of why I have this error message ?
I checked the inapp package name several times and it's ok...
What could be the issue ?
I've been trying to solve this for hours...
Thanks for your help.
I was able to solve the issue by doing these steps:
- I copied the public key found in "Services & API" google account and added it in my code
- I published the app in alpha mode and had to wait until it was really "published", and not "pending publishing"
Now it's working fine and I'm able to make test purchases.
But then I deleted the test account and tried to make a real purchase, and I'm having this error:
"Error: Impossible to buy this article"
Does anybody had this issue ?
Thanks
Related
Completed build the web bot app in Microsoft Azure. It runs fine in the bot emulator locally. But in the azure , in the beginning it doesn't respond to the question asked. Now it keeps me waiting for the bot to ready.
Issue is listed as:
There was an error sending this message to your bot: HTTP status code InternalServerError
There was no option to update QnAKnowledgebaseId,QnAAuthKey and QnAEndpointHostName and hence I manually added those field.
When did I go wrong and how do I get it working in Azure?
Couple of things to note:
Please ensure you have updated the Messaging endpoint correctly as described in the picture below:
Make sure you have updated the MS App ID and password correctly, also the QNAKnowledgeBaseID in the configuration section like below:
If still doesn't help , please connect application Insights to your bot in order to see the innerExceptions of this InternalServerError. With app insights you can see the Failed Requests the exceptions and the specific platform errors.
Hope it helps, feel free to tag me in your conversation and share the code repo , will help further.
It's working in test mode, but I have to go into live mode with stripe live key, it's not working in android.
If your issue is
"Request Failed", even though you could see the white window to show the cards starting to pop up, then I have the same issue.
I am in contact with Stripe support. They told me everything I have done is correct and it should be working with Stripe.
I am opening a ticket on Google Side to understand why the production isn't working. Only them can actually help now, because they will have access to the logs giving the error.
I will post here if I get any response from it
Yesterday, I was doing some test with Instagram API. I want to design a web page where I show the lastest photos in our account (Some like social feed). Today, I'm recieving this error: "The client used for authentication is no longer active.".
Somebody knows if I did some wrong working with your API and How can I do to fix this problem.
Best regards.
Thanks.
I'm running into similar issues. Have not been able to successfully pull anything through the API for over 12 hours.
Check out this link for quick API testing:
http://instagram.com/developer/api-console/
Nothing seems to work.
I need some advice on setting up merchant account in google.
When I try to set up merchant account, account signing up page shows me an error.
The error code is shown as "An error occurred {"type":"PLATFORM_ERROR", "payload":"0"}"
I've tried to resolve this issue with Google support team, but they keep sending me general information and manual..
Please give me suggestions on this issue. (I already finished developing my commercial application, but can't set the price because of this issue. )
Thanks in advance.
I had the same issue.
What I did to resolve it was to flush the browser cookies, history and cache. After that, I opened a new browser tab and logged in to my Google Wallet account (the one I set up previously to BUY apps on the play store). As I was logging in, I noticed there was some error but it quickly resolved itself - I successfully logged in and could see what I previously bought.
After that, I closed and re-opened my Google Dev Console, and tried to setup a Merchant Account again and it worked.
I experienced the same problem and I finish solved changing my address length, uou can't use more than 64 characters. see https://stackoverflow.com/a/21412790/2359141
clear cache and everything by using ctl+alt+delete
keep only one tab
Select proper product type , I selected Computer software its worked for me
Do sign out and login in wallet google
I found the solution.
You just have to let the VAT number empty during registration, fill it later.
It worked for me.
I got the payload error as well, what resolved my problem was changing my PO Box address to a physical address. Google chat support figured it out.
We have developed a SaaS solution on Windows Azure. We generate Ical feeds for the appointments in our applications for every user.
The Ical seems to work on outlook, iphone etc.
Google calendar is the only one where it does not work.
We work with a SSL certicate signed by GoDaddy.
When working with a normal http connection the Ical seems to work like normal.
I would assume google accepts the certificates from GoDaddy but there still seems to be a problem?
I had different situations:
Our events pop up but then disappear again and we get the error: 'Could not fetch the URL'
Or our events pop up but we keep getting the message 'Importing calendar for URL'. That message stays there forever. When refreshing our events will stay but will not be updated.
Validating the Ical with http://severinghaus.org/projects/icv/ works.
Downloading the .ics and inserting it manually works as well.
Any help?
Kevin,
Google is having an issue right now with all iCal feeds, which is most likely the cause of your problem. The symptons are just as you described, they show up and then disappear.
Google hasn't come out and admitted anything yet, but it's obviously something on there end. Hopefully we get a fix soon, I'm in the same boat as you.
You can follow the issue here:
http://productforums.google.com/forum/#!topic/calendar/tB7ICbqeLpo
Problem seems to be related to your SSL certificate. Similar question was answered here Google calendar can't import my ical file