kun602048555 / marketbilling

Automatically exported from code.google.com/p/marketbilling
0 stars 0 forks source link

Can't get Google Android Subscription API expiration time for a subscription token. Gives server error 503 #72

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
STEPS TO REPRODUCE:
When I make the following request, Google only gives error 503, and won't 
provide any useful information. 

I'm following the documentation here: 
https://developers.google.com/android-publisher/v1/purchases/get

The authorization token is recently refreshed (automatically). (Normally it 
says 401 when it's stale.)

    [root@308321 cgi-bin]# wget -dSO- 'https://www.googleapis.com/androidpublisher/v1/applications/com.kizbit.pairfinder/subscriptions/subscription99/purchases/vkorjajxnjfyhxbftpymwfox?access_token=ya29.AHES6ZSnxLdOVf2QWrX96VbpDMdUKlHFXJOFEdHM_f_ErQlL'
    Setting --server-response (serverresponse) to 1
    Setting --output-document (outputdocument) to -
    DEBUG output created by Wget 1.12 on linux-gnu.

    --2012-07-05 00:09:46--  https://www.googleapis.com/androidpublisher/v1/applications/com.kizbit.pairfinder/subscriptions/subscription99/purchases/vkorjajxnjfyhxbftpymwfox?access_token=ya29.AHES6ZSnxLdOVf2QWrX96VbpDMdUKlHFXJOFEdHM_f_ErQlL
    Resolving www.googleapis.com... 2001:4860:b007::5f, 74.125.142.95
    Caching www.googleapis.com => 2001:4860:b007::5f 74.125.142.95
    Connecting to www.googleapis.com|2001:4860:b007::5f|:443... connected.
    Created socket 3.
    Releasing 0x0000000000cc9370 (new refcount 1).
    Initiating SSL handshake.
    Handshake successful; connected socket 3 to SSL handle 0x0000000000cd8e70
    certificate:
      subject: /C=US/ST=California/L=Mountain View/O=Google Inc/CN=*.googleapis.com
      issuer:  /C=US/O=Google Inc/CN=Google Internet Authority
    X509 certificate successfully verified and matches host www.googleapis.com

    ---request begin---
    GET /androidpublisher/v1/applications/com.kizbit.pairfinder/subscriptions/subscription99/purchases/vkorjajxnjfyhxbftpymwfox?access_token=ya29.AHES6ZSnxLdOVf2QWrX96VbpDMdUKlHFXJOFEdHM_f_ErQlL HTTP/1.0
    User-Agent: Wget/1.12 (linux-gnu)
    Accept: */*
    Host: www.googleapis.com
    Connection: Keep-Alive

    ---request end---
    HTTP request sent, awaiting response...
    ---response begin---
    HTTP/1.0 503 Service Unavailable
    Content-Type: application/json; charset=UTF-8
    Date: Thu, 05 Jul 2012 04:09:56 GMT
    Expires: Thu, 05 Jul 2012 04:09:56 GMT
    Cache-Control: private, max-age=0
    X-Content-Type-Options: nosniff
    X-Frame-Options: SAMEORIGIN
    X-XSS-Protection: 1; mode=block
    Server: GSE

    ---response end---

      HTTP/1.0 503 Service Unavailable
      Content-Type: application/json; charset=UTF-8
      Date: Thu, 05 Jul 2012 04:09:56 GMT
      Expires: Thu, 05 Jul 2012 04:09:56 GMT
      Cache-Control: private, max-age=0
      X-Content-Type-Options: nosniff
      X-Frame-Options: SAMEORIGIN
      X-XSS-Protection: 1; mode=block
      Server: GSE
    Closed 3/SSL 0x0000000000cd8e70
    2012-07-05 00:09:47 ERROR 503: Service Unavailable.

EXPECTED OUTPUT: A JSON result with a long timestamp. Or at least an error with 
a description of what is wrong.

ACTUAL OUTPUT:
      HTTP/1.0 503 Service Unavailable

AFFECTED ORDER IDS (IF RELEVANT):
909960251762286
119973174719677

NOTES:

The app is uploaded, but not published.
The APK is activated.
The subscription product id is published.
I tried to purchase subscription on totally unrelated phone, not my account.
All accounts I tested are listed in Android Developer Console > Edit Profile
The BILLING_REQUEST_ITEM_TYPE is set to "subs".
The BILLING_REQUEST_API_VERSION is set to 2.
The app is signed and a release version, ant release installr.

Original issue reported on code.google.com by starrych...@oliveyou.net on 5 Jul 2012 at 5:33

GoogleCodeExporter commented 8 years ago
I have experienced the same problem.

The funniest thing is when you try the API call again and agin then you might 
get a 200 response.

Anyway, from the perspective of API, 503 response should be the error from 
Google and is really a huge blocker for the service.

503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for 
maintenance).[2] Generally, this is a temporary state.

Original comment by tszm...@gmail.com on 26 Jul 2012 at 4:11