Unable to save sandbox postback url
47 views
Skip to first unread message
Jack
May 29, 2012, 1:08:38 PM5/29/12
to In-App Payments
I am unable to save a postback url in the sandbox settings page. After
clicking 'save', the page reloads and the field is blanked. Saving
works with an old test seller account I have. I'm using the new
account because the old account isn't receiving postbacks. With the
old account, I tested the postback url from two external locations to
make sure the server is properly exposed. Is google in-app payments
having server issues? Thanks
clicking 'save', the page reloads and the field is blanked. Saving
works with an old test seller account I have. I'm using the new
account because the old account isn't receiving postbacks. With the
old account, I tested the postback url from two external locations to
make sure the server is properly exposed. Is google in-app payments
having server issues? Thanks
Jack
May 29, 2012, 1:15:11 PM5/29/12
to In-App Payments
I just tried saving again, and it's working now. However, I'm still
unable to receive postbacks. I've looked through old threads in this
group and have tried the following steps to no success:
- create new test buyer account
- create new test seller account
As noted above, I have verified the postback url is publicly exposed.
I tested my sandbox account a few weeks ago with no problems. Since
then the only thing that has changed is my server's ip address. In
case it's important, I have always been using a direct ip address in
the postback url, e.g. http://111.111.111.111/mypostbackroute.
Is there a way to see more detail errors Google's servers experience
when trying to postback? Thanks
unable to receive postbacks. I've looked through old threads in this
group and have tried the following steps to no success:
- create new test buyer account
- create new test seller account
As noted above, I have verified the postback url is publicly exposed.
I tested my sandbox account a few weeks ago with no problems. Since
then the only thing that has changed is my server's ip address. In
case it's important, I have always been using a direct ip address in
the postback url, e.g. http://111.111.111.111/mypostbackroute.
Is there a way to see more detail errors Google's servers experience
when trying to postback? Thanks
Jack
May 29, 2012, 3:27:59 PM5/29/12
to In-App Payments
The postback is now working without changes on my end. Occasional
downtime and problems in the sandbox system are understandable and not
critical for me, but it would be helpful if the sandbox error popup
included more details about the problem.
On May 29, 12:15 pm, Jack <typingsel...@gmail.com> wrote:
> I just tried saving again, and it's working now. However, I'm still
> unable to receive postbacks. I've looked through old threads in this
> group and have tried the following steps to no success:
>
> - create new test buyer account
> - create new test seller account
>
> As noted above, I have verified the postback url is publicly exposed.
> I tested my sandbox account a few weeks ago with no problems. Since
> then the only thing that has changed is my server's ip address. In
> case it's important, I have always been using a direct ip address in
> the postback url, e.g.http://111.111.111.111/mypostbackroute.
downtime and problems in the sandbox system are understandable and not
critical for me, but it would be helpful if the sandbox error popup
included more details about the problem.
On May 29, 12:15 pm, Jack <typingsel...@gmail.com> wrote:
> I just tried saving again, and it's working now. However, I'm still
> unable to receive postbacks. I've looked through old threads in this
> group and have tried the following steps to no success:
>
> - create new test buyer account
> - create new test seller account
>
> As noted above, I have verified the postback url is publicly exposed.
> I tested my sandbox account a few weeks ago with no problems. Since
> then the only thing that has changed is my server's ip address. In
> case it's important, I have always been using a direct ip address in
Peng Ying
May 30, 2012, 4:57:46 PM5/30/12
to in-app-...@googlegroups.com
Hmm try looking in the JWT it should now include error messages that give you at least some idea of the cause.
Peng Ying
May 30, 2012, 5:00:34 PM5/30/12
to in-app-...@googlegroups.com
Jack
May 30, 2012, 8:23:32 PM5/30/12
to in-app-...@googlegroups.com
Thanks for the reply. I didn't realize the failure callback contained more details. This will be helpful.
Reply all
Reply to author
Forward
0 new messages