New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 834741 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Google servers throw an error when making In-app purchase

Reported by he...@wyatt.engineer, Apr 19 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36

Steps to reproduce the problem:
 1. Install browser extension
2. Inspect the background page
3. Enter the following into the console:

google.payments.inapp.buy({
  'parameters': {'env': 'prod'},
  'sku': 'copiedin_full_100',
  'success': msg => console.log(msg),
  'failure': err => console.log("err", err),
});

4. Click "Buy"

What is the expected behavior?
You should be able to make the in-app purchase

What went wrong?
The "Chrome Webstore Payments" window makes a POST to 

https://payments.google.com/efe/payments/oauth/embedded/buy_flow/submit?(removed parameters)

Google servers return with an error: "An unexpected error has occurred. Please try again later."

WebStore page: https://chrome.google.com/webstore/detail/copiedin/jgiejpldlcmmopmojhhnjgidjcijbbla

Did this work before? No 

Chrome version: 66.0.3359.117  Channel: n/a
OS Version: OS X 10.12.6
Flash Version:
 
Labels: Needs-Triage-M66
Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback Triaged-ET
Tested this issue on reported version 66.0.3359.117 & Canary 68.0.3400.0 using  Win-10, Mac 10.13.3  and followed the given steps,

Steps
-----------
1. Installed browser extension given in the original comment.
2. Clicked on Background page link in chrome://extensions page.
3. Entered the given code into the console.
4. Observed that the page is navigated to ""Complete your purchase"" page 

@Reporter: Here it is asking for Payment, we don't have testing card's to verify this issue. Can you please tell us any other way to test this issue? Or is there any simple test case available to check this issue from our end. 

Thanks
834741.mp4
1.6 MB View Download
Hi Phanindra,

I've added your email address, phanindra.tm@gmail.com, as a tester, so you will not be charged for the transaction.

To verify, please read the official testing docs: https://developer.chrome.com/webstore/payments-iap#testing

Just so you know, it's using the official Google Merchants/Payments system, and the Payments API. https://developer.chrome.com/webstore/payments-iap

In any case, notice it said "Billing starts Apr 27", the payments don't start for 7 days because it has a demo, so even if there's an error, you still won't be charged and we can cancel it right away.

Please let me know how else I can help.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 21 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Unable to test this on reported version 66.0.3359.117 because we are getting 404 & 405 errors while using URL provided in  original comment  

Attaching screenshot for reference.

" WebStore page: https://chrome.google.com/webstore/detail/copiedin/jgiejpldlcmmopmojhhnjgidjcijbbla " & 

"https://payments.google.com/efe/payments/oauth/embedded/buy_flow/submit?"

Steps
-------
1. Logged in to chrome account using phanindra.tm@gmail.com
2. Entered the webstore page URL
3. Still observing error 404

 @Reporter: Could you please let us know is there any other option available to install this extension? If possible could you please send the extension as an attachment folder to check this issue from Chrome testing team.
 
Thanks!
834741.PNG
44.4 KB View Download
Hi,

It's because you're not signed into your phanindra.tm@gmail.com account on the webstore.

I've made a video demonstrating how to fix this. The video shows that I also got the 404 error because I was not signed into the correct account, but after signing in, the 404 error goes away and I can download the extension.

https://www.useloom.com/share/177f52f0e6f149339f556d8f68d0731f

Please let me know if you have any other questions.
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 24 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Unable to purchase the app as we are getting Invalid card details Error.

@Reporter: Tested the issue by providing multiple dummy cards from the url as given bellow:

1. https://www.datatrans.ch/showcase/test-cc-numbers,2.http://www.getcreditcardnumbers.com/. 

we have tried all cards which are in mentioned in the sites as we couldn't move furhter to test this issue, so can you help us to test this to furthermore.

Thanks!

Comment 9 Deleted

Comment 10 Deleted

Phanindra where did you find that credit card URL? It's not mentioned in the official testing documentation.

https://developer.chrome.com/webstore/payments-iap#testing
Project Member

Comment 12 by sheriffbot@chromium.org, Apr 26 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Phanindra, the Google backend service is the one that processes your card information. IF you're getting "Invalid card details" Error, that's the GOOGLE BACKEND telling you that. There's literally nothing I can do to change that.
Phanindra, I will literally send you $5 via Google Pay if it means you'll properly test this. I'm pleading with you to please help

Comment 15 by ajha@chromium.org, May 8 2018

Cc: rouslan@chromium.org
Components: Blink>Payments UI>Browser>Payments
Adding proper component and requesting rouslan@ for help in triaging this further.

Comment 16 by ajha@chromium.org, May 8 2018

Cc: ma...@chromium.org
Looks like rouslan is OOO, ccing mathp@ as well for inputs on this.
Cc: ligim...@chromium.org durgapandey@google.com
Durga, will it be possible for you to find someone from Payments team to followup on this bug.
Labels: TE-NeedsTriageHelp
As per comment #17, adding 'TE-NeedsTriageHelp' label and requesting durgapandey@ to look into the issue and help in further triaging.

Thanks...

Comment 19 by ma...@chromium.org, May 11 2018

I'll send an email to the Google Payments team for triage (this is the Chrome browser bug tracker).

Comment 20 by ma...@chromium.org, May 14 2018

Components: -Blink>Payments -UI>Browser>Payments Platform>Extensions>API
Owner: devlin@chromium.org
Over to Devlin since this is an extension API. 
Cc: rdevlin....@chromium.org
Owner: jawag@chromium.org
Status: Assigned (was: Unconfirmed)
jawag@, seems like something on the payments backend.  Do you know who owns this?

Comment 22 by jawag@chromium.org, May 14 2018

Owner: phu@chromium.org
I think it's possible this could be a bug in the CWS Payments code. +phu@, could you take a look and if everything looks ok, we can send to the Payments team to investigate.

Comment 23 by phu@chromium.org, May 14 2018

I was able to buy the in-app product without a problem... Could the developer please try again and provide the login account if it can still be reproed? Also, please note the owner's account probably can not purchase her/his own products.
Well I tried to purchase it again as before, and I got the following:

{"srp":[["An unexpected error has occurred. Please try again later.",null,"56c2f8ad90f28"] ... (a bunch of other stuff)


Then I opened up Chrome Canary and logged into a different account, ran through the steps, and the error didn't occur. This means either developers in general get this error when trying to buy their own product, or it's just something with my account (hello@wyatt.engineer). Either way, is that really an "Unexpected error"? And wouldn't you agree the returned text is really unclear? Finally, as far as I know this isn't documented anywhere that you can't buy your own products.

Comment 25 by phu@chromium.org, May 14 2018

yeah, developers can't buy their own products. We can look into improving the returned messages, and make sure it's documented clearly as a first step.

Sign in to add a comment