In App Payments sandbox down?

[Adam Villalobos]

We had a couple applications being tested in the sandbox right now,
all of them fail to start now. After calling buy, it displays the
window with the product correctly, however it fails to fully load,
displaying:

"Uh oh. There was a problem.

We couldn't start your purchase because of a technical issue."

Its not displaying any additional message now, but one person
mentioned it displayed bad seller key.

[Adam Villalobos]

Nothing changed with our client or server code when this started
happening.

[Peng Ying]

Thanks for notifying us of the issue, I'll speak with the engineers.

--

Developer Programs Engineer

Google Commerce

Google+

[Adam Villalobos]

Thanks! it seems to be working again.

Adam

On Nov 22, 1:41 pm, Peng Ying <py...@google.com> wrote:
> Thanks for notifying us of the issue, I'll speak with the engineers.
>

> On Tue, Nov 22, 2011 at 1:38 PM, Adam Villalobos <a...@ziplinegames.com>wrote:
>
> > We had a couple applications being tested in the sandbox right now,
> > all of them fail to start now. After calling buy, it displays the
> > window with the product correctly, however it fails to fully load,
> > displaying:
>
> > "Uh oh. There was a problem.
>
> > We couldn't start your purchase because of a technical issue."
>
> > Its not displaying any additional message now, but one person
> > mentioned it displayed bad seller key.
>
> --
> Developer Programs Engineer
> Google Commerce
>

> Google+ <http://goo.gl/28b8c>

[Peng Ying]

Awesome let us know about any other issues we can help us.

[Brian]

I'm having the same issue today as well. Everything has been working
fine since last week and there have been no code changes on my end.

On Nov 22, 5:06 pm, Peng Ying <py...@google.com> wrote:
> Awesome let us know about any other issues we can help us.
>

> On Tue, Nov 22, 2011 at 2:53 PM, Adam Villalobos <a...@ziplinegames.com>wrote:
>
>
>
>
>
>
>
>
>
> > Thanks! it seems to be working again.
>
> > Adam
>
> > On Nov 22, 1:41 pm, Peng Ying <py...@google.com> wrote:
> > > Thanks for notifying us of the issue, I'll speak with the engineers.
>
> > > On Tue, Nov 22, 2011 at 1:38 PM, Adam Villalobos <a...@ziplinegames.com
> > >wrote:
>
> > > > We had a couple applications being tested in the sandbox right now,
> > > > all of them fail to start now. After calling buy, it displays the
> > > > window with the product correctly, however it fails to fully load,
> > > > displaying:
>
> > > > "Uh oh. There was a problem.
>
> > > > We couldn't start your purchase because of a technical issue."
>
> > > > Its not displaying any additional message now, but one person
> > > > mentioned it displayed bad seller key.
>
> > > --
> > > Developer Programs Engineer
> > > Google Commerce
>
> > > Google+ <http://goo.gl/28b8c>
>
> --
> Developer Programs Engineer
> Google Commerce
>

> Google+ <http://goo.gl/28b8c>

[Brian]

Sorry, just a minute after I posted things seem to be magically
working again.

[Brian]

It seems like things are suddenly down again for me and no code
changes. Since about yesterday noon CST I haven't been receiving
postbacks from Google.

[Peng Ying]

Yeah, we're aware of this and are working to restore sandbox service.

[Brian]

Any estimate on when it'll be back up? Sandbox service still seems to
be down.

> Google+ <http://goo.gl/28b8c>

[Peng Ying]

Sandbox is up, though there are some cookies that could be causing
issues. Test a purchase in the incognito view, if it works there then
you'll need to clear your cache/cookies.

[Brian]

I tried incognito mode before and after clearing my cache and cookies.
 Both times I got:
"Looks like there is an error in the setup for your purchase. Please
contact the merchant with this error message: Invalid 'iss' (bad
secret key)."
The iss hasn't changed in the code, and when I went to verify that by
checking the seller info at https://sandbox.google.com/checkout/customer/gadget/inapp/settings.html
I got nothing but a blank page.

[Peng Ying]

Well an outage wouldn't give you that error. I just tested sandbox
w/o issues. I'm guessing that you probably have a bad key/secret or
are specifying the wrong environment.

[Brian]

Right, which is why I tried to verify what my key and secret were, but
I'm unable to find that information using the link provided in the
documentation. Is there any other way to obtain that information?

On Dec 12, 3:30 pm, Peng Ying <py...@google.com> wrote:
> Well an outage wouldn't give you that error.  I just tested sandbox
> w/o issues.  I'm guessing that you probably have a bad key/secret or
> are specifying the wrong environment.
>
>
>
>
>
>
>
>
>
> On Mon, Dec 12, 2011 at 11:21 AM, Brian <beng...@gmail.com> wrote:
> > I tried incognito mode before and after clearing my cache and cookies.
> >  Both times I got:
> > "Looks like there is an error in the setup for your purchase. Please
> > contact the merchant with this error message: Invalid 'iss' (bad
> > secret key)."
> > The iss hasn't changed in the code, and when I went to verify that by

> > checking the seller info athttps://sandbox.google.com/checkout/customer/gadget/inapp/settings.html

