Google Chrome Licensing API returning 500 error. Need help!

・1 min read

Hi. Any Chrome Extensions developer here?

I've developed a chrome extension and I'm trying to provide Free Trial to users using Google License API. I'm taking the code here(https://stackoverflow.com/questions/25707443/chrome-web-store-payments-free-trial-for-extension) as reference. Getting OAuth token is working fine. But after that when I'm making a call to the license API, I'm getting below 500 error(in link). I'm not sure what I'm doing wrong. Any help is appreciated!

https://thepracticaldev.s3.amazonaws.com/i/yviatoopipigebonhlup.png

DISCUSS (10)
 
 

@Yura T: Did you have any luck with solving the issue?

 

No :(

To be honest I'm starting to doubt about choosing this Chrome Web Store API for payments organisation. Keeping an eye on Stripe API.

After all, it's the part of extension which should be extremely robustβ€”I don't want to be my extension to break because of some 3rd party payments API failure, about which the vendor doesn't care (I mean, it's a freaking 500, seriously, Google).

Hi there, I came across the same problem yesterday, seems Google is not planning to fix it and it is really near impossible to contact the relevant support about this issue.

Could you please tell me if you have managed to find a way out? By using this other API you mentioned or somehow else?

Thanks a lot in advance.

Yeah, I haven't solved it yet.

I don't have a strong time pressure to release my extension, so I'm still waiting in hope that Google will fix it in some nearest future.

But if you need to release it soon you might want to implement it via another platform. Stripe API is one of the platforms for this (I don't know other, maybe you want to research some).

As I see it, switching to another platform has following pros:

  • Better support (no 500 error, yay);
  • Cross-platform compatibility (you can release the extension not only to Chrome, but in most cases to other browsers, e.g. Firefox, and who knows, maybe Edge soon).

But the cons:

  • You have to re-write the code to support new API;
  • New API might require backend proxy (I think Stripe requires that, otherwise you'd expose your API keys);
  • The payments won't be integrated so smoothly to Chrome Web Store. Instead of having the button in the store, you would have to implement payment interface yourself.

So, I don't know. I'm not ready yet to re-write my code, so I'm waiting, but maybe for someone time is critical.

 

Hey! I'm struggling with exactly the same thing. Free trial, error 500 after license request. Have no idea what to do.

It seems to me that Google experiences some problems with their servers.

 

The issue still exists, I am getting the {"error":{"errors":[{"domain":"global","reason":"backendError","message":"Backend Error"}],"code":500,"message":"Backend Error"}}

On GitHub.com there is a sample application for one time payments, and it works when installed from CWS. So maybe the issue reproducible just for new applications/extensions. In such case, it is not going to be fixed soon, as even it is not clear whom to report that.

 

Hi guys, did you have find a solution on this issue? I faced with the same issue

 
 

Will be honest the payments api is buggy as hell. im moving all mine to stripe

Classic DEV Post from Aug 2 '18

Changelog for developers?

Potential way to help teams work together on projects

A passionate programmer. I love building new things.

A blogging community of over 100,000 software developers Join dev.to