[Peng Ying]

Hmm it can only be found on the settings page. Have you tried opening
the settings page in an incog window or a different browser?

[Brian]

I am now able to access the settings page. Yesterday and this morning
it showed a blank page but now it loads normally.

The seller info matches, but now the error message has changed back to
"Sorry, we were unable to process this request. The order has been
automatically cancelled and you will not be charged for the purchase.
Please try again later."

The code has not changed since December 6, and since that update
orders have went through fine but then have completely failed since
the known downtime on December 7 up until now. We're still not
receiving any postbacks.

[Matt Endsley]

Is the sandbox configuration down now?

I still get the "We couldn't start your purchase because of a
technical issue." even when using the inapp purchase demo page at:
https://sandbox.google.com/checkout/customer/gadget/inapp/demo.html

[Brian]

FWIW, I still haven't had any success with the sandbox in my app since
December 7.

[pying]

Hey guys, an update:

The sandbox was down yesterday but should be back up. We apologize
for the outage. In regards to Brian's account our engineers should
have fixed it? It was stuck in a state where you added a new payment
method but the payment method's fake auth in sandbox didn't complete
which caused it to store incorrectly. We just removed the payment
method so it should now be fine?

[pying]

Ok just kidding, sandbox is still down the patch that was supposed to
be pushed yesterday hasn't been pushed yet. I expect it to be back up
around noon.

[pying]

Ok sandbox should be fixed

[Matt Endsley]

Thanks, everything is working correctly now!

On Dec 21, 9:24 am, pying <py...@google.com> wrote:

[Brian]

Peng,

By new payment method, do you mean credit card provider like Visa,
Mastercard, Amex?

If so, then that might be consistent to the behavior we were seeing.
We were testing with the Visa test card, then things stopped working
around the time we tested the Mastercard test card. I originally
thought that could be the problem, so I made sure to delete all my
saved cards and start from scratch but that didn't help.

Unfortunately things are still not working and we're not receiving the
postback from Google.

-Brian

[pying]

Try creating a separate test buyer account for the time being.

[Brian]

Great, that worked. Not sure why I didn't think of trying that
earlier. Thanks for the suggestion.

[Peng Ying]

It's def not an ideal solution but hey whatever's quicker i suppose.

[J]

Hi Pying,

further to this exchange it appears that sandbox is down again as detailed in this thread (https://groups.google.com/forum/#!topic/in-app-payments/S47xVlJ48c0)

J

[Brian]

Peng,

Things are suddenly not working again and there haven't been any code
changes on our end. Not sure if I should continue the discussion here
or at the recently created "dreaded uh oh.." thread
http://groups.google.com/group/in-app-payments/t/4b8ef1565278f1cd

In any case, is the sandbox down and is there any way to determine the
status of it? Also, I tried the demo that Matt linked above and it
doesn't work.

-Brian

[Brian]

Sorry, please ignore my previous post.

Things are still not working with the account that had a Master Card
number added to its wallet, but the new account you suggested creating
still works. I didn't realize I was using the broken account.
However, on that topic: is there anyway to get that account back into
a useable state and is this an issue in production?

-Brian

On Jan 3, 2:12 pm, Brian <beng...@gmail.com> wrote:
> Peng,
>
> Things are suddenly not working again and there haven't been any code
> changes on our end.  Not sure if I should continue the discussion here

> or at the recently created "dreaded uh oh.." threadhttp://groups.google.com/group/in-app-payments/t/4b8ef1565278f1cd

> ...
>
> read more »

[Peng Ying]

I don't believe this issue should affect production.  I think since it's a sandbox buyer account it may take some time before the account's fixed.  You can probably just use the second test account for the time being?

[T]

This exact same problem is effecting me. I have been able to complete (sandbox) purchases for a few days now, but yesterday I started being presented with this screen. The strange thing is that I am able to complete the sandbox purchase at  https://developers.google.com/in-app-payments/docs/tutorial#1  . 

I've debugged my code and the 200 response is definitely being sent along with the orderId...

Is the sandbox down again?

[Thomas ...]

guys just use a different payment processor. i.e zooz.

when google takes your app of the market(which they will if one of the dickheads is in the mood for it) you still get paid.

p.s to google app team. FUCK YOU

---

Date: Tue, 17 Jul 2012 01:41:02 -0700
From: timothy...@gmail.com
To: in-app-...@googlegroups.com
Subject: Re: In App Payments sandbox down?

[Peng Ying]

Looks fine to me.  The tutorial runs off sandbox so that should be an indicator of the sandbox status.  We have new error messages so check out the error message in the failure callback.  

https://developers.google.com/in-app-payments/docs/jsreference#failurehandler

[T]

Hi Peng,

thanks for your response - I can confirm that it is again working (no code changes on my side).

T

On Tuesday, July 17, 2012 6:52:12 PM UTC+1, Peng Ying wrote:

Looks fine to me.  The tutorial runs off sandbox so that should be an indicator of the sandbox status.  We have new error messages so check out the error message in the failure callback.  

https://developers.google.com/in-app-payments/docs/jsreference#failurehandler